Software Inventory: Knowing what software touches patient data

If you have been asked for evidence of software inventory, the framework outcome behind the question is NIST CSF 2.0 ID.AM-02. What follows is what it says, what satisfies it, and where organizations usually come up short.

What the framework says

NIST CSF 2.0 ID.AM-02 sets the expectation for software inventory. The framework describes the outcome rather than prescribing a technology, so the question is whether your implementation achieves it and whether you can show that it does.

What this looks like in practice

On the ground, NIST CSF 2.0 ID.AM-02 is not one check. It resolves into several questions, and each one is really asking for different evidence:

• Does the organization maintain an inventory of the software, services, and systems it manages?

Ownership usually sits with the IT or security team, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

NIST CSF 2.0 is voluntary rather than binding, and that changes how it should be used. Adopting it does not create a legal obligation, and declining it is not a violation. It earns its place when a customer contract names it, when it gives structure to a program HIPAA describes only in outcomes, or when a recognized practice is worth having on record. Treat it as a way of organizing work you already owe, if HIPAA applies to you, not as a second regime.

Building it, in order

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Maintain a current inventory of software, services, and systems in use.
2. Keep it updated as software is added, changed, or retired.
3. Record the inventory and how it is kept current.

Evidence an assessor asks for

For this outcome the evidence types that satisfy it are inventory. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. No federal rule sets a retention period for a voluntary framework document, so this is our recommendation rather than a requirement: keep six years, because that is what HIPAA requires of the documentation this work usually overlaps with (45 CFR 164.316(b)(2)(i) for security documentation, 164.530(j)(2) for privacy), and holding two sets of dates is how the earlier one goes missing.

Where this usually goes wrong

The usual gap is a control that exists in practice and nowhere in writing. Someone does the work, reliably, and it has never been written down, so the organization cannot demonstrate it and cannot notice when it stops. The fix is not more control, it is a dated record and a named owner.

What to do about it

• Produce the evidence, not the intention. For NIST CSF 2.0 ID.AM-02 that means an inventory with an owner and a last-reviewed date on every row. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Whoever administers the systems should be recorded as the owner. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Set a review cadence and keep the evidence of each review. An annual date with a dated output is a common floor; what fails an assessment is a control implemented once and never re-checked against a changed environment.
• Do not treat this as a legal obligation. It is a voluntary framework. Adopt it where a customer contract names it or where it gives structure to something HIPAA describes only as an outcome, and say in your own documentation which of those reasons applies.

The practical test for NIST CSF 2.0 ID.AM-02 is whether someone unfamiliar with your organization could read your documentation and tell what you do, who does it, and when it last happened. If they can, the documentation will hold up; whether the outcome is met is a judgment about what it shows, and your counsel owns that conclusion. If they need you in the room to explain it, it will not.

Related outcomes

• Hardware Inventory: An asset inventory that stays current
• Asset Prioritization: Prioritizing assets by clinical impact
• Strategy Review: Reviewing the program against measured outcomes

References

• ID.AM-02, in NIST Cybersecurity Framework 2.0. This is a voluntary framework, not a legal requirement.
• This post describes what a framework outcome asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose additional obligations of its own.