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.

What else in your programme already covers this

This control maps to 43 controls across 22 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

  • NIST800-AU-10 Non-repudiation. Provide irrefutable evidence that an individual (or process acting on behalf of an individual) has performed [organization-defined]
  • NIST800-CM-14 Signed Components. Prevent the installation of [organization-defined] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization
  • NIST800-SI-7 Software, firmware, and information integrity
  • 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 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

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

PCI DSS 4.0 · 2 controls

  • 11.5.2 Change detection mechanism (FIM)
  • 6.4.3 All payment page scripts that are loaded and executed in the consumer's browser are managed as follows: • A method is implemented to confirm that each script is authorized. • A method is implemented
  • E8-MACRO-ML3 Configure Microsoft Office Macro Settings (ML3)
  • ASD37-01 Application control (Essential)

HIPAA Security Rule · 1 control

SOC 2 · 1 control

  • SOC2-CC6.8 Controls to prevent or detect unauthorized 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.

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