NIST SP 800-53 Rev 5
SA - System and Services Acquisition

NIST SP 800-53 Rev 5 NIST800-SA-24: Design For Cyber Resiliency. Design organizational systems, system components, or system services to achieve cyber resiliency by: Defining the following cyber resiliency goals: [organization-defined]. Defining the following cyber resiliency objectives: [organization-defined]. Defining the following

Design For Cyber Resiliency. Design organizational systems, system components, or system services to achieve cyber resiliency by: Defining the following cyber resiliency goals: [organization-defined]. Defining the following cyber resiliency objectives: [organization-defined]. Defining the following

What else in your programme already covers this

This control maps to 34 controls across 9 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 22301:2019 · 5 controls

  • 6.2.1 Establishing business continuity objectives
  • 8.2.2 Business impact analysis
  • 8.3.2 Identification of strategies and solutions
  • 8.3.3 Selection of strategies and solutions
  • 8.3.5 Implementation of solutions

CIS Controls v8 · 4 controls

  • CIS-11.2 Perform Automated Backups
  • CIS-13.8 Deploy a Network Intrusion Prevention Solution
  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-17.4 Establish and Maintain an Incident Response Process

ISO 27001:2022 · 4 controls

  • 5.29 Information security during disruption
  • 8.14 Redundancy of information processing facilities
  • 8.25 Secure development life cycle
  • 8.27 Secure system architecture and engineering principles

ISO 27002:2022 · 4 controls

  • 5.29 Information security during disruption
  • 8.13 Information backup
  • 8.14 Redundancy of information processing facilities
  • 8.27 Secure system architecture and engineering principles

ISO 27701:2019 · 4 controls

  • 6.11.1 Security requirements of information systems
  • 6.14.1 Information security continuity
  • 7.4.1 Limit collection
  • 7.4.4 PII minimization objectives

ISO/IEC 42001:2023 · 4 controls

  • 6.1.2 Risk assessment
  • 6.2 Objectives and planning to achieve them
  • 8.3 AI risk treatment
  • A.9.3 Objectives for responsible use of AI system
  • NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
  • NIST-CSF-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated
  • NIST-CSF-PR.DS-11 Backups of data are created, protected, maintained, and tested
  • NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations

SOC 2 · 4 controls

  • SOC2-A1.3 Recovery plan procedures support system recovery from failures
  • SOC2-CC5.1 COSO principle 10: Selects and develops control activities to mitigate risks
  • SOC2-CC6.6 Measures against threats outside system boundaries are implemented
  • SOC2-CC9.1 Identifies, selects and develops risk mitigation activities

NIST SP 800-172 · 1 control

  • 3.13.3e Confuse and Mislead Adversaries

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in SA - System and Services Acquisition

You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-SA-24 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 300 NIST SP 800-53 Rev 5 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 34 it maps to, and the evidence behind each claim, over MCP and REST.