800-53 · SA System and Services Acquisition
SA-24
Design For Cyber Resiliency
frameworkNIST SP 800-53 Rev 5.2
sectionSA System and Services Acquisition
csf 2.0GV.RM-03 PR.IR-03 PR.PS-06
topics—
frameworks0 0 1
Official texta. Design organizational systems, system components, or system services to achieve cyber resiliency by:
1. Defining the following cyber resiliency goals: [Assignment: organization-defined cyber resiliency goals].
2. Defining the following cyber resiliency objectives: [Assignment: organization-defined cyber resiliency objectives].
3. Defining the following cyber resiliency techniques: [Assignment: organization-defined cyber resiliency techniques].
4. Defining the following cyber resiliency implementation approaches: [Assignment: organization-defined cyber resiliency implementation approaches].
5. Defining the following cyber resiliency design principles: [Assignment: organization-defined cyber resiliency design principles].
b. Implement the selected cyber resiliency goals, objectives, techniques, implementation approaches, and design principles as part of an organizational risk management process or systems security engineering process.NIST SP 800-53 Rev 5.2 control statement (public domain)
1. Defining the following cyber resiliency goals: [Assignment: organization-defined cyber resiliency goals].
2. Defining the following cyber resiliency objectives: [Assignment: organization-defined cyber resiliency objectives].
3. Defining the following cyber resiliency techniques: [Assignment: organization-defined cyber resiliency techniques].
4. Defining the following cyber resiliency implementation approaches: [Assignment: organization-defined cyber resiliency implementation approaches].
5. Defining the following cyber resiliency design principles: [Assignment: organization-defined cyber resiliency design principles].
b. Implement the selected cyber resiliency goals, objectives, techniques, implementation approaches, and design principles as part of an organizational risk management process or systems security engineering process.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 | GV.RM-03PR.IR-03PR.PS-06 | Cybersecurity risk management activities and outcomes are included in enterprise risk management processes; Mechanisms are implemented to achieve resilience requirements in normal and adverse situations… | No mapping. Only shares CSF GV.RM-03, PR.IR-03, PR.PS-06: related, not a mapping | |
| ISO 27001 | A.5.1A.5.29A.8.14A.8.17 | Policies for information security; Information security during disruption… | No mapping. Only shares CSF GV.RM-03, PR.IR-03: related, not a mapping+9 more loosely related (not mappings)A.8.27 Secure system architecture and engineering principles Only shares CSF PR.IR-03: related, not a mapping …and 5 more in the downloads | |
| CIS v8.1 | CIS 16.1CIS 9.3CIS 11.1CIS 13.10 | Establish and Maintain a Secure Application Development Process; Maintain and Enforce Network-Based URL Filters… | No mapping. Only shares CSF PR.PS-06, PR.IR-03: related, not a mapping+10 more loosely related (not mappings)CIS 16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities Only shares CSF PR.PS-06: related, not a mapping CIS 16.3 Perform Root Cause Analysis on Security Vulnerabilities Only shares CSF PR.PS-06: related, not a mapping CIS 16.5 Use Up-to-Date and Trusted Third-Party Software Components Only shares CSF PR.PS-06: related, not a mapping CIS 16.8 Separate Production and Non-Production Systems Only shares CSF PR.PS-06: related, not a mapping …and 6 more in the downloads | |
| SOC 2 | CC9.1A1.1A1.2A1.3 | Mitigating risks from business disruptions; Capacity management to meet availability commitments… | No mapping. Only shares CSF GV.RM-03, PR.IR-03: related, not a mapping+4 more loosely related (not mappings)CC3.1 Objectives specified clearly enough to identify risks Only shares CSF GV.RM-03: related, not a mapping CC6.6 Protection against threats from outside system boundaries Only shares CSF PR.PS-06: related, not a mapping CC8.1 Change management for infrastructure, data and software Only shares CSF PR.PS-06: related, not a mapping | |
| PCI DSS | 5.2.3.15.3.2.16.2.26.2.3 | Re-evaluation frequency set by targeted risk analysis; Scan frequency set by targeted risk analysis… | No mapping. Only shares CSF GV.RM-03, PR.PS-06: related, not a mapping | |
| CMMC | SC.L2-3.13.2 | Security Engineering | No mapping. Only shares CSF PR.IR-03, PR.PS-06: related, not a mapping | |
| HIPAA | §164.308(a)(1)(ii)(B)§164.308(a)(7)(ii)(D) | Risk Management; Testing and Revision Procedure | No mapping. Only shares CSF GV.RM-03, PR.IR-03: related, not a mapping | |
| GDPR | Art.24(1)Art.25(1)Art.32(1)(b)Art.32(1)(c) | Responsibility of the controller; Data protection by design and by default… | No mapping. Only shares CSF GV.RM-03, PR.PS-06, PR.IR-03: related, not a mapping+1 more loosely related (not mappings) | |
| NIS2 | 1.12.14.36.2 | Policy on the security of network and information systems; Risk management framework… | No mapping. Only shares CSF GV.RM-03, PR.IR-03, PR.PS-06: related, not a mapping | |
| Essential Eight | ISM-1515 | Restoration of data, applications and settings from backups to a common point in time… | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| DORA | Art.5(2)(a)Art.6(1)Art.6(8)Art.11(1) | Governance and organisation; ICT risk management framework… | No mapping. Only shares CSF GV.RM-03, PR.IR-03: related, not a mapping+5 more loosely related (not mappings)Art.12(4) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF PR.IR-03: related, not a mapping …and 1 more in the downloads | |
| CPS 234 | Para 13Para 15Para 27Para 31 | Board ultimately responsible for information security; Maintain a capability commensurate with threats… | No mapping. Only shares CSF GV.RM-03: related, not a mapping | |
| 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.