Cloud Security Engineering -- from foundations to enterprise practitioner
A cloud security engineer designs, implements, validates and keeps improving the controls that protect cloud infrastructure, identities, networks, workloads, applications, data, delivery pipelines and enterprise architectures. Where SecOps notices what went wrong, you make it hard to go wrong in the first place -- and prove the controls work. The emphasis throughout is why a control is needed, how it should be designed, how it interacts with other controls, and how its effectiveness is validated. AWS is the only cloud you practise here: every lab and every mark is on simulated AWS accounts. Microsoft Azure and Google Cloud are in the reading only: each module names their equivalent services and where they behave differently, and a few module-check questions ask for an equivalent's name, but no lab configures, practises or marks either.
What the course covers
- Stage 1. IT, cloud computing and security engineering foundations — The technical foundation for designing secure cloud systems: how applications, infrastructure and identities interact.
- Stage 2. Cloud security architecture, identity and network engineering — Secure foundations and the boundaries that control access to enterprise resources.
- Stage 3. Workload, application, data and platform security engineering — Protecting the systems, applications and information that run on cloud infrastructure.
- Stage 4. Security automation, engineering pipelines and operational integration — Repeatable controls, security in delivery, and environments that stay secure as they change.
- Stage 5. Enterprise cloud security, resilience and professional mastery — Secure enterprise platforms, governance obligations, incident readiness and defensible design decisions.
- Stage 6. Capstone — A secure enterprise cloud platform for a migration, from requirements to the executive presentation.
- Projects
- Interview preparation