4 standards bodies wrote this down separately. None of them consulted the others. That is not a preference you can argue with, it is what happens.From 4 controls across our corpus
Botswana Data Protection Act Evidence & Implementation Kit
This is the complete documentation set: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.
See what is in it, $249
The same set every buyer of this kit receives. Nothing here is produced on request.
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.
- Determination of controller status and processing in scope
- Records of processing subject to the Act
- Determination that the organisation uses personal information and is in scope
- Records of personal information held and processing performed
- Determination of organisation status and processing in scope
- Records of processing subject to the Order
What closing it also buys you
The 5 controls that warn about this failure map onto controls in other
frameworks. Close them here and this much of each of those is closed too. It is the same work
counted once, which is usually the difference between a programme that finishes and one that
does not.
ISO/IEC 27004:20163
ISO/IEC 29100:20244
ISO/IEC 238377
ISO/IEC 27557:20223
ISO/IEC 38500:20247
ISO/IEC 30111:20192
Albania Law on Protection of Personal Data (Law No. 9887, 2008, amended 2014)10
ISO/IEC 29147:20181
21 CFR Part 586
ISO/IEC 27014:20203
ISO 190116
Austria Data Protection Act (Datenschutzgesetz, DSG, amended 2018)14
Scaled against the framework this reaches furthest into, not against a hundred
percent. Exact figures below.
| Also progresses | Covered |
Controls reached |
|---|
| ISO/IEC 27004:2016 International | 3.1% | 3 of 97 |
| ISO/IEC 29100:2024 International (ISO/IEC JTC 1/SC 27) | 4.5% | 3 of 67 |
| ISO/IEC 23837 International (ISO/IEC) | 7.1% | 3 of 42 |
| ISO/IEC 27557:2022 International (ISO/IEC JTC 1/SC 27) | 3.9% | 3 of 77 |
| ISO/IEC 38500:2024 International (ISO/IEC) | 7.1% | 3 of 42 |
| ISO/IEC 30111:2019 International (ISO/IEC JTC 1/SC 27); adopted as EN ISO/IEC 30111:2020 and nationally (DIN EN ISO/IEC 30111:2020 held) | 2.9% | 2 of 69 |
| Albania Law on Protection of Personal Data (Law No. 9887, 2008, amended 2014) Albania | 10.0% | 2 of 20 |
| ISO/IEC 29147:2018 International (ISO/IEC JTC 1/SC 27); adopted as EN ISO/IEC 29147:2020 and nationally | 1.8% | 2 of 113 |
| 21 CFR Part 58 United States | 6.2% | 2 of 32 |
| ISO/IEC 27014:2020 International | 3.2% | 2 of 62 |
| ISO 19011 International | 6.7% | 2 of 30 |
| Austria Data Protection Act (Datenschutzgesetz, DSG, amended 2018) Austria | 14.3% | 2 of 14 |
Read as: closing this failure reaches that share of the named
framework's control library through cross-framework mappings held in our corpus. It is not a
claim of compliance with that framework, it is a measure of how much of it you have already
touched.
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