NIST SP 800-53 Rev 5 HIGH
SA: System and Services Acquisition – NIST SP 800-53 Revision 5.1 HIGH

NIST SP 800-53 Rev 5 HIGH SA-15(3): SA-15(3) Development Process, Standards, and Tools | Criticality Analysis

Require the developer of the system, system component, or system service to perform a criticality analysis: (a) At the following decision points in the system development life cycle: [Assignment: organization-defined decision points in the system development life cycle]; and (b) At the following level of rigor: [Assignment: organization-defined breadth and depth of criticality analysis].

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

FedRAMP High · 1 control

  • SA-15(3) Development Process, Standards, and Tools | Criticality Analysis. Require the developer of the system, system component, or system service to perform a criticality analysis: (a) At the following decision points in the system development

FedRAMP Moderate · 1 control

  • SA-15(3) Development Process, Standards, and Tools | Criticality Analysis. Require the developer of the system, system component, or system service to perform a criticality analysis: (a) At the following decision points in the system development
  • NIST800-SA-15(3) SA-15(3) Development Process, Standards, and Tools | Criticality Analysis

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 – NIST SP 800-53 Revision 5.1 HIGH

Query this from an agent

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