United States

CISA Cloud Security Technical Reference Architecture v2.0

29 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

29 controls 0 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1Purpose, scope, programs and initiatives0
3.1Know the shared responsibility split for every service model and confirm what each vendor does and does not provide0
3.3aContinuously monitor cloud services after authorisation, covering what the provider does not and sharing the work across agencies0
3.3bReport and communicate cloud incidents promptly, including suspected ones0
3.3cDefine the authorisation boundary and settle data location expectations with the provider0
4.1Design software for the cloud with security built in from the start of the life cycle0
4.2Set a cloud migration strategy that weighs challenges, benefits and the right migration pattern per application0
4.3Run each migration through plan, design, pilot, migrate and maintain0
4.4aMake DevSecOps the primary approach, with CI/CD and infrastructure as code0
4.4bTest security automatically in the pipeline and layer expert, third-party and public vulnerability disclosure on top0
4.4cEnforce least privilege, attribute-based access and two-person code review in DevSecOps teams0
4.5aCentralise common cloud services: an agency platform, gold images, artefact repositories, encryption and key services0
4.5bCentralise development tools, public-facing protections and security services such as logging and single sign-on0
4.6Invest in people: train, hire, procure, support staff and give timely access0
5.1Use cloud security posture management continuously and as an enabler of zero trust0
5.2aGovern cloud use against statutes, regulations, policies and standards across the whole service life cycle, and reassess as providers change0
5.2bManage identities, credentials and access across the life cycle with phishing-resistant MFA and granular privileged access0
5.2cProtect data at every stage, type and state: decide what to protect, how much, who controls sharing, and handle termination and sanitisation0
5.2dProtect infrastructure and applications: scan everything, segment networks, harden configurations, shield applications and manage vulnerabilities with a disclosure policy0
5.2eMonitor system health and resources, and keep tested response and recovery plans that use cloud capabilities0
5.3aAdopt posture management capabilities deliberately: native or third-party, independent or integrated, with multi-cloud coverage0
5.3bStructure provider accounts in a hierarchy with central monitoring and separate development and test accounts0
5.3cDecide where authentication happens, federate identity, minimise authentication realms and enforce least privilege with entitlement management0
5.3dRedesign the perimeter around data and segmentation, and place sensors for inbound, outbound and inter-service visibility0
5.3eMonitor compliance, vulnerabilities, availability, misconfigurations and service footprint across regions and providers0
5.3fSecure APIs and microservices: versioning, encryption, keyed and authorised access, gateways and a service mesh with ABAC0
5.3gKnow, validate, synchronise and centralise logs and telemetry to meet federal logging requirements0
5.3hDeploy through automation: integrated DevSecOps, golden images, zero-downtime replacement, vetted dependencies, infrastructure as code, key management and drift control0
6Conclusion and scenarios0

Tell me when CISA Cloud Security Technical Reference Architecture v2.0 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for CISA Cloud Security Technical Reference Architecture v2.0, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition