An enterprise organization is establishing a micro-segmented hybrid environment based on Zero Trust Architecture (ZTA) control plane and data plane principles. Match each logical Zero Trust component on the left with its correct operational responsibility on the right.
- Policy Engine (PE)Evaluates contextual signals, trust criteria, and security rules to determine whether access to a requested resource should be granted, denied, or revoked.
- Policy Administrator (PA)Executes policy decisions by issuing dynamic session credentials and sending signals to set up or tear down encrypted communication paths.
- Policy Enforcement Point (PEP)Functions in the data plane to directly inspect, route, initiate, or terminate network connections between client subjects and enterprise workloads.
Answer
Policy Engine (PE) matches with evaluating contextual signals and determining access decisions; Policy Administrator (PA) matches with issuing dynamic credentials and signaling path setups; Policy Enforcement Point (PEP) matches with operating in the data plane to inspect traffic and enforce access boundaries.
Under NIST SP 800-207, Zero Trust architecture divides functions between the control plane and data plane. The Policy Engine evaluates trust inputs to decide access. The Policy Administrator communicates control decisions by managing credentials and signaling gateways. The Policy Enforcement Point sits on the data plane to enforce session bounds.
Step-by-Step Solution
Key Concept
Logical Components of Zero Trust Architecture (Policy Engine, Policy Administrator, Policy Enforcement Point)
Estimated Time:2m 0s