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
FedRAMP High 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.
- Function verification logs
- Consumer rights portal
- Verification procedures
- 45-day response tracking
- 60-day appeal handling
- Authorised agent register
What closing it also buys you
The 31 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.
NIST SP 800-53 Rev 54
New Hampshire Data Privacy Act87
New Jersey Data Privacy Act87
NIST SP 800-171A21
API 116425
ISO 2701913
BSI IT-Grundschutz10
NIST SP 1800-3213
IEC 624437
Bahrain PDPL20
APPI28
ACSC Essential Eight25
Scaled against the framework this reaches furthest into, not against a hundred
percent. Exact figures below.
| Also progresses | Covered |
Controls reached |
|---|
| NIST SP 800-53 Rev 5 United States | 4.7% | 9 of 192 |
| New Hampshire Data Privacy Act United States - New Hampshire | 87.5% | 7 of 8 |
| New Jersey Data Privacy Act United States - New Jersey | 87.5% | 7 of 8 |
| NIST SP 800-171A United States | 21.9% | 7 of 32 |
| API 1164 United States | 25.0% | 6 of 24 |
| ISO 27019 International | 13.0% | 6 of 46 |
| BSI IT-Grundschutz Germany | 10.9% | 6 of 55 |
| NIST SP 1800-32 United States | 13.6% | 6 of 44 |
| IEC 62443 International | 7.4% | 6 of 81 |
| Bahrain PDPL Bahrain | 20.7% | 6 of 29 |
| APPI Japan | 28.6% | 6 of 21 |
| ACSC Essential Eight Australia | 25.0% | 6 of 24 |
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