An enterprise health system is updating its clinical application platform to align with Zero Trust Architecture (ZTA) principles. During an architectural review, an engineer proposes that once a medical professional completes multi-factor authentication (MFA) at the central identity provider (IdP) and receives a session token, all subsequent API requests sent to internal microservices during their 8-hour shift should be implicitly trusted without re-assessing device posture or access policies. Which core Zero Trust Architecture principle does this proposed design fail to uphold?
- Continuous verification, because access requests must be evaluated dynamically on a per-request basis using contextual signal inputs rather than relying on initial authentication success.Cevap
- BControl plane isolation, because internal microservice communication must rely on traditional perimeter firewalls to establish trust boundaries across corporate zones.
- CLeast privilege enforcement, because multi-factor authentication mechanisms determine user permissions rather than verifying identity credentials.
- DExplicit validation, because session tokens issued by an identity provider function strictly as detective controls rather than preventive access controls.
Cevap
Continuous verification, because access requests must be evaluated dynamically on a per-request basis using contextual signal inputs rather than relying on initial authentication success.
The correct option accurately identifies continuous verification as the missing principle. Zero Trust dictates that no implicit trust is granted based on network location or initial authentication. Every transaction must be continuously authorized using real-time contextual attributes (e.g., identity, device security posture, anomalous behavior patterns).
Adım Adım Çözüm
Anahtar Kavram
Zero Trust Continuous Verification
Tahmini Süre:2m 0s