comprehensive authorized software process
163627·updated Oct 3, 2026A compositional phrase, not a term of art. The words "comprehensive," "authorized software," and "process" each carry their ordinary security-configuration meanings — respectively, covering multiple levels of abstraction, limiting execution to explicitly permitted code, and the organizational lifecycle (identification, enforcement, and periodic review) for doing so. The phrase describes the goal that an allowlisting program should span all software layers (applications, modules, APIs, system services, kernel functions, drivers, etc.) rather than operating only at the application level, but it is not defined, scoped, or used as a standalone concept anywhere in the standards corpus.
Source
Authorized software programs can be limited to specific versions or come from specific sources. To facilitate a comprehensive authorized software process and increase the strength of protection against attacks that bypass application-level authorized software, software programs may be decomposed into and monitored at different levels of detail. These levels include applications, application programming interfaces, application modules, scripts, system processes, system services, kernel functions, registries, drivers, and dynamic link libraries.the sentence this term was read in
generalized from a web lookup of the quoted expression, with 1 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 compositional phrase, not a term of art. The words "comprehensive," "authorized software," and "process" each carry their ordinary security-configuration meanings — respectively, covering multiple levels of abstraction, limiting execution to explicitly permitted code, and the organizational lifecycle (identification, enforcement, and periodic review) for doing so. The phrase describes the goal that an allowlisting program should span all software layers (applications, modules, APIs, system services, kernel functions, drivers, etc.) rather than operating only at the application level, but it is not defined, scoped, or used as a standalone concept anywhere in the standards corpus.
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
Classifications
Entity Type
Sensitivity
Information Class
Variants
- plural
- comprehensive authorized software processes
- possessive
- comprehensive authorized software process's
- pluralpossessive
- comprehensive authorized software processes'
Framework definitions
- §1 · attested_usage_reviewer_confirmed
- No definition is given in NIST SP 800-171r3. The term is attested in use at 1 citation in that document; a definition is pending curation.Increment 2: attested in NIST SP 800-171r3 without a glossary definition.
- §1 · web_lookup_draft
- A compositional phrase, not a term of art. The words "comprehensive," "authorized software," and "process" each carry their ordinary security-configuration meanings — respectively, covering multiple levels of abstraction, limiting execution to explicitly permitted code, and the organizational lifecycle (identification, enforcement, and periodic review) for doing so. The phrase describes the goal that an allowlisting program should span all software layers (applications, modules, APIs, system services, kernel functions, drivers, etc.) rather than operating only at the application level, but it is not defined, scoped, or used as a standalone concept anywhere in the standards corpus.Drafted by the propose-term web lookup (PD-018); a curator confirms or replaces it.