A fintech enterprise is restructuring its cloud-native microservices architecture to mitigate risks associated with lateral movement after a compromised service credential allowed unauthorized database queries. The security engineering team must align service-to-service communication with core Zero Trust Architecture (ZTA) principles. Which implementation strategy best enforces the Zero Trust principles of explicit verification and dynamic access control for every transaction request?
- AEstablishing a persistent IPSec tunnel between the API gateway and database subnet, trusting all internal traffic that originates within the authorized gateway network boundary.
- Configuring the Policy Decision Point (PDP) to continuously evaluate identity attributes, contextual threat intelligence, and resource compliance state before issuing per-request authorization decisions to the Policy Enforcement Point (PEP).Answer
- CAuthenticating the initial caller at the edge proxy via multifactor authentication (MFA) and issuing a long-lived session token that grants implicit authorization across all backend microservices.
- DDeploying an inline network intrusion prevention system (IPS) to terminate TCP sessions exhibiting abnormal database query volume without validating service identity or request authorization tokens.
Answer
Configuring the Policy Decision Point (PDP) to continuously evaluate identity attributes, contextual threat intelligence, and resource compliance state before issuing per-request authorization decisions to the Policy Enforcement Point (PEP).
In a Zero Trust Architecture (ZTA), access decisions are never granted implicitly based on network location or initial login state. Instead, the Policy Decision Point (PDP) continuously evaluates contextual attributes (such as service identity, device compliance, telemetry, and threat risk) for every request, instructing the Policy Enforcement Point (PEP) to enforce fine-grained access control.
Step-by-Step Solution
Key Concept
Zero Trust Architecture Control Plane Separation and Continuous Explicit Verification
Estimated Time:2m 0s