Cloud Security Office Hours Banner

Cloud Security Learning Path

A practical roadmap from "I have no cloud experience" to working practitioner. Built from what actually works for the 2000+ people in the CSOH community — with milestones, free labs, and the certifications that matter.

Start Here First, What is Cloud Security?

The honest version: Most people who break into cloud security do it in 6–18 months of focused effort. Not 6 weeks, not 3 years. The path below isn't a strict order — skip what you already know, slow down on what's hard. Hands-on work matters more than passive coursework. A portfolio of CTF write-ups and lab walkthroughs beats three certifications and zero practical experience.

📖 The Path

  1. Prerequisites (skip if you have them)
  2. Stage 1: Beginner (Months 0–3)
  3. Stage 2: Intermediate (Months 3–9)
  4. Stage 3: Advanced (Months 9+)
  5. Stage 4: Specialize
  6. Stay current
  7. Common mistakes

Prerequisites (skip if you have them)

You'll have a much easier time if you're already comfortable with:

If you're missing one of these, do that first. If you have all four, jump to Stage 1.

Stage 1: Beginner (Months 0–3)

Goal: Understand what cloud security is, get hands-on with one cloud, and pass a foundational cert.

1. Read the foundations

2. Pick one cloud and create a free account

AWS, Azure, or GCP — all three have free tiers. Pick the one your current employer uses, the one most jobs in your area use, or AWS by default. Don't try to learn three at once.

3. Walk through the official training

4. Get hands-on with the basics

5. Earn a foundational cert

See the cloud security certifications guide for details.

Stage 1 milestone: You can explain what IAM is, what the shared responsibility model means, and you've configured at least one service end-to-end on your chosen cloud.

Stage 2: Intermediate (Months 3–9)

Goal: Move from "I know the concepts" to "I can find and exploit cloud misconfigurations and explain how to fix them."

1. Run intentionally vulnerable environments

Pick three or four from our cloud security CTF directory and work through them. Recommended starting set:

2. Read real breach post-mortems

Walk through the CSOH breach kill chains. Each one is mapped to MITRE ATT&CK Cloud techniques. For each breach, identify: which IAM controls would have stopped it, which detection rule would have caught it, what the post-incident response looked like.

3. Get familiar with the tooling

4. Earn a provider security specialty

5. Start writing

Publish CTF write-ups, lab walkthroughs, or breach analyses on a personal blog or LinkedIn. This is the single highest-leverage thing you can do for your career — it builds your reputation, forces you to actually understand what you did, and gives you something to show in interviews.

Stage 2 milestone: You've completed at least 5 CTF scenarios, can use Prowler or an equivalent tool to audit a real account, and have at least one provider security cert.

Stage 3: Advanced (Months 9+)

Goal: Build deep skill in a chosen specialization and start contributing to the community.

1. Detection engineering

Build detection content for your cloud. Translate ATT&CK Cloud techniques into Sigma or vendor-specific rules. Learn how to investigate alerts without false-positive paralysis. Practice with sample data sets like Mordor.

2. Incident response and threat hunting

Read SANS DFIR materials. Practice with cloud forensics scenarios. Learn what evidence you can and can't get from each cloud (CloudTrail completeness, log retention defaults, what GuardDuty does and doesn't catch).

3. IAM at scale

Master IAM policy evaluation, condition keys, and cross-account access patterns. Read every word of the AWS Security Blog on identity. Use IAM Access Analyzer to find unused permissions in real environments. Study privilege-escalation paths via tools like Pacu.

4. Kubernetes security

If your environment uses Kubernetes, get comfortable with cluster hardening, pod security standards, network policies, and runtime security tools (Falco, Tetragon). Pursue CKS as your hands-on credential.

5. AI / LLM security

Increasingly relevant. Read the OWASP Top 10 for LLMs. Practice on AI-focused CTFs in our CTF directory. Study agentic-system risks and prompt injection in production scenarios.

6. Senior credentials

If you're going the architect/consultant route, CCSP from ISC2 once you hit five years of relevant experience. SC-100 if you're heavy in Microsoft.

Stage 3 milestone: You're shipping detection content, presenting at meetups, or leading an aspect of cloud security at your job.

Stage 4: Specialize

By this point, the field has too many depths for any one person to be expert at all of them. Pick what you're drawn to:

Stay current

Cloud changes faster than most fields. Build a rhythm:

Common mistakes

Ready to start?