75% of ACSC Essential Eight you already have
AWS Well-Architected Security Pillar already covers about 75% of ACSC Essential Eight, leaving
6 of 24 controls as genuinely new work.
Already covered 0
Likely covered 18
New work 6
No control in AWS Well-Architected Security Pillar
maps directly to one in ACSC Essential Eight. Everything counted as covered is covered because both
map to the same third standard, which is what a crosswalk is, but it is an inference rather
than a lookup.
What is genuinely new work
Nothing in AWS Well-Architected Security Pillar reaches these. This is the list to scope.
E8-APP-ML1Application Control (ML1)
E8-APP-ML2Application Control (ML2)
E8-APP-ML3Application Control (ML3)
E8-MACRO-ML1Configure Microsoft Office Macro Settings (ML1)
E8-MACRO-ML2Configure Microsoft Office Macro Settings (ML2)
E8-MACRO-ML3Configure Microsoft Office Macro Settings (ML3)
Show the 18 you already have
E8-ADMIN-ML1Restrict Administrative Privileges (ML1)
E8-ADMIN-ML2Restrict Administrative Privileges (ML2)
E8-ADMIN-ML3Restrict Administrative Privileges (ML3)
E8-BACKUP-ML1Regular Backups (ML1)
E8-BACKUP-ML2Regular Backups (ML2)
E8-BACKUP-ML3Regular Backups (ML3)
E8-MFA-ML1Multi-Factor Authentication - Maturity Level 1
E8-MFA-ML2Multi-Factor Authentication - Maturity Level 2
E8-MFA-ML3Multi-Factor Authentication - Maturity Level 3
E8-PATCHAPP-ML1Patch Applications (ML1)
E8-PATCHAPP-ML2Patch Applications (ML2)
E8-PATCHAPP-ML3Patch Applications (ML3)
E8-PATCHOS-ML1Patch Operating Systems (ML1)
E8-PATCHOS-ML2Patch Operating Systems (ML2)
E8-PATCHOS-ML3Patch Operating Systems (ML3)
E8-UAH-ML1User Application Hardening - Maturity Level 1
E8-UAH-ML2User Application Hardening - Maturity Level 2
E8-UAH-ML3User Application Hardening - Maturity Level 3
How this is calculated
Already covered means a mapping runs from a control in AWS Well-Architected Security Pillar to that control. Likely
covered means no direct mapping exists but both frameworks map to the same control in a third
standard. New work means neither. We keep those separate rather than adding them into one
friendlier number, because blending them would present a two-hop inference as a verified
fact.
Coverage is not symmetric.
Run it the other way and you will get a
different number; both are correct.
From 332,959 cross-framework control
mappings across 723 frameworks, 531 of them verified against
their source documents. It does not tell you that you are compliant: a mapped control means
the two standards ask for the same thing, not that you have done it.
Try another pair ยท
Today's edition