Personal data handling is documented

For the personal data it holds, the service states what it keeps, why, for how long and how it is erased.

HighChecked by hand

Applies to:
Services that handle personal data
Rule id:
security.pii-handling-documented

Why it matters

Personal data brings obligations that ordinary data does not: a person can ask what you hold and ask you to delete it, and a leak has to be reported. A service that can't list the personal data it holds can't meet any of them, and finds out during the request or the breach.

How to apply it

  • List the personal fields the service stores and the reason each is needed. Drop the ones without a reason.
  • State the retention period and how deletion works, including in backups, caches, logs and events already published.
  • Keep personal data out of logs, traces and event payloads where an id will do.
  • Encrypt it at rest and in transit, and limit who can query it.
  • Record this in the service's documentation or an ADR.

Example

"Stores name, email and delivery address for order fulfilment. Kept 24 months after the last order, then anonymized by a nightly job. Erasure requests are handled by DELETE /v1/customers/{id}/personal-data, which also publishes CustomerErased."

References

Checklists with this rule

Related agent skill: microservice-security