home/glossary/organization-defined time period

organization-defined time period

MWEid 163500·updated Aug 30, 2026
verified

No definition recorded.

Composition

organization-defined+time+period

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review
element
e0152
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
The accounts have been inactive for [ Assignment: organization-defined time period ],the sentence this term was read in
Where the definition came fromawaiting curator confirmation

generalized from a web lookup of the quoted expression at proposal time Verdict: term of art.

A definition generalized from search results is a draft to react to, not provenance. Confirm it against an authority document before this term is verified.

A web lookup ran when this term was proposed

A **time-typed organization-defined parameter (ODP)** — a placeholder embedded in a security or privacy control statement that a deploying organization must replace with a concrete duration or interval during the control-tailoring process. Per the NIST Computer Security Resource Center glossary (sourced from NIST SP 800-37 Rev. 2 and SP 800-53 Rev. 5), an organization-defined control parameter is "the variable part of a control or control enhancement that can be instantiated by an organization during the tailoring process by either assigning an organization-defined value or selecting a value from a pre-defined list." "Organization-defined time period" is the time-dimensioned instance of that class of parameter: many NIST controls are not "complete" as published but require "fill in the blanks," and those blanks are called Organization-Defined Values or Organization-Defined Parameters. In practice it appears across a wide range of control families — account management, audit retention, identifier reuse, lockout windows, and more — wherever the standard mandates a time-bounded obligation but deliberately leaves the specific duration to organizational risk and policy judgment: for example, enforcing a limit on consecutive invalid logon attempts "during a [Assignment: organization-defined time period]" and then locking the account "for [Assignment: organization-defined time period]"; preventing "the reuse of identifiers for [Assignment: organization-defined time period]"; and disabling a user identifier "after [Assignment: organization-defined time period] of inactivity."

Advisory only. A term this product ships is defined by an authority document, not by a search result.

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.