access control policy
A governing statement or set of rules — situated at the policy layer of a security architecture, above implementation mechanisms — that defines which subjects (users, processes, or roles) are permitted to perform which operations on which objects (files, devices, records, domains, or other resources), and under what conditions. Organizations implementing access control systems distinguish three abstractions — policies, models, and mechanisms — with access control policies being the high-level requirements that specify how access is managed and who may access information under what circumstances. Policies may pertain to resource usage within or across organizational units, or may be based on need-to-know, competence, authority, obligation, or conflict-of-interest factors. In practice the term names a recognized category of security artifact that can be instantiated in several named paradigms: identity-based, role-based, and attribute-based policies are all enumerated types, each paired with a corresponding enforcement mechanism such as access control lists, matrices, or cryptography.
Senses
No definition is given in NIST SP 800-171r3. The term is attested in use at 2 citations in that document; a definition is pending curation.
A governance instrument — sitting above models and mechanisms in the access-control abstraction stack — that states the high-level rules an organization adopts to determine which subjects (users or processes) may perform which operations on which objects (files, devices, records, domains). NIST places it as one of three design abstractions — policies, models, and mechanisms — where the policy layer supplies "high-level requirements that specify how access is managed and who may access information under what circumstances." In practice it takes named forms — identity-based, role-based, or attribute-based — and is paired with enforcement mechanisms such as access-control lists, matrices, or cryptography to mediate access between users or processes and objects such as devices, files, records, and domains. Specifying one is treated as a non-trivial engineering problem in its own right, because a system's security is more often compromised by access-control policy misconfiguration than by failures of cryptographic primitives.
Classifications
Entity Type
Sensitivity
Information Class
Variants
- plural
- access control policies
- possessive
- access control policy's
- pluralpossessive
- access control policies'