AWS Well-Architected Security Pillar
Infrastructure Protection

AWS Well-Architected Security Pillar SEC06-BP05: Automate compute protection

Automate scanning, patching and remediation of compute resources so protection operations run without human intervention, including dependency freshness checks in the delivery pipeline.

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 24 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 6 controls

  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-7.3 Perform Automated Operating System Patch Management
  • CIS-7.4 Perform Automated Application Patch Management
  • CIS-7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets
  • CIS-7.7 Remediate Detected Vulnerabilities

FedRAMP High · 5 controls

  • SA-22 Unsupported System Components (SA-22)
  • SI-2 Flaw Remediation
  • SI-2(2) Automated Flaw Remediation Status
  • SI-3 Malicious Code Protection
  • SI-4(23) System Monitoring | Host-based Devices (SI-4(23))

FedRAMP Moderate · 5 controls

  • SA-22 Unsupported System Components (SA-22)
  • SI-2 Flaw Remediation
  • SI-2(2) Automated Flaw Remediation Status
  • SI-3 Malicious Code Protection
  • SI-4(23) System Monitoring | Host-based Devices (SI-4(23))

CMMC 2.0 · 4 controls

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

NIST SP 800-53 Rev 5 · 4 controls

NIST Cybersecurity Framework 2.0 · 3 controls

  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

ACSC Essential Eight · 2 controls

  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • ANSSI-HYG-35 Anticipate the End of Maintenance of Software and Systems

Azure Security Benchmark · 2 controls

  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities

C5 (Germany) · 2 controls

  • C5-OPS-05 Protection Against Malware - Implementation
  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept

ISO 27001:2022 · 2 controls

  • 8.7 Protection against malware
  • 8.8 Management of technical vulnerabilities

PCI DSS 4.0 · 2 controls

  • 5.3.1 5.3.1 Anti-malware kept current through automatic updates
  • 6.3.3 6.3.3 Timely installation of security patches

UK Cyber Essentials · 2 controls

  • CE-MP.2 Anti-Malware Signatures Updated
  • CE-SU.2 Automatic Updates Enabled Where Possible

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-19 Patch operating systems (Essential)

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-4 Formal vulnerability management program

HIPAA Security Rule · 1 control

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27701:2019 · 1 control

  • 6.9.6 Technical vulnerability management

NIST SP 800-218 · 1 control

NIST SP 800-66 Rev 2 · 1 control

SOC 2 · 1 control

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

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

MCP endpointAll AWS Well-Architected Security Pillar controls