Difference between revisions of "Top 10 2014-I5 Privacy Concerns"

Revision as of 06:34, 5 February 2016

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?

Checking for Privacy Concerns includes:

Identifying all data types that are being collected by the device, its mobile application and any cloud interfaces
The device and it's various components should only collect what is necessary to perform its function
Personally identifiable information can be exposed when not properly encrypted while at rest on storage mediums and during transit over networks
Reviewing who has access to personal information that is collected
Determining if data collected can be de-identified or anonymized
Determining if data collected is beyond what is needed for proper operation of the device (Does the end-user have a choice for this data collection?)
Determining if a data retention policy is in place

How Do I Prevent Privacy Concerns?

Minimizing privacy concerns requires:

Ensuring only data critical to the functionality of the device is collected
Ensuring that any data collected is of a less sensitive nature (i.e., try not to collect sensitive data)
Ensuring that any data collected is de-identified or anonymized
Ensuring any data collected is properly protected with encryption
Ensuring the device and all of its components properly protect personal information
Ensuring only authorized individuals have access to collected personal information
Ensuring that retention limits are set for collected data
Ensuring that end-users are provided with "Notice and Choice" if data collected is more than what would be expected from the product
Ensuring the role based access control/authorization to the collected data/analyzed data is applied
Ensuring that the analyzed data is de-identified

Please review the following tabs for more detail based on whether you are a Manufacturer, Developer or Consumer

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

Top 10 2013-A6-Sensitive Data Exposure

External
FTC: Careful Connections: Building Security in the Internet of Things

@@ Line 41: / Line 41: @@
 # Ensuring that retention limits are set for collected data
 # Ensuring that end-users are provided with "Notice and Choice" if data collected is more than what would be expected from the product
+# Ensuring the role based access control/authorization to the collected data/analyzed data is applied
+# Ensuring that the analyzed data is de-identified
 Please review the following tabs for more detail based on whether you are a [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Manufacturers Manufacturer], [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Developers Developer] or [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Consumers Consumer]