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) |
Craig Smith (talk | contribs) |
||
| Line 25: | Line 25: | ||
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Prevent Privacy Concerns?|position=right|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Prevent Privacy Concerns?|position=right|year=2013|language=en}} | ||
| − | + | Minimizing privacy concerns requires: | |
# Ensuring only data critical to the functionality of the device is collected. | # Ensuring only data critical to the functionality of the device is collected. | ||
# Ensuring any data collected is properly protected with encryption. | # Ensuring any data collected is properly protected with encryption. | ||
Revision as of 03:46, 30 June 2014
| Threat Agents | Attack Vectors | Security Weakness | Technical Impacts | Business Impacts | |
|---|---|---|---|---|---|
| Application Specific | Exploitability AVERAGE |
Prevalence COMMON |
Detectability EASY |
Impact SEVERE |
Application / Business Specific |
| Consider anyone who has access to the device itself, the network the device is connected to, the mobile application and the cloud connection including external and internal users. | Attacker uses multiple vectors such as insufficient authentication, lack of transport encryption or insecure network services to view personal data which is not being properly protected or is being collected unnecessarily. Attack could come from external or internal users. | Privacy concerns generated by the collection of personal data in addition to the lack of proper protection of that data is prevalent. Privacy concerns are easy to discover by simply reviewing the data that is being collected as the user sets up and activates the device. Automated tools can also look for specific patterns of data that may indicate collection of personal data or other sensitive data. | Collection of personal data along with a lack of protection of that data can lead to compromise of a user's personal data. | Consider the business impact of personal data that is collected unnecessarily or isn't protected properly. Data could be stolen. Could your customers be harmed by having this personal data exposed? | |
|
Does My Device Present Privacy Concerns?
The most efficient way to determine if privacy concerns are present is to identify all data types that are being collected by the device, its mobile app and any cloud interfaces. The device and it's various components should only collect what is necessary to perform its function. In most cases, personally identifiable information is considered to be exposed when not properly encrypted while at rest on storage mediums and during transit over networks. |
How Do I Prevent Privacy Concerns?
Minimizing privacy concerns requires:
|
|
Example Attack Scenarios
Scenario #1: Collection of personal data. Date of birth, home address, phone number, etc. Scenario #2: Collection of financial and/or health information. Credit card data and bank account information. In the cases above, exposure of any of the data examples could lead to identity theft or compromise of accounts.
|
References
OWASP External |
