800-53 · CA Assessment, Authorization and Monitoring
CA-6
Authorization
frameworkNIST SP 800-53 Rev 5.2
sectionCA Assessment, Authorization and Monitoring
csf 2.0—
topics—
frameworks2 0 11
Official texta. Assign a senior official as the authorizing official for the system;
b. Assign a senior official as the authorizing official for common controls available for inheritance by organizational systems;
c. Ensure that the authorizing official for the system, before commencing operations:
1. Accepts the use of common controls inherited by the system; and
2. Authorizes the system to operate;
d. Ensure that the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems;
e. Update the authorizations [Assignment: organization-defined frequency].NIST SP 800-53 Rev 5.2 control statement (public domain)
b. Assign a senior official as the authorizing official for common controls available for inheritance by organizational systems;
c. Ensure that the authorizing official for the system, before commencing operations:
1. Accepts the use of common controls inherited by the system; and
2. Authorizes the system to operate;
d. Ensure that the authorizing official for common controls authorizes the use of those controls for inheritance by organizational systems;
e. Update the authorizations [Assignment: organization-defined frequency].NIST SP 800-53 Rev 5.2 control statement (public domain)
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | — | No requirement | No mapping in our data | No mapping in our data. |
| ISO 27001 | Clause 9.3.1Clause 9.3.3 | General; Management review results | Crosswalk | NIST SP 800-53 → ISO 27001 mapping |
| CIS v8.1 | — | No requirement | No mapping in our data | No mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards). |
| SOC 2 | — | No requirement | No mapping in our data | No mapping in our data (SOC 2 links are editorial only). |
| PCI DSS | — | No requirement | No mapping in our data | No mapping in our data. |
| CMMC | — | No requirement | No mapping in our data | No mapping in our data. |
| HIPAA | §164.308(a)(2)§164.308(a)(8) | Assigned Security Responsibility; Evaluation | Crosswalk | NIST HIPAA → SP 800-53 crosswalk |
| GDPR | — | No requirement | No mapping in our data | No mapping in our data (only GDPR's security articles are mapped, editorially). |
| NIS2 | — | No requirement | No mapping in our data | No mapping in our data. |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | — | No requirement | No mapping in our data | No mapping in our data (DORA links are editorial, and its technical standards are not mapped). |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.