An enterprise cloud application utilizes a service mesh architecture to handle communication between internal microservices. To reduce authentication overhead and improve performance, a DevOps engineer proposes issuing a persistent session token after an initial mTLS handshake, allowing subsequent microservice calls to bypass per-request authorization checks. Which of the following statements best explains why this proposed design violates core Zero Trust Architecture principles?
- It creates implicit trust within the internal communications boundary by assuming prior authentication remains valid for subsequent transactions without continuous verification.Cevap
- BIt shifts Policy Decision Point (PDP) functionality directly into the data plane layer rather than isolating trust evaluation logic within the Policy Enforcement Point (PEP).
- CIt relies on transport-layer cryptographic handshakes to validate application privilege levels instead of using identity-aware access tokens.
- DIt assumes inter-service traffic is inherently secure due to perimeter boundary filtering, bypassing inline microsegmentation controls.
Cevap
The proposed design violates Zero Trust Architecture principles because it establishes implicit trust across subsequent requests within the service mesh by assuming prior authentication remains valid without continuous per-request evaluation.
Zero Trust Architecture (ZTA) mandates that no implicit trust is granted based on past authentication or internal network positioning. Every transaction and inter-service call must be individually evaluated and authorized continuously in real time using contextual signals.
Adım Adım Çözüm
Anahtar Kavram
Continuous Explicit Verification and Elimination of Implicit Trust in Zero Trust Architecture
Tahmini Süre:2m 30s