AWS Well-Architected Security Pillar
Application Security

AWS Well-Architected Security Pillar SEC11-BP06: Deploy software programmatically

Deploy through automated pipelines with separation of duties, approvals and audit so no human pushes code or infrastructure directly to production.

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

What else in your programme already covers this

This control maps to 53 controls across 17 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 · 6 controls

  • AC-5 Separation of Duties
  • CM-3 Configuration Change Control
  • CM-5 Access Restrictions for Change
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-3 System Development Life Cycle

FedRAMP Moderate · 6 controls

  • AC-5 Separation of Duties
  • CM-3 Configuration Change Control
  • CM-5 Access Restrictions for Change
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-3 System Development Life Cycle

C5 (Germany) · 5 controls

ISO 27002:2022 · 4 controls

  • 5.3 Segregation of duties
  • 8.19 Installation of software on operational systems
  • 8.25 Secure development life cycle
  • 8.32 Change management

NIST SP 800-53 Rev 5 · 4 controls

  • ASBv3-DS-3 Secure DevOps infrastructure
  • ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy
  • DS-6 Enforce security of workload throughout DevOps lifecycle

CMMC 2.0 · 3 controls

ISO 27001:2022 · 3 controls

  • 5.3 Segregation of duties
  • 8.19 Installation of software on operational systems
  • 8.32 Change management

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

PCI DSS 4.0 · 3 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.4 6.5.4 Separate roles between production and pre-production
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
  • 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-218 · 2 controls

CIS Controls v8 · 1 control

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

ISO 27701:2019 · 1 control

  • 6.9.1 Operational procedures and responsibilities

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 Application Security

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC11-BP06 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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