home/glossary/prior user

prior user

MWEid 163658·updated Oct 4, 2026
verified

No definition recorded.

Composition

prior+user

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review from Jev verdict jev:9a404e19-31b3-452c-805b-7a09013dcbfa:e0898:122-144
element
e0898
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
Preventing unauthorized and unintended information transfer via shared system resources stops information produced by the actions of prior users or roles (or actions of processes acting on behalf of prior users or roles) from being available to current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. Information in shared system resources also applies to encrypted representations of information. In other contexts, the control of information in shared system resources is referred to as object reuse and residual information protection. Information in shared system resources does not address information remanence, which refers to the residual representation of data that has been nominally deleted, covert channels (including storage and timing channels) in which shared system resources are manipulated to violate information flow restrictions, or components within systems for which there are only single users or roles.the sentence this term was read in
Where the definition came fromawaiting curator confirmation

generalized from a web lookup of the quoted expression, with 2 reviewed place(s) it is used as the term Verdict: compositional.

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 relational security concept used to identify the source side of a resource-reuse threat: any principal — whether a human user, an assigned role, or a process acting on behalf of either — whose session has ended and whose allocated system resources (memory, cache, disk sectors, registers, etc.) have been returned to the system for reassignment. The concern is that information produced by the actions of prior users or roles may remain accessible to any current users or roles that obtain access to those shared system resources after the resources have been released back to the system. The phrase appears consistently in the object-reuse and residual-information-protection family of controls, where it anchors the threat model by naming the unintended originator of residual data, as opposed to the successor principal who must be denied access to it. This problem domain is commonly referred to as object reuse and residual information protection, covering shared resources such as registers, cache memory, main memory, and hard disks.

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.