A.5.9 Organizational
Inventory of information and other associated assets
Structured attributes from ISO/IEC 27002:2022 — control type · CIA properties · cybersecurity concept · operational capability · security domain. What do these mean?
Mapped NIST 800-53 r5 controls (15)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- CM-8partialcovers — A.5.9's broad asset inventory requirement (information + associated assets, with ownership) accounts for the bulk of CM-8's system component inventory but leaves a residual: CM-8's system-specific, non-duplicative, granularity, and accountability details are narrower and more prescriptive than the general asset inventory in A.5.9.
Aligned NIST CSF 2.0 outcomes (21)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- ID.AM-01explicit mandateimplements — A.5.9 directly operationalizes the maintenance of asset inventories that ID.AM-01 requires (hardware is a core subclass of the assets A.5.9 names and owns)
- ID.AM-02explicit mandateimplements — A.5.9's defined purpose is to maintain an inventory of information and associated assets (including systems/services/software); this directly operationalizes the exact outcome named in ID.AM-02
- ID.AM-05domain mandateimplements — A.5.9's inventory+ownership process directly operationalizes the asset-prioritization outcome in ID.AM-05; classification/criticality/impact are assigned and used during that inventory, making the technical control the primary means that gives effect to the governance outcome within the asset-management domain
- ID.AM-07explicit mandateimplements — A.5.9's defined purpose is exactly to maintain asset inventories (including data) and assign ownership; this directly operationalizes the CSF outcome that inventories of data and metadata are maintained.
- ID.AM-08domain mandateimplements — A.5.9's inventory process directly operationalizes the asset life-cycle management outcome named in ID.AM-08 (identification and ownership are core early phases of any asset life cycle); the link is within the shared asset-management domain but not by explicit citation of life-cycle stages.
Related OWASP ASVS 5.0 requirements (8)
Application-security verification requirements (OWASP ASVS 5.0) this ISO control aligns with; links open the ASVS chapter. Our analysis (mostly llm_verified) — many ISO controls have no ASVS counterpart.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Mitigated MITRE ATT&CK techniques (3245)
Adversary techniques (MITRE ATT&CK Enterprise) this ISO control helps mitigate; links open attack.mitre.org. Our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Prevented OWASP Web Top 10 (2025) risks (3)
OWASP Web Top 10 (2025) risk categories this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Control IDs, short titles and the structured attribute table (control type, CIA properties, cybersecurity-concept, operational capability, security domain) are facts from ISO/IEC 27001:2022 Annex A / ISO/IEC 27002:2022. The full implementation guidance prose lives in ISO/IEC 27002:2022 — not reproduced here. Cross-walks to NIST 800-53, NIST CSF 2.0, OWASP ASVS, CWE, MITRE ATT&CK and OWASP Web Top 10 are our own analysis (mostly llm_verified), not an ISO, NIST, MITRE or OWASP product — how ours compare.