Cloud Security for DevSecOpss
Cloud security applies least privilege and configuration checks to cloud environments. Identity and access management controls who and what can access resources, infrastructure as code is scanned before deployment, and cloud security posture management, CSPM, detects misconfigurations such as public buckets and open security groups in running accounts.
Stage: Cloud, Containers and Runtime · Part of the DevSecOps roadmap · Last reviewed 19 November 2026
What to learn in Cloud Security
- Write an IAM policy that grants only the actions and resources needed
- Use roles and temporary credentials rather than static keys
- Scan Terraform with tools such as Checkov or tfsec
- Detect public storage and open security groups using CSPM
- Enable audit logs such as CloudTrail across accounts
- Explain the shared responsibility model
Cloud Security interview questions
How does the shared responsibility model change how a DevSecOps team secures cloud workloads?
The cloud provider secures the underlying infrastructure, such as data centres and hypervisors, while the customer secures what they configure, including identities, data, network rules and applications. The split varies by service type, such as virtual machine versus managed service. Pipeline and IaC checks sit on the customer side.
How do you find over-permissive IAM policies?
Review policies for wildcards on actions and resources, use access analysers and last-used data to remove unused permissions, scan infrastructure code in pipelines, and replace broad managed policies with scoped ones tied to specific roles.
Where Cloud Security fits in the DevSecOps roadmap
Cloud Security belongs to the Cloud, Containers and Runtime stage (intermediate level), which takes about 6 hours. Harden where it runs.
Other units in this stage
Back to the full DevSecOps roadmap