Who warns about it
Every framework below independently names this failure. They were written by different
bodies, in different jurisdictions, for different industries, and they agree.
What an auditor asks for
The artefacts named on the controls that warn about this failure. This is what closes
it, and what you will be asked to produce when somebody checks.
- Lawful basis register + per processing + Article 7 + records + per activity
- Lawful basis register + per processing + Section 19 + records + per activity
- Consent records + Section 11 + audit trail + withdrawal mechanism + records + per data subject
- Privacy notice + Section 22 + identity/DPO/purposes/rights + records + per touchpoint + versioned
- Direct marketing consent + Section 9 + opt-in/opt-out + records + per campaign + penalty awareness
- Sensitive data conditions + Section 5 + explicit consent + records + per category + per processing
Where this comes from
Harvested from the control library itself. Every control in our corpus carries the evidence an
auditor expects and the ways implementations commonly fail, recorded when that control was
verified against its source document. This page is those two fields, for one failure, across
every framework that names it.
The overlap is computed by traversing
332,959 cross-framework control mappings out from the specific controls that
warn about this failure, not from the frameworks they sit in. Those mappings were built control
by control against source documents.
Nothing here is inferred, predicted or scored. The number at the top
is a count of frameworks.
All failure modes ยท
The index