AM-1 Track asset inventory and their risks
Track the asset inventory by discovering and querying all cloud resources, organising them by tagging and grouping, and giving the security organisation access to a continuously updated view.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), AM-1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Continuously refreshed resource inventory · Policy repository / GRC workspace
- Tagging standard and tag compliance reporting · Policy repository / GRC workspace
- Security team access to the inventory · Policy repository / GRC workspace
- Reconciliation between the inventory and billing or discovery data · Policy repository / GRC workspace
First move
Common gaps auditors find
- inventory exported to a spreadsheet quarterly
- untagged resources excluded from reporting
- security team dependent on platform teams for asset data
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet