trio.so
Explained

Policy Enforcement Point (PEP): What It Is and How It Works in Zero Trust

What a policy enforcement point (PEP) is, how it works with the PDP, PIP and PAP, where it sits in NIST zero trust architecture, and common PEP types.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A policy enforcement point (PEP) is the component that sits between a user or device and a protected resource and carries out the access decision: it lets the request through, blocks it, or ends a session that is already open. It does not make the decision itself. It sends the request to a policy decision point (PDP), which checks it against the organization's policies, and then enforces the answer. In NIST's zero trust architecture (SP 800-207), the PEP is the gate in the data path, while the policy engine and policy administrator behind it make up the PDP. In practice a PEP is an identity-aware proxy, an API gateway, a network gateway or an agent on the device.

If you met the term in a zero trust design, an exam or an audit and want to see how the pieces fit together, the components table and the request flow below show it in one pass.

Policy Enforcement Point vs. Policy Decision Point

The two names describe a split of duties that goes back to XACML, the OASIS standard for access control policies. One component decides, the other acts. Keeping them apart means the rules live in one place and can be enforced in many.

Policy Decision Point (PDP): The Brain Behind the Operation

The PDP evaluates each access request against the policies that apply to it and returns a decision, usually permit or deny, sometimes with conditions. NIST SP 800-162 describes it as the component that "computes access decisions by evaluating the applicable digital policies". To decide, it uses facts about the request: who is asking, from which device, for which resource, and in what context.

Policy Enforcement Point (PEP): The Action Taker

The PEP intercepts the request, asks the PDP, and enforces the result. NIST's glossary puts it plainly: it "enforces policy decisions in response to a request from a subject requesting access to a protected object; the access control decisions are made by the policy decision point." If the decision is deny, the request never reaches the resource. If it is permit, the PEP opens the connection and, in a zero trust design, keeps watching it so it can be cut off later.

For example, when an employee opens an internal finance app, the request goes to a gateway in front of the app (the PEP). The gateway asks the PDP, which checks the user's role, the device's state and the time of day, and answers. The gateway then lets the session through or returns an access denied page.

The four XACML components: PEP, PDP, PIP and PAP

Two more components complete the model, and most PEP and PDP explanations refer to them:

ComponentWhat it doesExample
Policy enforcement point (PEP)Intercepts the request and enforces the decisionAn identity-aware proxy in front of a web app
Policy decision point (PDP)Evaluates the request against policy and returns permit or denyThe policy engine in an identity provider or a zero trust service
Policy information point (PIP)Supplies the facts the PDP needsThe user directory, an HR system, device management or threat intelligence
Policy administration point (PAP)Where policies are written and managedThe admin console where security teams define access rules

The Role of Policy Enforcement Points in Zero Trust Security

In a zero trust architecture, no user or device is trusted because of where it sits on the network. Every request to a resource is checked, and the PEP is where that check is enforced. NIST SP 800-207 describes three logical parts:

  • The policy engine (PE) makes the decision to grant, deny or revoke access to a resource.
  • The policy administrator (PA) carries the decision out by setting up or shutting down the communication path between the subject and the resource, and tells the PEP what to do.
  • The policy enforcement point (PEP) enables, monitors and terminates the connection between the subject and the resource.

Together, the policy engine and the policy administrator form the PDP. Everything on the resource side of the PEP is the implicit trust zone; everything before it is not trusted until the PDP says so. NIST also notes that the PEP can be one component or two: an agent on the user's device and a gateway in front of the resource, working together.

Dynamic Policy Enforcement

Zero trust decisions are made per request, not once at sign-in. The PDP can take into account the user's identity, the device's health (for example, whether it is managed, encrypted and patched), the location and the sensitivity of the resource. If any of those change during a session, such as a device falling out of compliance, the PDP can revoke access and the PEP ends the connection.

Attribute-Based Access Control (ABAC)

Many PEP and PDP setups use attribute-based access control: policies are written as conditions on attributes of the user, the resource and the environment rather than as fixed lists of who can access what. A rule such as "finance staff can open payroll records from company-managed devices during working hours" is an ABAC policy. The PEP enforces it the same way for every request, and the PIP supplies the attributes.

For instance, a financial firm might let employees open customer account data only from company devices that meet its security baseline. The same employee on a personal laptop is denied, or gets read-only access, depending on the policy.

Policy Enforcement Point Capabilities

Whatever form it takes, a PEP needs a few capabilities to do its job well.

Comprehensive Authorization Management

A PEP intercepts every request to the resources it protects, asks the PDP and applies the answer, including conditions such as step-up authentication or read-only access. It should fail closed: if it cannot reach the PDP, it denies access rather than letting requests through. It should also log each decision, so security teams can see who was allowed in and who was refused.

Scalable Deployment Across Systems

Because the decision logic lives in the PDP, PEPs can be placed wherever resources are: in front of web apps, at API gateways, at network edges, inside cloud services and on endpoints. Open source tools are common here, for example API gateways and service meshes that can call an external authorization service, alongside commercial zero trust network access (ZTNA) products.

Policy Enforcement Point Example

A hospital runs a cloud-based patient records system. A doctor opens it from a clinic workstation. The request reaches an identity-aware proxy in front of the system (the PEP), which asks the PDP. The PDP checks the doctor's identity and role, whether the workstation is a managed and compliant device, and whether the request comes from an expected network. If all conditions pass, the proxy lets the session through; if the device fails a check, access is denied and the attempt is logged.

How a request flows through a PEP

  1. A user or service requests a resource.
  2. The PEP intercepts the request before it reaches the resource.
  3. The PEP sends the request and its context to the PDP.
  4. The PDP pulls the facts it needs from PIPs, such as the directory and device management, and evaluates the policies written in the PAP.
  5. The PDP returns permit, deny or permit with conditions.
  6. The PEP enforces the answer: it opens the connection, refuses it, or asks for more proof such as MFA.
  7. While the session is open, the PEP keeps monitoring and ends it if the PDP revokes access.

Types of policy enforcement points

PEPs come in several forms, and a zero trust design usually uses more than one:

  • Identity-aware proxy or access gateway: sits in front of web applications and checks each request against identity and device signals.
  • API gateway: enforces authorization on API calls between services or from apps.
  • Network gateway or ZTNA connector: controls which users and devices can reach which private applications, instead of opening the whole network through a VPN.
  • Endpoint agent: enforces decisions on the device itself, often paired with a gateway as NIST's agent and gateway model describes.
  • Application or database layer: code inside an application that asks a PDP before returning sensitive records.

So what is the best policy enforcement point for zero trust? There is no single answer: the best PEP is the one closest to the resource it protects that can see every request to it. For web apps that is usually an identity-aware proxy; for APIs, an API gateway; for private network services, a ZTNA connector; and for data on the device, an endpoint agent. Many organizations use all four, with one central PDP so the policies stay consistent.

How Policy Enforcement Points Strengthen Enterprise Security

PEPs turn access policy from a document into something that happens on every request. They help in three ways.

Preventing Unauthorized Access

Because every request passes through a PEP, a stolen password alone is not enough when the policy also requires a known, healthy device or MFA. Placing PEPs close to each resource also limits how far an attacker can move after getting in. For the common ways attackers get in, see unauthorized access to computer systems.

Supporting Compliance Goals

Frameworks such as HIPAA, PCI DSS and ISO/IEC 27001 expect access to sensitive data to match each person's role and to be logged. PEPs enforce those rules the same way every time and record each decision, which gives auditors evidence that access control works in practice. They support a compliance program; they do not make an organization compliant on their own.

Facilitating Zero Trust Principles

Zero trust asks you to verify explicitly, use least privilege and assume breach. PEPs are where all three meet the traffic: each request is verified, access is limited to what the policy allows, and sessions can be cut off as soon as something changes. See the least privilege access model, network segmentation and defense in depth for the controls around it, and zero trust architecture for the full model.

Conclusion: Strengthen Your Security with Policy Enforcement Points

A policy enforcement point is the gate that carries out access decisions: it intercepts each request, asks the policy decision point, and enforces the answer. In NIST's zero trust architecture it sits in the data path, with the policy engine and policy administrator behind it, and it can take the form of a proxy, a gateway, a connector or an agent. Put PEPs as close to your resources as you can, keep the decisions in one PDP, and feed it good information about users and devices.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

The component that intercepts a request for a protected resource, asks a policy decision point whether to allow it, and enforces the answer by allowing, denying or ending the connection.

The PDP decides whether a request should be allowed by evaluating it against policy. The PEP enforces that decision in the path between the user and the resource. One decides, the other acts.

The four parts of the XACML access control model: the policy enforcement point enforces decisions, the policy decision point makes them, the policy information point supplies the facts, and the policy administration point is where policies are written.

It depends on the resource. An identity-aware proxy suits web apps, an API gateway suits APIs, a ZTNA connector suits private network services and an endpoint agent suits the device itself. Most designs combine several with one central decision point.

In the data path between the subject and the resource. In NIST SP 800-207, the PEP enables, monitors and ends connections, while the policy engine and policy administrator behind it form the policy decision point.

Related

From the blog

The related industry news, interviews, technologies, and resources.