AWS Well-Architected Security Pillar
Application Security

AWS Well-Architected Security Pillar SEC11-BP07: Regularly assess security properties of the pipelines

Treat the CI CD pipeline itself as a sensitive workload and review its IAM roles, secrets handling, runner isolation and tamper resistance regularly.

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

What else in your programme already covers this

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

Azure Security Benchmark · 3 controls

FedRAMP High · 3 controls

  • CA-7 Continuous Monitoring
  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))
  • SI-6 Security and Privacy Function Verification (SI-6)

FedRAMP Moderate · 3 controls

  • CA-7 Continuous Monitoring
  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))
  • SI-6 Security and Privacy Function Verification (SI-6)

NIST SP 800-53 Rev 5 · 3 controls

C5 (Germany) · 2 controls

  • C5-DEV-04 Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools
  • C5-DEV-07 Logging of changes

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

ISO 27001:2022 · 2 controls

  • 8.25 Secure development life cycle
  • 8.31 Separation of development, test and production environments

ISO 27002:2022 · 2 controls

  • 8.31 Separation of development, test and production environments
  • 8.4 Access to source code

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
  • 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 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-218 · 2 controls

CIS Controls v8 · 1 control

  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure

CMMC 2.0 · 1 control

PCI DSS 4.0 · 1 control

  • 6.5.3 6.5.3 Separate pre-production from production

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

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gapsIf you hold ISO 27002:202273% covered · 17 gapsIf you hold FedRAMP Moderate69.8% covered · 19 gapsIf you hold Azure Security Benchmark65.1% covered · 22 gapsIf you hold PCI DSS 4.063.5% covered · 23 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll AWS Well-Architected Security Pillar controls