AWS Builder Center
Turn Security Hub findings into ISO 27001 evidence

Turn Security Hub findings into ISO 27001 evidence

AWS publishes a practical guide for using cloud services to support ISO 27001:2022 controls. The fastest path is to reuse AWS Security Hub findings through the official NIST to ISO mapping, then combine that technical evidence with records from the rest of the organization inside your ISMS scope.

Gather ISO evidence for the workloads you run on AWS

Every ISO 27001 project eventually turns into an evidence project. The standard sets the requirements for an information security management system, or ISMS, while ISO/IEC 27002 explains how to implement the controls it references. Between them they reach across people, policies, physical safeguards, technology, and the management processes that keep all of it working, which is why an audit asks for proof from almost every corner of an organization.[1]
To help with the part that runs in the cloud, AWS published the ISO 27001:2022 on AWS Compliance Guide, which maps identity, monitoring, encryption, backup, and incident response capabilities to selected Annex A controls.[1]
If your workloads run on AWS, this is where the guide pays off, because those services can produce the technical proof an auditor asks for on demand and with a timestamp. What makes that proof genuinely useful is knowing where it stops. AWS manages security of the cloud, while you keep ownership of your data, identities, configurations, risk decisions, policies, and the evidence for security in the cloud.[1]

Know which controls the guide covers

Annex A of ISO/IEC 27001:2022 lists 93 controls, with implementation guidance for each in ISO/IEC 27002:2022. That set is the reference an organization works through when it decides which controls its ISMS needs, recording those decisions in the Statement of Applicability.[1] The AWS guide works through 40 of them with implementation examples:
  • 8 of 37 organizational controls
  • 1 of 8 people controls
  • 0 of 14 physical controls
  • 31 of 34 technological controls
The pattern is hard to miss. Coverage is strongest where a control is technical and configurable, and thinnest where it depends on a building or a person. That is a fair reflection of what a cloud provider can help with, but the remaining 53 controls are no less applicable to an organization running on AWS. Many of them draw their evidence from human resources, legal, procurement, and internal audit rather than from your account.

Map an ISO control to the checks that evidence it

Two published resources do most of the work. Security Hub CSPM includes a standard based on NIST SP 800-53 Revision 5 that runs automated checks against supported AWS resources and reports pass or fail, though AWS is explicit that it covers a subset of NIST requirements and leaves out anything needing a manual check.[2] NIST, in turn, publishes an official crosswalk between SP 800-53 Revision 5 and ISO/IEC 27001:2022.[3]
Security Hub evaluates part of the AWS subset, and that subset sits inside a larger ISMS.

Put the two together and you have a repeatable path from an ISO control to a dated finding:
  1. Start with an ISO Annex A control in your Statement of Applicability.
  1. Use the NIST crosswalk to find related SP 800-53 controls.
  1. Identify the matching Security Hub controls that evaluate your AWS resources.
  1. Export the dated Security Hub findings and keep them with the policy, procedure, and other evidence for that ISO control.
  1. Record gaps where Security Hub cannot test the requirement.[2][3][4]
Cryptography shows how this plays out. ISO control A.8.24 covers the use of cryptography, and Security Hub controls such as  S3.5 ,  S3.17 ,  RDS.3 , and  KMS.4  can evidence encryption in transit, encryption at rest, and key rotation across your resources.[2][4]
Security Hub CSPM control screenshot

What comes back is evidence for one slice of that control rather than the control itself, because A.8.24 also expects a policy that defines when encryption is required, who owns the keys, how exceptions are handled, and how often the arrangement is reviewed.
NIST is careful here too, noting that the crosswalk gives only a general indication of how controls relate, does not establish equivalence, and is not always one to one.[3] Treat it as a bridge rather than a shortcut and it will hold up when an auditor pushes on it.

Keep the evidence boundary larger than AWS

An audit assesses the ISMS, and that boundary can stretch across AWS, other cloud providers, on-premises systems, employee devices, offices, suppliers, and business processes.[1] Inside the AWS part of it, evidence answers questions crisply: whether CloudTrail is enabled, whether storage is encrypted, whether public access is restricted.
Push past that boundary and the questions change character. Whether employee screening was completed, whether supplier agreements carry the right clauses, whether management reviews happened and corrective actions were closed are all answered by records held elsewhere. A clean Security Hub dashboard says something about your AWS configuration; an ISO certificate says something about your management system as a whole.

Takeaway

Use the AWS guide to find the services that support the controls you have declared applicable, then let Security Hub and the NIST crosswalk collect that technical evidence repeatably instead of by hand. AWS can take genuine effort out of proving your technical controls, but deciding where your compliance program begins and ends stays with your organization.

References

[2] AWS Security Hub User Guide, NIST SP 800-53 Revision 5 in Security Hub CSPM.  https://docs.aws.amazon.com/securityhub/latest/userguide/standards-reference-nist-800-53.html 
[3] NIST, SP 800-53 Revision 5, including the ISO/IEC 27001:2022 crosswalk.  https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final 
[4] AWS Security Hub User Guide, Control reference for Security Hub CSPM.  https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-controls-reference.html 
This content publication is assisted by opus-5.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article