Sensitive information is data that needs additional security. Social Security numbers, driver’s license numbers, bank information, and credit card details are clear examples. Start by identifying which data your organization handles; not all data calls for the same rules. section 8.5.2
For each sensitive-data category, ask:
- Who owns it? Client or user data may be yours to steward, not yours to use freely. section 8.5.2
- How long must it be held, including in operational stores and backups? section 8.5.2
- Where could it escape? Look beyond primary storage to transfers and logs. section 3.2.2 section 12.4.1
Keep the client’s workflow, change the transfer
A client received a daily file containing sensitive data by email because an employee needed to save it to a network share. Asking why email mattered revealed another option: a download in the portal the employee already used. The file could then travel over a secure channel with the transfer logged. section 3.2.2
Check what the logs retain
Protecting a database does not protect data copied into logs. One organization hashed passwords but captured clear-text passwords while logging incoming POST requests. Review API request and response logs, and mask sensitive values before they enter the logging environment rather than abandoning useful logs. section 12.4.1
