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

NIST SP 800-53 Rev 5 NIST800-SA-17: SA-17 Developer Security and Privacy Architecture and Design

Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that: a. Is consistent with the organization’s security and privacy architecture that is an integral part the organization’s enterprise architecture; b. Accurately and completely describes the required security and privacy functionality, and the allocation of controls among physical and logical components; and c. Expresses how individual security and privacy functions, mechanisms, and services work together to provide required security and privacy capabilities and a unified approach to protection.

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

What else in your programme already covers this

This control maps to 59 controls across 19 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 · 7 controls

  • PL-8 Security and Privacy Architectures
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-4(1) Acquisition Process | Functional Properties of Controls (SA-4(1))
  • SA-4(10) Use of Approved PIV Products
  • SA-4(2) Acquisition Process | Design and Implementation Information for Controls (SA-4(2))
  • SA-8 Security and Privacy Engineering Principles

FedRAMP Moderate · 7 controls

  • PL-8 Security and Privacy Architectures
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-4(1) Acquisition Process | Functional Properties of Controls (SA-4(1))
  • SA-4(10) Use of Approved PIV Products
  • SA-4(2) Acquisition Process | Design and Implementation Information for Controls (SA-4(2))
  • SA-8 Security and Privacy Engineering Principles

ISO 27701:2019 · 7 controls

  • 6.11 Systems acquisition, development and maintenance
  • 6.11.1 Security requirements of information systems
  • 6.11.2 Security in development and support processes
  • 7.4 Privacy by design and privacy by default
  • 7.4.1 Limit collection
  • 7.4.4 PII minimization objectives
  • 8.4 Privacy by design and privacy by default

CIS Controls v8 · 5 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-16.11 Leverage Vetted Modules or Services for Application Security Components
  • CIS-16.14 Conduct Threat Modeling
  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure

HIPAA Security Rule · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

PCI DSS 4.0 · 4 controls

  • 3.6.1.1 3.6.1.1 Service provider cryptographic architecture documented
  • 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

ISO 27001:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles

ISO 27002:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles

ISO/IEC 42001:2023 · 3 controls

  • 8.3 AI risk treatment
  • A.6.2.2 AI system requirements and specification
  • A.9 Use of AI systems

NIST SP 800-218 · 3 controls

AWS Well-Architected Security Pillar · 1 control

  • SEC01-BP07 Identify threats and prioritize mitigations using a threat model

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

  • CCM-AIS-04 Secure Application Design and Development

EU AI Act · 1 control

GDPR · 1 control

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-161 Rev 1 · 1 control

  • 161R1-SA-17 Developer Security and Privacy Architecture and Design

NIST SP 800-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations

NIST SP 800-53 Rev 5 HIGH · 1 control

  • SA-17 SA-17 Developer Security and Privacy Architecture and Design

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-17 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.

If you hold ISO 27001:202216.1% covered · 851 gapsIf you hold ISO 27002:202210.8% covered · 904 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.110.2% covered · 911 gapsIf you hold CIS Controls v810.1% covered · 912 gapsIf you hold NIST SP 800-171 Rev 310.1% covered · 912 gapsIf you hold C5 (Germany)9.6% covered · 917 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll NIST SP 800-53 Rev 5 controls