NIST SP 800-53 Revision 5.1 HIGH
SA System Services Acquisition

NIST SP 800-53 Revision 5.1 HIGH SA-2: Allocation of Resources

Determine the high-level information security and privacy requirements for the system or system service in mission and business process planning; determine, document and allocate the resources required to protect the system or system service as part of the organizational capital planning and investment control process; and establish a discrete line item for information security and privacy in organizational programming and budgeting documentation.

What else in your programme already covers this

This control maps to 32 controls across 11 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 27002:2022 · 5 controls

  • 5.24 Information security incident management planning and preparation
  • 5.26 Response to information security incidents
  • 5.7 Threat intelligence
  • 8.15 Logging
  • 8.16 Monitoring activities

NIST Cybersecurity Framework 2.0 · 5 controls

  • NIST-CSF-DE.AE-03 Information is correlated from multiple sources
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-DE.CM-02 The physical environment is monitored to find potentially adverse events
  • NIST-CSF-GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

CIS Controls v8 · 4 controls

  • CIS-12.4 Establish and Maintain Architecture Diagram(s)
  • CIS-13.1 Centralize Security Event Alerting
  • CIS-3.8 Document Data Flows
  • CIS-8.9 Centralize Audit Logs

ISO 27001:2022 · 4 controls

  • 5.2 Information security roles and responsibilities
  • 5.24 Information security incident management planning and preparation
  • 5.7 Threat intelligence
  • 8.16 Monitoring activities

NIST SP 800-53 Rev 5 · 4 controls

  • NIST800-CA-7 Continuous monitoring
  • NIST800-IR-4 Incident handling
  • NIST800-PM-31 Continuous Monitoring Strategy. Develop an organization-wide continuous monitoring strategy and implement continuous monitoring programs that include: Establishing the following organization-wide metrics to be monitored: [organization-defined]; Establishing [organization-defined] and [organization-defined] for control effectiveness; Ongoing monitoring
  • NIST800-SC-7 Boundary protection

SOC 2 · 4 controls

  • SOC2-CC2.2 COSO principle 14: Internally communicates information including objectives and responsibilities
  • SOC2-CC7.1 Detection and monitoring procedures for security events are in place
  • SOC2-CC7.2 Monitors system components for anomalies indicating malicious acts
  • SOC2-CC7.3 Evaluates security events to determine incident status

NIS2 Directive · 2 controls

  • Art.20.1 Management body approves the cybersecurity risk-management measures and oversees their implementation
  • Art.21.1 Take proportionate all-hazards measures calibrated to the entity's own risk exposure

AWS Well-Architected Security Pillar · 1 control

  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-23 Resources Sufficient to Fulfil Obligations

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

DORA · 1 control

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 Services Acquisition

Query this from an agent

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

MCP endpointAll NIST SP 800-53 Revision 5.1 HIGH controls