Examkin

Question

Difficulty: Very hardZero Trust Architecture Principles

A cloud-native software provider operates a microservices workload where internal APIs communicate across multiple environments. A threat actor successfully steals active bearer tokens from a developer workstation located on the internal office LAN. When the attacker uses these stolen tokens to invoke downstream financial data microservices from inside the corporate network, access is denied due to an anomalous device posture score and unverified request velocity. Which core Zero Trust Architecture principle directly prevented this lateral movement despite the presentation of valid authentication credentials from an internal source?

  1. Continuous contextual authorization that dynamically evaluates transaction risk and endpoint health for every microservice requestAnswer
  2. B
    Implicit perimeter trust established once multi-factor authentication successfully validates the user on the internal network segment
  3. C
    Periodic re-authentication of user identity credentials through the central Identity Provider at fixed time intervals
  4. D
    Passive detective intrusion monitoring that logs unauthorized API invocations for post-incident threat hunting

Answer

Continuous contextual authorization that dynamically evaluates transaction risk and endpoint health for every microservice request.
The correct answer highlights continuous contextual authorization. Under Zero Trust Architecture (ZTA), trust is never implicitly granted based on network location or initial login success. Every access request is individually evaluated using real-time signals—such as device security posture, user behavior anomalies, and request velocity—before authorization is granted by the Policy Enforcement Point (PEP).

Step-by-Step Solution

1
Analyze the threat scenario and failure point for the attacker.
The attacker possesses valid authentication tokens and operates from inside the internal corporate network, yet the request is blocked based on contextual anomaly and device health.
This isolates the security mechanism from static perimeter defense or simple token validity check.
2
Map the defensive control to Zero Trust tenets.
Zero Trust assumes breach and requires continuous verification—evaluating every request individually using real-time attributes like user context, device health, location, and request anomalies.
Authenticating once at login or relying on internal network location does not grant persistent access across microservice workloads.
3
Select the option that reflects real-time continuous evaluation.
The option specifying continuous contextual authorization accurately describes the mechanism enforcing policy per request.
It addresses why stolen valid credentials fail when contextual parameters fail policy inspection.

Key Concept

Continuous Verification and Contextual Authorization in Zero Trust Architecture
Rate this question

Topics

Zero Trust Architecture Principles

More questions from this topic