System Component Inventory is the requirement that makes you know what you have. It is the counterpart to Baseline Configuration (03.04.01): where the baseline captures how the system is configured, the inventory captures what components make up the system. In R2 these two lived together in a single requirement, and R3 split the inventory into System Component Inventory (03.04.10). It has three (3) parts: develop and document an inventory of system components, review and update that inventory on a defined frequency, and update it as part of installations, removals, and system updates. Per the NIST discussion, effective accountability includes information such as system name, software owners and version numbers, license information, hardware specifications, and machine names and network addresses for networked components.
A common difficulty with this requirement is keeping a spreadsheet that is out of date the moment it is saved. An inventory is only useful if it is maintained, and R3 assesses maintenance in two ways: a recurring review and update, and an update tied to every installation, removal, and system update. You cannot protect, patch, or scope what you do not know you have, so this control underpins much of the rest of the framework. For Department of Defense (DoD) contractors, the review frequency is specified.
Where things stand for companies facing the transition from NIST 800-171 R2 to R3:
The following is reproduced verbatim from NIST 800-171 R3, requirement 03.04.10 System Component Inventory. Only the formatting has been adjusted for readability. This requirement has three (3) lettered parts:
The source controls are CM-08 and CM-08(01) from NIST 800-53. The bracketed assignment in part b is the Organization-Defined Parameter (ODP): the review and update frequency. Per the NIST discussion, organizations may use a centralized inventory covering all systems as long as it includes the system-specific information needed for component accountability. You can read the requirement directly at NIST 800-171 R3, 03.04.10 (p. 31).
One (1) value sits inside this requirement. Depending on your contract, your organization may be permitted to define it. Organizations in the DIB subject to CMMC are not, because the DoD has defined it as policy.
The value below comes from Attachment A of the DoD Chief Information Officer (CIO) memorandum dated 10 April 2025 (signed David W. McKeown). The memo identifies each parameter by requirement sub-part, while NIST 800-171A R3 identifies the same parameter by ODP number. Both identifiers appear below so you can match your System Security Plan (SSP) language to either document.
The memo states that its values "will be updated as necessary," so confirm against the current version before writing them into policy.
NIST 800-171A R3 breaks 03.04.10 into seven (7) assessment objectives: one (1) Organization-Defined Parameter (ODP) and six (6) determination statements. These AOs are:
Part b splits into review and update, and part c splits into installations, removals, and system updates, so an inventory that is reviewed annually but never updated after a component removal leaves objectives open. If you are a DoD contractor, the ODP is specified. Per the DoD-specified ODP value in ComplianceForge's NIST 800-171 R3 Transition Guide, the review and update frequency (ODP[01]) is at least quarterly. The full guidance on assessment methods and objects, is in NIST 800-171A R3, 03.04.10 (p. 39).
Examine: configuration management policy and procedures; procedures for system component inventory; configuration management plan; system design documentation; system component inventory; inventory reviews and update records; component installation records; change control records; component removal records; system change records; system security plan.
Interview: personnel with component inventory management responsibilities; personnel with information security responsibilities; system administrators.
Test: processes for managing the system component inventory; mechanisms for supporting or implementing the system component inventory; processes for updating the system component inventory; mechanisms for supporting or implementing the system component inventory updates.
03.04.10 maps from NIST 800-171 R2 requirement 3.4.1 (establish and maintain baseline configurations and inventories of organizational systems, including hardware, software, firmware, and documentation, throughout the respective system development life cycles), specifically the inventory portion that R3 separated out:
Mapped against the seven (7) AOs, one (1) is direct (minimal effort), five (5) are indirect (moderate effort), and one (1) is net new (significant effort), with none having no mapping. The inventory work carries forward from R2 3.4.1, but R3 gives it its own requirement and adds a defined review-and-update frequency. Confirm your inventory maintenance meets the new cadence rather than assuming the old baseline-plus-inventory evidence still fits.
Source Controls in NIST 800-53 R5:
Secure Controls Framework (SCF) Crosswalk
Organizations running a single control set across multiple frameworks can satisfy 03.04.10 through the following SCF controls:
The crosswalks from NIST 800-171 R3 and NIST 800-171A R3 to the SCF are available at no cost through the SCF Set Theory Relationship Mapping (STRM): https://securecontrolsframework.com/start-here/set-theory-relationship-mapping-strm. The STRM also carries the relationship type for each mapping (Equal, Subset Of, Intersects With), which tells you whether an SCF control fully satisfies the requirement or only part of it. Mapping above taken from SCF 2026.3.
The following are issues teams may encounter rather than certainties. They are about maintenance and completeness, each of which needs documented evidence of due diligence and due care such as policies, standards, procedures, and configuration screenshots:
Reasonable objective evidence for an assessment is often subjective. The following examples of evidence to address NIST 800-171 R3 03.04.10 are sourced from the SCF Evidence Request List (ERL), available at https://securecontrolsframework.com/free-content/scf-download. These ERL artifacts are mapped to NIST 800-171 R3 03.04.10 through SCF controls. They establish a starting point for discussions on what an organization needs to have for evidence of due diligence and due care to withstand external scrutiny by an assessor or regulator.
Alongside these, keep the System Security Plan (SSP) narrative for 03.04.10 recording the ODP values you adopted.
With one AO mapping directly, five indirectly, and one net new, 03.04.10 is a moderate lift centered on maintenance. A realistic sequence:
What value does the DoD require for the organization-defined parameter in NIST 800-171 R3 03.04.10? R3 leaves the value to the organization. For the DIB, the DoD set it in the 10 April 2025 memorandum under ODP identifier 03.04.10.b: at least quarterly.
How many assessment objectives does NIST 800-171 R3 03.04.10 have? NIST 800-171A R3 breaks 03.04.10 into seven (7) assessment objectives: one (1) Organization-Defined Parameters (ODPs) and six (6) determination statements. An assessor works through each one separately, so each needs its own evidence.
Which NIST 800-53 R5 controls does NIST 800-171 R3 03.04.10 come from? CM-08, CM-08(01).
Where does NIST 800-171 R3 03.04.10 sit in the NIST 800-171 R3 Kill Chain? Phase 3b, Establish The Compliance Scope. The Kill Chain is a phased model for sequencing R3 implementation, and it assigns this requirement to that phase.
03.04.10 System Component Inventory develops and maintains an inventory of system components, reviews and updates it on a defined frequency, and updates it on installations, removals, and system updates. It maps from the inventory portion of R2 3.4.1 with the establishment objective transitioning directly and the maintenance objectives indirectly, plus a net-new review frequency. The recurring problem is a stale spreadsheet. Build a complete inventory, set the review frequency (for DoD, at least quarterly), and update it both on schedule and on every component change.
Authoritative sources:
Authoritative sources:
This guide reproduces U.S. Government text from NIST 800-171 R3 and NIST 800-171A R3 and references the DoD ODP memorandum of 10 April 2025. It is educational, not legal or assessment advice. Last reviewed: 2026-09-22.
