`ID.AM-02` Inventories of software, services, and systems managed by the organization are maintained

Q: What evidence do auditors commonly ask for on ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained?

Software inventory with licensing and version data; SaaS application register with owner and data class; Allowlist and denylist with review cadence; Discovery feed from endpoint and network tools; Quarterly software lifecycle review.

Inventories of software, services, and systems managed by the organization are maintained. Control from NIST Cybersecurity Framework 2.0 framework, domain: ID - Identify.

Source: NIST CSF 2.0, ID.AM-02. 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 NIST CSF 2.0 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Quarterly software lifecycle review · Document repository

governing documentDocuments that govern the control

Software inventory with licensing and version data · Policy repository / GRC workspace
SaaS application register with owner and data class · Policy repository / GRC workspace
Allowlist and denylist with review cadence · Policy repository / GRC workspace
Discovery feed from endpoint and network tools · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Shadow SaaS not captured
Allowlist drift over time
Versioning unreliable for plugins
Lifecycle review not performed

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

ID.AM-01 Inventories of hardware managed by the organization are maintained · ID.AM-03 Representations of the organization's authorized network communication and internal and external network data…