AWS Well-Architected Security Pillar covers 45.9% of ASD Strategies to Mitigate Cyber Security Incidents
17 of the 37 controls in ASD Strategies to Mitigate Cyber Security Incidents are already satisfied by evidence you collected for AWS Well-Architected Security Pillar. 20 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.
What this leaves you to do
ASD Strategies to Mitigate Cyber Security Incidents has 37 controls. Holding AWS Well-Architected Security Pillar already evidences 17 of them, so the work in front of you is 20 controls, not 37, which is 54% of the standard rather than all of it.
That is the whole claim. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.
In money, using only our numbers. The full report is $299 and names 17 controls of ASD Strategies to Mitigate Cyber Security Incidents you do not have to implement again, which is $17.59 per control identified. That arithmetic uses our price and our count and assumes nothing about you.
In your hours, using your assumption. We do not know what a control costs you to implement, so pick the column that looks like your organisation. These are your figures, not our claim.
| If a control takes you | 4 hours | 8 hours | 16 hours |
|---|---|---|---|
| the 17 already evidenced are | 68 hours | 136 hours | 272 hours |
| and the 20 remaining are | 80 hours | 160 hours | 320 hours |
Multiply by your own rate. We publish no rate because we have not measured yours, and a number built on an invented rate is the kind of claim this platform exists to argue against.
This number is directional. It says how much of ASD Strategies to Mitigate Cyber Security Incidents your AWS Well-Architected Security Pillar evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.
27 candidate mappings were examined and 0 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.
Where the gaps are
Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.
Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.
Claims that held
A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.
Cryptographic verification of artefacts before execution blocks unapproved code from running.
Continuous scanning of applications and images with remediation on a risk-prioritised timescale.
Deep packet inspection filters incoming and outgoing traffic for threats.
Private and restricted tiers deny compute direct internet connectivity by design.
Server workloads provisioned only from hardened images following vendor hardening guidance.
Operating system baselines hardened with unneeded software and services removed.
Unused access findings force regular revalidation and withdrawal of privilege.
Administrative permissions granted only for the specific actions each duty requires.
Claims that did not hold
Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.
The full report
Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.
Buy this crosswalk