1. Home
  2. |
  3. Reference Library
  4. |
  5. Policy Enforcement Point (PEP)

FAQ

A Policy Enforcement Point (PEP) enforces authorization decisions to control access to protected resources. It intercepts access requests, communicates with a Policy Decision Point (PDP), and allows or blocks access based on the returned decision. This separates authorization enforcement from policy evaluation.

No, a PEP and a PDP perform different functions within an authorization architecture. The PDP evaluates authorization policies and determines whether access should be permitted or denied. The PEP enforces that decision at the point where access is requested.

Both components work together to ensure access requests comply with defined security policies.

A PEP can be deployed wherever access control must be enforced, including applications, APIs, microservices, API gateways, and other protected systems. Depending on the architecture, PEP functionality may be implemented through application code, middleware, gateways, or dedicated enforcement components.

Yes, PEPs are an important component of Zero Trust architectures because they enforce access decisions at protected resources. When integrated with context-aware authorization policies, PEPs can enforce decisions that consider identity, device posture, resource sensitivity, and other relevant conditions. This helps organizations move beyond relying solely on network location or static permissions.

Typically, no. In an externalized authorization architecture, the PEP requests and enforces authorization decisions, while the PDP evaluates the policies. The PEP may collect request information and perform enforcement-related functions, but the policy evaluation logic is generally handled by the PDP.

Related articles

This website uses cookies

Cookies consist of small text files. They contain data that is stored on your device. To enable us to place certain types of cookies we need to obtain your consent. At Axiomatics AB, corp. ID no. 556708-1012, we use the following kinds of cookies. To read more about which cookies we use and storage times, click here to access our cookies policy.

Manage your cookie-settings

Necessary cookies

Check to consent to the use of Necessary cookies

Nödvändiga cookies

Cookie Syfte Lagringstid
consents

Används för att hantera samtycke

1 år
__hssrc

Närhelst HubSpot ändrar sessionscookien, ställs denna cookie också in för att avgöra om besökaren har startat om sin webbläsare.

Session

Cookies for statistics

Check to consent to the use of Cookies for statistics

Cookies för statistik

Cookie Syfte Lagringstid
__hssc

För att lagra anonymiserad statistik.

30 minuter
_gcl_au

För att lagra och spåra konverteringar.

3 månader

 

Cookies for ad-tracking

Check to consent to the use of Cookies for ad-tracking

Cookies för annonsmätning

Cookie Syfte Lagringstid
__hstc

För att lagra besökstid.

6 månader
hubspotutk

För att lagra och spåra en besökares identitet.

6 månader

 

Ad measurement user cookies

Check to consent to the use of Ad measurement user cookies
In order to show relevant ads we place cookies to tailor ads for you

Personalized ads cookies

Check to consent to the use of Personalized ads cookies
To show relevant and personal ads we place cookies to provide unique offers that are tailored to your user data