home/glossary/unsatisfied security requirement

unsatisfied security requirement

MWEid 164436·updated Oct 23, 2026
candidate

No definition recorded.

Composition

unsatisfied+security+requirement

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review
element
e0858
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
Plans of action and milestones (POAMs) are important documents in organizational security programs. Organizations use POAMs to describe how unsatisfied security requirements will be met and how planned mitigations will be implemented. Organizations can document system security plans and POAMs as separate or combined documents in any format. Federal agencies may consider system security plans and POAMs as inputs to risk-based decisions on whether to process, store, or transmit CUI on a system hosted by a nonfederal organization.the 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

No parent term linked
MWE terms inherit classifications from a parent verb or noun. This MWE has no parent linkage; it is classified only by term-type and status.

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.