CISA Cloud Security Technical Reference Architecture v2.0
Section 5: Cloud security posture management – CISA Cloud Security Technical Reference Architecture v2.0

CISA Cloud Security Technical Reference Architecture v2.0 5.3c: Decide where authentication happens, federate identity, minimise authentication realms and enforce least privilege with entitlement management

What does 5.3c require?

One of the first architecture decisions is how and where authentication is performed, guided by the digital identity guidelines, the federal zero trust strategy and the identity playbooks: a federated identity provider serves multiple clouds and on-premises resources, multi-factor authentication is checked against government requirements such as PIV or phishing resistance, identity and assessment logs feed a SIEM so alerts trigger on selected activity and automated corrections and rollbacks follow, authentication realms are carefully managed and reduced (platform services remove server-level realms), least privilege is enforced within each realm with assessments detecting over-privileged accounts, and cloud infrastructure entitlement management is considered to enforce least privilege and monitor authorisations.

Maintained by Gerard Blokdyk

Other controls in Section 5: Cloud security posture management – CISA Cloud Security Technical Reference Architecture v2.0

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.