Examkin

Soru

Zorluk: OrtaZero Trust Architecture Principles

In a Zero Trust Architecture (ZTA) implementation following NIST SP 800-207, distinct logical components handle policy decisions, enforcement, and data boundaries. Match each Zero Trust functional component on the left with its core operational responsibility on the right.

  • Policy Engine (PE)Evaluates contextual signals, trust criteria, and enterprise policy to render explicit access grant or denial decisions.
  • Policy Administrator (PA)Signals the enforcement mechanism to open or close communication paths and issues short-lived access credentials.
  • Policy Enforcement Point (PEP)Directly intercepts, gates, and monitors active application connections between subjects and enterprise resources.
  • Control PlaneServes as the administrative communication network used by security components to coordinate access control commands.

Cevap

The Policy Engine maps to evaluating contextual risk and policy to render access decisions; the Policy Administrator maps to signaling enforcement points and issuing session credentials; the Policy Enforcement Point maps to intercepting and gating resource connections; the Control Plane maps to serving as the administrative communication network for management traffic.
NIST SP 800-207 specifies a clear separation of responsibilities within Zero Trust Architecture: the Policy Engine acts as the decision brain, the Policy Administrator serves as the control dispatcher issuing dynamic credentials, the Policy Enforcement Point mediates raw application data flows, and the Control Plane establishes the secure administrative network connecting PDP and PEP entities.

Adım Adım Çözüm

1
Identify the primary role of the Policy Engine within the Policy Decision Point (PDP).
The Policy Engine serves as the decision maker, utilizing enterprise rules and dynamic trust scores to decide if access should be granted.
Zero Trust separates the decision logic from the execution and enforcement layers.
2
Identify the operational execution role of the Policy Administrator.
The Policy Administrator translates the Policy Engine's approval into actionable commands, issuing control signals and temporary credentials.
The Policy Administrator acts as the execution controller that communicates with the enforcement points.
3
Determine where the Policy Enforcement Point (PEP) operates.
The PEP operates on the data plane, physically or logically gating subject-to-resource connection requests.
PEPs act as gatekeepers that enforce decisions passed down from the PDP.
4
Distinguish the Control Plane from the Data Plane.
The Control Plane isolates administrative signaling and component-to-component management communication from user data traffic.
Decoupling control signals from payload traffic prevents unauthorized access to management interfaces.

Anahtar Kavram

Zero Trust Architecture Logical Components (PDP, PEP, Control Plane)
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Zero Trust Architecture Principles

Bu konudan daha fazla soru