In a zero trust model, why is a user re-authenticated and re-authorised for each resource request instead of being granted broad access after one successful login?
- ABecause re-authentication is mandated by the DHCP lease renewal process whenever a host changes subnet.
- BBecause zero trust issues one single sign-on token at the perimeter that stays valid and does not expire.
- CBecause zero trust assumes any session or credential could be compromised, so it applies continuous verification with least-privilege access. Correct
- DBecause the CIA triad requires availability to be prioritised above confidentiality on every single request.
Why A is wrong: DHCP lease renewal is an addressing function unrelated to authorisation, so it does not drive the per-resource access decisions that zero trust makes.
Why B is wrong: A non-expiring perimeter token is the opposite of zero trust, because continuous re-verification exists so a stale or stolen token cannot grant lasting access.
Why C is correct: Zero trust assumes breach and grants the minimum access needed, so it re-verifies identity, device, and context on each request rather than trusting one login.
Why D is wrong: This misapplies the CIA triad, because availability and confidentiality are goals rather than the reason for per-request checks, which stem from assuming compromise.