home/glossary/accountability of system component

accountability of system component

nounid 164082·updated Oct 22, 2026
candidate

No definition recorded.

MWE

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review
element
e0490
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
from all systems. In such situations, organizations ensure that the inventories include the system-specific information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, software license information, hardware inventory specifications, and - for networked components - the machine names and network addresses for all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include component type, physical location, date of receipt, manufacturer, cost, mothe sentence this term was read in

Proposed during multiword review of this document in the CKI mapping queue.

Attested in

No recorded attestations. They are written when an MWE tagging stage is completed, stamped with the pack version and the document’s digest.

Classifications

Entity Type

Unknown—authoritativecki_proposal_default_pending_classifier

Sensitivity

unclassified

Information Class

unclassified

Variants

plural
accountability of system components
possessive
accountability of system component's
pluralpossessive
accountability of system components'

Framework definitions

No framework-specific definitions
This term has not been bound to a regulatory framework with a sense definition.

Outgoing relationships

No outgoing triples
This term is not the subject of any RDF-style relationship yet.

Incoming relationships

No incoming triples
No other term currently asserts a relationship to this one.