1 | Purpose, scope, programs and initiatives | 0 |
3.1 | Know the shared responsibility split for every service model and confirm what each vendor does and does not provide | 0 |
3.3a | Continuously monitor cloud services after authorisation, covering what the provider does not and sharing the work across agencies | 0 |
3.3b | Report and communicate cloud incidents promptly, including suspected ones | 0 |
3.3c | Define the authorisation boundary and settle data location expectations with the provider | 0 |
4.1 | Design software for the cloud with security built in from the start of the life cycle | 0 |
4.2 | Set a cloud migration strategy that weighs challenges, benefits and the right migration pattern per application | 0 |
4.3 | Run each migration through plan, design, pilot, migrate and maintain | 0 |
4.4a | Make DevSecOps the primary approach, with CI/CD and infrastructure as code | 0 |
4.4b | Test security automatically in the pipeline and layer expert, third-party and public vulnerability disclosure on top | 0 |
4.4c | Enforce least privilege, attribute-based access and two-person code review in DevSecOps teams | 0 |
4.5a | Centralise common cloud services: an agency platform, gold images, artefact repositories, encryption and key services | 0 |
4.5b | Centralise development tools, public-facing protections and security services such as logging and single sign-on | 0 |
4.6 | Invest in people: train, hire, procure, support staff and give timely access | 0 |
5.1 | Use cloud security posture management continuously and as an enabler of zero trust | 0 |
5.2a | Govern cloud use against statutes, regulations, policies and standards across the whole service life cycle, and reassess as providers change | 0 |
5.2b | Manage identities, credentials and access across the life cycle with phishing-resistant MFA and granular privileged access | 0 |
5.2c | Protect data at every stage, type and state: decide what to protect, how much, who controls sharing, and handle termination and sanitisation | 0 |
5.2d | Protect infrastructure and applications: scan everything, segment networks, harden configurations, shield applications and manage vulnerabilities with a disclosure policy | 0 |
5.2e | Monitor system health and resources, and keep tested response and recovery plans that use cloud capabilities | 0 |
5.3a | Adopt posture management capabilities deliberately: native or third-party, independent or integrated, with multi-cloud coverage | 0 |
5.3b | Structure provider accounts in a hierarchy with central monitoring and separate development and test accounts | 0 |
5.3c | Decide where authentication happens, federate identity, minimise authentication realms and enforce least privilege with entitlement management | 0 |
5.3d | Redesign the perimeter around data and segmentation, and place sensors for inbound, outbound and inter-service visibility | 0 |
5.3e | Monitor compliance, vulnerabilities, availability, misconfigurations and service footprint across regions and providers | 0 |
5.3f | Secure APIs and microservices: versioning, encryption, keyed and authorised access, gateways and a service mesh with ABAC | 0 |
5.3g | Know, validate, synchronise and centralise logs and telemetry to meet federal logging requirements | 0 |
5.3h | Deploy through automation: integrated DevSecOps, golden images, zero-downtime replacement, vetted dependencies, infrastructure as code, key management and drift control | 0 |
6 | Conclusion and scenarios | 0 |