AWS Well-Architected Security Pillar
Infrastructure Protection

AWS Well-Architected Security Pillar SEC06-BP04: Validate software integrity

Cryptographically verify the integrity of software artefacts the workload consumes and sign software the organisation produces so unauthorised changes are detectable before execution.

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

What else in your programme already covers this

This control maps to 39 controls across 20 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-161 Rev 1 · 4 controls

NIST SP 800-171 Rev 3 · 4 controls

FedRAMP High · 3 controls

  • CM-7(2) Prevent Program Execution
  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks

FedRAMP Moderate · 3 controls

  • CM-7(2) Prevent Program Execution
  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks

NIST SP 800-53 Rev 5 · 3 controls

Azure Security Benchmark · 2 controls

  • ASBv3-AM-5 Use only approved applications in virtual machine
  • DS-2 Ensure software supply chain security

CIS Controls v8 · 2 controls

  • CIS-2.5 Allowlist Authorized Software
  • CIS-2.7 Allowlist Authorized Scripts

CMMC 2.0 · 2 controls

ISO 27001:2022 · 2 controls

  • 5.21 Managing information security in the information and communication technology (ICT) supply chain
  • 8.19 Installation of software on operational systems

ISO 27002:2022 · 2 controls

  • 5.21 Managing information security in the ICT supply chain
  • 8.24 Use of cryptography

NIST SP 800-218 · 2 controls

PCI DSS 4.0 · 2 controls

  • 11.5.2 11.5.2 Change detection on critical files
  • 6.4.3 6.4.3 Payment page script management

ACSC Essential Eight · 1 control

  • E8-MACRO-ML3 Configure Microsoft Office Macro Settings (ML3)

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-01 Application control (Essential)

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

HIPAA Security Rule · 1 control

NIST Cybersecurity Framework 2.0 · 1 control

NIST SP 800-66 Rev 2 · 1 control

SOC 2 · 1 control

  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software

UK Cyber Essentials · 1 control

  • CE-MP.4 Application Allowlisting (Alternative)

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 Infrastructure Protection

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

AWS Well-Architected Security Pillar SEC06-BP04 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 39 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll AWS Well-Architected Security Pillar controls