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

NIST SP 800-53 Rev 5 NIST800-SA-15: SA-15 Development Process, Standards, and Tools

a. Require the developer of the system, system component, or system service to follow a documented development process that: 1. Explicitly addresses security and privacy requirements; 2. Identifies the standards and tools used in the development process; 3. Documents the specific tool options and tool configurations used in the development process; and 4. Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and b. Review the development process, standards, tools, tool options, and tool configurations [Assignment: organization-defined frequency] to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: [Assignment: organization-defined security and privacy requirements].

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

NIST SP 800-218 · 18 controls

ISO 27001:2022 · 6 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.28 Secure coding
  • 8.29 Security testing in development and acceptance
  • 8.30 Outsourced development
  • 8.31 Separation of development, test and production environments

ISO 27002:2022 · 6 controls

  • 8.25 Secure development life cycle
  • 8.28 Secure coding
  • 8.29 Security testing in development and acceptance
  • 8.30 Outsourced development
  • 8.31 Separation of development, test and production environments
  • 8.32 Change management

CIS Controls v8 · 5 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-16.4 Establish and Manage an Inventory of Third-Party Software Components
  • CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities
  • CIS-16.9 Train Developers in Application Security Concepts and Secure Coding

PCI DSS 4.0 · 5 controls

  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.2.3 6.2.3 Code review before release
  • 6.2.4 6.2.4 Engineering techniques against common software attacks
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • 6.5.1 6.5.1 Change control procedure for production
  • ASBv3-GS-10 Define and implement DevOps security strategy
  • DS-6 Enforce security of workload throughout DevOps lifecycle
  • CCM-AIS-01 Application and Interface Security Policy and Procedures
  • CCM-AIS-04 Secure Application Design and Development

ISO 27701:2019 · 2 controls

  • 6.11 Systems acquisition, development and maintenance
  • 6.11.2 Security in development and support processes

ISO/IEC 42001:2023 · 2 controls

  • 8.3 AI risk treatment
  • A.6.1.3 Processes for responsible design and development of AI systems

SOC 2 · 2 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • AUCDR-IS-4 Formal vulnerability management program

C5 (Germany) · 1 control

  • C5-DEV-04 Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools
  • CFTC-SS-5 Systems Development and Quality Assurance Category

EU AI Act · 1 control

FedRAMP High · 1 control

  • SA-15 Development Process, Standards, and Tools (SA-15)

FedRAMP Moderate · 1 control

  • SA-15 Development Process, Standards, and Tools (SA-15)
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
  • SA-15 SA-15 Development Process, Standards, and Tools
  • SA-15 SA-15 Development Process, Standards, and Tools
  • 3(e)(i)(C) Sec. 3(e)(i)(C) (now 3(c)(i)(C)) Use secure software and hardware development for civil space systems

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-15 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 1014 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 63 it maps to, and the evidence behind each claim, over MCP and REST.