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

NIST SP 800-53 Rev 5 NIST800-SA-3: SA-3 System Development Life Cycle

a. Acquire, develop, and manage the system using [Assignment: organization-defined system development life cycle] that incorporates information security and privacy considerations; b. Define and document information security and privacy roles and responsibilities throughout the system development life cycle; c. Identify individuals having information security and privacy roles and responsibilities; and d. Integrate the organizational information security and privacy risk management process into system development life cycle activities.

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

What else in your programme already covers this

This control maps to 51 controls across 25 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-160 · 10 controls

NIST SP 800-218 · 5 controls

PCI DSS 4.0 · 4 controls

  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.3.2 6.3.2 Inventory of bespoke software and components
  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.3 6.5.3 Separate pre-production from production

ISO 27001:2022 · 3 controls

  • 5.8 Information security in project management
  • 8.25 Secure development life cycle
  • 8.31 Separation of development, test and production environments

ISO 27002:2022 · 3 controls

  • 5.8 Information security in project management
  • 8.25 Secure development life cycle
  • 8.31 Separation of development, test and production environments

ISO/IEC 42001:2023 · 3 controls

  • 8.3 AI risk treatment
  • A.6 AI system life cycle
  • A.6.1.3 Processes for responsible design and development of AI systems
  • ASBv3-GS-10 Define and implement DevOps security strategy
  • DS-6 Enforce security of workload throughout DevOps lifecycle

C5 (Germany) · 2 controls

  • C5-DEV-01 Policies for the development/procurement of information systems
  • C5-DEV-10 Separation of environments
  • CCM-AIS-01 Application and Interface Security Policy and Procedures
  • CCM-AIS-04 Secure Application Design and Development
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • CFTC-SS-5 Systems Development and Quality Assurance Category

CIS Controls v8 · 1 control

  • CIS-16.1 Establish and Maintain a Secure Application Development Process

EU AI Act · 1 control

FedRAMP High · 1 control

  • SA-3 System Development Life Cycle

FedRAMP Moderate · 1 control

  • SA-3 System Development Life Cycle

ISO 27701:2019 · 1 control

  • 6.11.2 Security in development and support processes

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure
  • 03.16.01 Security Engineering Principles
  • SA-3 SA-3 System Development Life Cycle
  • SA-3 SA-3 System Development Life Cycle
  • SA-3 SA-3 System Development Life Cycle

SOC 2 · 1 control

  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

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