This free curriculum covers every domain assessed in the Oxford Certified Cloud Security Professional examination: cloud models and shared responsibility, governance, identity and access, data protection and keys, network security, workload and container security, infrastructure as code and DevSecOps, posture management, logging, detection and incident response, resilience, SaaS and multi-cloud, zero trust and compliance. Read each chapter, note the key points, and then sit the 90-question examination.
Cloud services come as IaaS, PaaS and SaaS, deployed in public, private, hybrid or multi-cloud models. Under the shared responsibility model, the provider secures the underlying infrastructure while customers secure what they put in the cloud. In PaaS, the provider manages runtime and OS while customers manage applications, data and access. In IaaS, customers manage operating systems, applications, data and configurations; in SaaS, they still own their data, user access and settings.
Most cloud incidents result from customer misconfigurations and weak identity controls rather than provider failures. A cloud security professional enables the business to use the cloud safely through architecture, automation, monitoring and governance.
IaaS, PaaS, SaaS
Public, private, hybrid, multi-cloud
Shared responsibility by model
Misconfiguration is the main risk
À retenir: The provider secures the cloud; you secure what you put in it.
Chapitre 2
Governance and guardrails
Cloud governance combines policies, roles, risk assessment, guardrails, compliance monitoring and executive reporting. Guardrails such as organisation-level policies prevent or detect risky configurations across accounts.
Service control or organisation policies set permission boundaries across accounts, and secure defaults keep new resources restrictive. Separate accounts or subscriptions for production, development and testing limit blast radius. Tagging identifies owners, environments and data sensitivity. Cost anomaly alerts can reveal compromises such as cryptomining.
Policies and guardrails
Account separation
Resource tagging
Cost anomalies as signals
À retenir: Guardrails let teams move fast without falling off the edge.
Chapitre 3
Identity and access management
Least privilege grants only needed permissions; developers requesting full admin should receive specific permissions, ideally via roles with time-limited, approved elevation. The root account is protected with strong MFA, not used daily and monitored. Temporary role credentials are preferred over long-lived keys, and access keys must never be embedded in code, even in private repositories.
Federation with SSO centralises authentication, enables MFA and quick deprovisioning. Good practice uses groups or roles, regular access reviews and just-in-time privileged access. Workload identities let applications access resources without static credentials, and CIEM tools find excessive permissions.
Least privilege and JIT access
Protect the root account
Temporary credentials and workload identities
SSO, MFA and access reviews
CIEM
À retenir: In the cloud, identity is the new perimeter.
Chapitre 4
Data protection, keys and secrets
Data classification drives controls. Encryption at rest protects stored data; encryption in transit uses TLS. Customer-managed keys give control over key policies, rotation and revocation; BYOK/HYOK models meet sovereignty needs; HSMs protect keys in tamper-resistant hardware.
Envelope encryption protects data keys with a master key in a KMS, and key rotation limits the impact of compromise. Secrets belong in dedicated secrets managers with access control, auditing and rotation. Account-level block public access prevents accidental exposure; if public buckets are found, block access, assess exposure via logs and follow incident response. DLP tools discover and protect sensitive data. Data residency may require specific regions.
Classification and encryption
Key management and HSMs
Secrets managers
Block public access
DLP and data residency
À retenir: Encrypt everything, and control who holds the keys.
Chapitre 5
Network security
VPCs and virtual networks isolate resources; subnets segment workloads; security groups act as stateful virtual firewalls. Databases belong in private subnets. Inbound rules are restricted to necessary ports and sources — never SSH open to the whole internet.
Private endpoints reach services without the public internet. WAFs protect against web attacks; DDoS protection absorbs traffic floods; bastions or session managers give audited admin access. Egress filtering limits data exfiltration and command-and-control. APIs need authentication, authorisation, rate limiting, validation and monitoring.
Isolation and segmentation
Security groups and private subnets
Private endpoints
WAF, DDoS and controlled admin access
Egress filtering and API security
À retenir: Expose only what must be exposed.
Chapitre 6
Workload, container and serverless security
VMs need hardened images, patching, endpoint protection and minimal ports. Protect instance metadata services (for example IMDSv2) against SSRF credential theft. Immutable infrastructure rebuilds from updated images.
Container security uses minimal trusted base images, vulnerability scanning, signing and non-root execution. Kubernetes needs least-privilege RBAC, network policies, admission controls against privileged containers, an authenticated API server and encrypted or externally managed secrets. Serverless security focuses on least-privilege function permissions, input validation and dependencies. Vulnerability management covers VMs, containers, serverless dependencies, IaC and configurations.
Hardened, patched VMs
Metadata service protection
Secure container images
Kubernetes RBAC and network policies
Serverless least privilege
À retenir: Every workload type has its own attack surface.
Chapitre 7
Infrastructure as code and DevSecOps
Infrastructure as Code puts configurations under version control and review, and enables scanning before deployment. Automated IaC scanning and policy-as-code checks in CI/CD block insecure configurations such as public buckets. Drift detection finds live resources diverging from approved definitions.
DevSecOps integrates security throughout delivery. Pipelines use short-lived credentials via workload identity federation, protected branches and separated build and deploy permissions. Supply chain security uses dependency scanning, SBOMs, signed artifacts and protected pipelines, which require strong access controls.
IaC reviews and scanning
Policy as code
Drift detection
DevSecOps and supply chain security
À retenir: Prevent misconfigurations before they reach production.
Chapitre 8
Posture management, logging and detection
CSPM tools continuously assess configurations against best practices and standards; CNAPPs combine posture, workload and identity protection. Audit logs record who did what, when and from where; they should be centralised, tamper-protected and retained appropriately.
Cloud-native threat detection analyses logs, network flows and DNS for suspicious behaviour. CASBs and SSPM provide visibility and control over SaaS use and configuration, including shadow IT.
CSPM and CNAPP
Centralised, protected logs
Threat detection services
CASB and SSPM
À retenir: You can only defend what you can see.
Chapitre 9
Incident response and resilience
Cloud incident plans include cloud-specific playbooks, responder access, evidence preservation and provider coordination. Compromised credentials are contained first by disabling keys and sessions. Evidence is preserved with snapshots and logs, isolating rather than terminating instances.
Game days and security chaos engineering test detection and response safely. Resilience relies on multiple availability zones, tested backups stored separately, defined RTO and RPO, and immutable or air-gapped backups that resist ransomware.
Cloud IR playbooks
Contain, then investigate
Preserve evidence
Multi-AZ and immutable backups
À retenir: Plan for compromise and recover with confidence.
Chapitre 10
Zero trust, multi-cloud and compliance
Zero trust never trusts implicitly, verifying every request based on identity, device and context. Multi-cloud environments need consistent policies and visibility across differing security models. Unapproved SaaS use is handled by assessing risk, offering secure alternatives, applying controls and educating users.
Frameworks include the CSA Cloud Controls Matrix and ISO/IEC 27017; SOC 2 reports provide independent assurance about provider controls. Provider assurance is reviewed through certifications, audit reports and contracts.
Zero trust principles
Consistent multi-cloud security
Managing shadow SaaS
CSA CCM, ISO 27017 and SOC 2
À retenir: Trust is verified continuously, never assumed.
Prêt ? Passez l’examen gratuit
Passez l’examen et obtenez gratuitement votre badge numérique. Après la réussite, vous pourrez commander le certificat officiel.