openskills.info
Course Preview

Cloud Penetration Testing

Cloud penetration testing evaluates the security of workloads, configurations, and identities deployed on cloud platforms. It applies offensive techniques to find misconfigurations, overprivileged roles, exposed services, and lateral movement paths specific to cloud environments.

itOffensive security and application security

Don't Panic — Cloud Penetration Testing

Cloud penetration testing is the disciplined effort to show how an attacker could reach a valuable cloud resource, while having permission to be there. That last part is not a footnote. It is the wall that keeps a useful security test from becoming an expensive conversation with several lawyers.

The old mental picture of a penetration test is a person staring at ports and web pages. Keep the ports and pages, but add the cloud's favorite furniture: provider APIs, managed services, temporary sessions, roles, policies, and data-sharing features. A machine can have no open door at all while an identity still has a very interesting set of keys.

The useful map has four surfaces. The public workload surface is what strangers can reach. The cloud control plane, meaning the provider consoles and APIs that create or alter resources, is where configuration becomes action. The identity plane, meaning accounts, workload identities, roles, credentials, and policies, decides who gets to ask. The data plane is where stored information gets read, copied, shared, or removed. A test follows the joins between them.

This is why a permission that looks harmless in isolation can be the beginning of a longer story. An application flaw might reveal a workload identity. That identity might assume a role. The role might change a policy. The policy might expose data. None of those steps needs a dramatic network exploit, which is rude of the cloud but entirely on brand.

The safety trick is minimum proof: collect the smallest evidence that answers the question. Listing approved secret metadata can prove discovery without reading a secret. Demonstrating that a role is assumable can prove escalation without changing a production resource. The evidence is still evidence; it merely arrives with fewer broken things attached.

Start with the Intro for the full map and the reason provider rules matter. Use Slides when the four surfaces and attack path need a quick redraw. Keep the Cheatsheet nearby for scope records, identity questions, and stop conditions. The Reference tab leads from NIST's testing structure to the current policies and cloud behaviors. The Quiz is where the terms stop politely nodding and start asking whether they have connected.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources

  • https://csrc.nist.gov/pubs/sp/800/115/final
  • https://aws.amazon.com/security/penetration-testing/
  • https://learn.microsoft.com/en-us/azure/security/fundamentals/pen-testing
  • https://support.google.com/cloud/answer/6262505?hl=en
  • https://cloud.google.com/terms/aup
  • https://attack.mitre.org/techniques/T1078/004/
  • https://attack.mitre.org/techniques/T1098/
  • https://attack.mitre.org/techniques/T1537/
  • https://github.com/RhinoSecurityLabs/cloudgoat
  • https://github.com/BishopFox/cloudfox
  • https://github.com/nccgroup/ScoutSuite
  • https://github.com/RhinoSecurityLabs/pacu
  • https://github.com/prowler-cloud/prowler
  • https://github.com/lyft/cartography