This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Top 10 2014-I5 Privacy Concerns"
Craig Smith (talk | contribs) (Created page with "<center>[https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=OWASP_Internet_of_Things_Top_10_for_2014 Back To The Internet of Things Top 10]</center> ...") |
Craig Smith (talk | contribs) |
||
Line 4: | Line 4: | ||
{{Top_10:SummaryTableTemplate|exploitability=1|prevalence=2|detectability=2|impact=1|year=2013|language=en}} | {{Top_10:SummaryTableTemplate|exploitability=1|prevalence=2|detectability=2|impact=1|year=2013|language=en}} | ||
{{Top_10_2010:SummaryTableHeaderEndTemplate|year=2013}} | {{Top_10_2010:SummaryTableHeaderEndTemplate|year=2013}} | ||
− | <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider anyone who has access to the | + | <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider anyone who has access to the network the device is connected to, including external and internal users. |
</td> | </td> | ||
− | <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Attacker uses | + | <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Attacker uses the lack of transport encryption to view data being passed over the network. Depending on setup, attack could come from external or internal users. |
</td> | </td> | ||
− | <td colspan=2 {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}> | + | <td colspan=2 {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Lack of transport encryption allows data to be viewed as it travels over local networks or the internet. Lack of transport encryption is prevalent on local networks as it is easy to assume that local network traffic will not make its way out to the internet, however in the case of a local wireless network, misconfiguration of that wireless network can make traffic visible to anyone within range of that wireless network. Many Issues with transport encryption are easy to discover simply by viewing network traffic and searching for readable data. Automated tools can also look for implementation of common transport encryption such as SSL and TLS. |
</td> | </td> | ||
− | <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}> | + | <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Lack of transport encryption can result in data loss or corruption and and can lead to complete compromise of the device or user accounts. |
</td> | </td> | ||
− | <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider the business impact of | + | <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider the business impact of exposed data as it travels across various networks. Data could be stolen or modified. Could your users be harmed by having their data exposed? |
</td> | </td> | ||
{{Top_10_2010:SummaryTableEndTemplate|year=2013}} | {{Top_10_2010:SummaryTableEndTemplate|year=2013}} | ||
− | {{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection= | + | {{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=Does My Device Present Privacy Concerns?|position=firstLeft|year=2013|language=en}} |
− | The simplest way to find out if you have | + | The simplest way to find out if you have insufficient authorization/authentication is to review the password policy for the various interfaces and to review whether the interfaces allow for separation of roles. For example, all features will be accessible to administrators, but users will have a more limited set of features available. |
− | Attempting to set usernames to simple passwords such as "1234" is a fast and easy way to determine | + | Attempting to set usernames to simple passwords such as "1234" is a fast and easy way to determine if authentication/authorization is sufficient. Manual testing can help a security analyst find instances where weak passwords are allowed, access control is not limited by roles or credentials are poorly protected. Penetration testers can validate these issues by conducting brute-force attacks against usernames, reviewing access controls and testing for privilege escalation. |
Automated dynamic scanning which exercises the application will provide insight into whether these issues exist as well. | Automated dynamic scanning which exercises the application will provide insight into whether these issues exist as well. | ||
− | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection= | + | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Use Prevent Privacy Concerns?|position=right|year=2013|language=en}} |
− | Ensuring | + | Ensuring sufficient authentication/authorization requires: |
− | # | + | # Ensuring password recovery mechanisms are robust. |
# Ensuring complex password construction. | # Ensuring complex password construction. | ||
− | # Ensuring | + | # Ensuring role/discretionary based access control is in place where necessary. |
− | # Ensuring credentials are | + | # Ensuring credentials are properly protected. |
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}} | ||
− | '''Scenario #1:''' The | + | '''Scenario #1:''' The interface only requires simple passwords. |
{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;"> | {{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;"> | ||
− | Username = | + | Username = Bob; Password = 1234 |
</span>{{Top_10_2010:ExampleEndTemplate}} | </span>{{Top_10_2010:ExampleEndTemplate}} | ||
− | '''Scenario #2:''' Username and password | + | '''Scenario #2:''' Username and password are poorly protected when transmitted over the network. |
{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;"> | {{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;"> | ||
− | + | Authorization: Basic YWRtaW46MTIzNA== | |
− | |||
− | |||
</span>{{Top_10_2010:ExampleEndTemplate}} | </span>{{Top_10_2010:ExampleEndTemplate}} | ||
− | In the cases above, the attacker is able to either easily guess the | + | In the cases above, the attacker is able to either easily guess the password or is able to capture the credentials as they cross the network and decode it since the credentials are only protected using Base64 Encoding. |
Revision as of 23:28, 18 June 2014
Threat Agents | Attack Vectors | Security Weakness | Technical Impacts | Business Impacts | |
---|---|---|---|---|---|
Application Specific | Exploitability EASY |
Prevalence COMMON |
Detectability AVERAGE |
Impact SEVERE |
Application / Business Specific |
Consider anyone who has access to the network the device is connected to, including external and internal users. | Attacker uses the lack of transport encryption to view data being passed over the network. Depending on setup, attack could come from external or internal users. | Lack of transport encryption allows data to be viewed as it travels over local networks or the internet. Lack of transport encryption is prevalent on local networks as it is easy to assume that local network traffic will not make its way out to the internet, however in the case of a local wireless network, misconfiguration of that wireless network can make traffic visible to anyone within range of that wireless network. Many Issues with transport encryption are easy to discover simply by viewing network traffic and searching for readable data. Automated tools can also look for implementation of common transport encryption such as SSL and TLS. | Lack of transport encryption can result in data loss or corruption and and can lead to complete compromise of the device or user accounts. | Consider the business impact of exposed data as it travels across various networks. Data could be stolen or modified. Could your users be harmed by having their data exposed? |
Does My Device Present Privacy Concerns?
The simplest way to find out if you have insufficient authorization/authentication is to review the password policy for the various interfaces and to review whether the interfaces allow for separation of roles. For example, all features will be accessible to administrators, but users will have a more limited set of features available. Attempting to set usernames to simple passwords such as "1234" is a fast and easy way to determine if authentication/authorization is sufficient. Manual testing can help a security analyst find instances where weak passwords are allowed, access control is not limited by roles or credentials are poorly protected. Penetration testers can validate these issues by conducting brute-force attacks against usernames, reviewing access controls and testing for privilege escalation. Automated dynamic scanning which exercises the application will provide insight into whether these issues exist as well. |
How Do I Use Prevent Privacy Concerns?
Ensuring sufficient authentication/authorization requires:
|
Example Attack Scenarios
Scenario #1: The interface only requires simple passwords. Username = Bob; Password = 1234 Scenario #2: Username and password are poorly protected when transmitted over the network. Authorization: Basic YWRtaW46MTIzNA== In the cases above, the attacker is able to either easily guess the password or is able to capture the credentials as they cross the network and decode it since the credentials are only protected using Base64 Encoding.
|
References
OWASP External |