AWS Well-Architected Security Pillar
Security Foundations

AWS Well-Architected Security Pillar SEC01-BP08: Evaluate and implement new security services and features regularly

Review new security services and features from the provider and partners on a regular cadence and adopt those that improve the workload's security posture.

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

What else in your programme already covers this

This control maps to 13 controls across 11 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 · 2 controls

  • AUCDR-IS-STEP3 Step 3 - Have and maintain an information security capability

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.23 Information security for use of cloud services

ISO 27002:2022 · 1 control

  • 5.23 Information security for use of cloud services
  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
  • 03.14.03 Security Alerts, Advisories, and Directives

PCI DSS 4.0 · 1 control

  • 12.3.4 12.3.4 Annual review of hardware and software technologies

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

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

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