P10: Collection of Data Not Required for the User-consented Purpose
The sign-up wanted her birthday, her friends and her location.
What Is P10: Collection of Data Not Required for the User-consented Purpose?
An app that asks for everything at sign-up, and copies whatever is on screen into analytics, ends up holding data no purpose needs. You'll capture a pharmacy app's sign-up and events in an inspecting proxy, trace contacts, location and a customer's note to where they are stored, cut them from the sign-up handler and the collection settings, set a retention period, and check the traffic again. You'll finish able to spot over-collection in real requests.
What You'll Learn in P10: Collection of Data Not Required for the User-consented Purpose
- Collect a field only when its purpose needs it, such as a date of birth on a prescription order.
- Contact uploads and background precise location expose people who never agreed, and the customer's own movements.
- Analytics events need an explicit list of properties and must never carry free text.
- Every store needs a retention period, and live traffic is the test of what an app collects.
P10: Collection of Data Not Required for the User-consented Purpose — Training Steps
-
Someone Who Never Signed Up
A message lands in the privacy team's inbox from someone who is not a Pellora customer.
-
Sign Up Like a Customer
To see what the app collects, Alice signs up the way a new customer does, on her staging phone. It runs the current app build against Pellora's staging servers, holds only test data, including twelve seeded test contacts, and its traffic goes through her inspecting proxy.
-
What Sign-Up Asks For
The form asks for more than an account needs, and marks the extras as required. Alice fills it in for a test account and leaves the boxes as the app sets them, the way most customers do.
-
The Sign-Up Payload
The proxy caught the request the form sent to Pellora's API.
-
Into the App
Sign-up done. The app opens the new test account's home screen and asks one more thing.
-
All the Time
The app wants the phone's location, all the time. Alice allows it, as the sign-up form already had.
-
Where the Phone Is
Alice puts the phone down with the app closed. Ten minutes later the proxy has kept catching location requests.
-
A Note for the Pharmacist
Customers can add a note to an order for the pharmacist. Staging seeds every new test account with a sample prescription order that carries one. Alice opens it.
-
The Analytics Event
Opening the order sent one more request, to Pellora's event collector, which forwards every event to the analytics warehouse Tallowfield Analytics runs for Pellora.
-
Where It All Went
Staging shows what the app sends. To see what that did to real people, Alice opens the Data Trail, which maps production: where Nadia's sign-up and app data ended up.
Security Framework Coverage
OWASP Privacy Top 10
- P10 Collection of Data Not Required for the User-consented Purpose
OWASP ASVS
- V14.2.3 General Data Protection
- V14.2.7 General Data Protection
CWE
- CWE-359 Exposure of Private Personal Information to an Unauthorized Actor
CIS Controls
- CIS 3 Data Protection
NIST CSF
- PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
- PR.DS Data Security
NICE Framework
- DD-WRL-003 Secure Software Development
- OG-WRL-008 Privacy Compliance
GDPR
- Art. 5 Principles relating to processing of personal data (data minimisation, storage limitation)
- Art. 25 Data protection by design and by default
- Art. 9 Processing of special categories of personal data
CCPA/CPRA
- 1798.100 General duties of businesses that collect personal information
- 1798.121 Right to limit use and disclosure of sensitive personal information
HIPAA
- 164.502(b) Minimum necessary