home/glossary/application-level authorized software

application-level authorized software

MWEid 163628·updated Oct 3, 2026
verified

No definition recorded.

Composition

application-level+authorized+software

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:e0478:215-259
element
e0478
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
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
Where the definition came fromawaiting curator confirmation

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 layer-scoped enforcement boundary within an authorized-software (allowlisting) control regime, specifically the granularity at which permitted-execution policy is applied to discrete, named software applications as whole units. It distinguishes coarse-grained controls that identify and permit or deny execution at the application boundary from finer-grained controls operating below that boundary — at the levels of APIs, modules, scripts, system processes, kernel functions, drivers, and dynamic-link libraries. The field uses it as a reference point for characterizing the *depth* of an allowlisting implementation: controls that act only at this layer can be bypassed by malicious code embedded within or loaded by an already-authorized application, which is why standards guidance calls for decomposing and monitoring software at sub-application levels to close that gap.

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.