policy engine
A component that takes a subject, an action and a resource and answers whether the request is allowed according to written rules.
In more detail
Putting rules in one engine keeps decisions consistent and testable instead of scattering checks through the code. In a zero trust architecture the policy engine also weighs signals such as device health and threat intelligence, and a policy administrator carries out its decision. Applications usually consult it on every request.
Related terms
- zero trust — A security approach where no user, device or network location is trusted by default, and every request is checked on its own merits.
- policy administrator — In a zero trust architecture, the component that acts on the policy engine's decision by opening or closing the path between a user and a resource.
- policy enforcement point — In a zero trust architecture, the gatekeeper in the data path that lets a request through to a resource or blocks it, as instructed.
- attribute-based access control — An authorization model that decides each request from attributes of the subject, the resource and the environment, such as owner, department or time of day.
- role-based access control — An authorization model where permissions are grouped into named roles, such as reader or editor, and people or services are given roles.
- middleware — Code that sits between an incoming request and the handler that answers it, doing a shared job such as logging, authentication or rate limiting.
Taught in
- CIA Triad, Non-Repudiation & Parkerian Hexad — Cybersecurity Fundamentals, GRC & Cryptography
- Role-Based & Attribute Access Control: RBAC & ABAC — Production Full-Stack Engineering