CloudGoat
v2.5.0 open-sourceThe section your link pointed to isn't on CloudGoat's page any more, so we've brought you to the top.
CloudGoat is Rhino Security Labs' Vulnerable by Design cloud deployment tool for honing cloud cybersecurity skills via capture-the-flag scenarios.
Summary
CloudGoat is an open-source, free command-line tool that spins up intentionally vulnerable AWS and Azure environments for hands-on cloud security penetration testing. It's run from a terminal, either natively with Python and Terraform or inside Docker, and is aimed at red teamers, pentesters, and cloud security practitioners who want CTFCTFCapture The Flag — a competitive hacking challenge format where participants exploit intentionally vulnerable systems or puzzles to retrieve hidden strings, used by cyber tools to practice and demonstrate offensive and defensive techniques.-style practice environments rather than production hardening guidance. Its scenario library covers IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. privilege escalationprivilege escalationGaining permissions beyond those an account or process initially had. It can turn limited access into administrator control or access to another user's resources., S3 and SNSSNSAmazon Simple Notification Service, a managed pub/sub messaging service from AWS that lets tools fan out alerts or events to multiple subscribers — queues, email, HTTP endpoints, or Lambda functions — without managing broker infrastructure. secrets exposure, ECSECSElastic Common Schema, an open specification maintained by Elastic that defines a standard field naming convention for log and event data, letting cyber tools share and correlate records without per-source field mapping. and Lambda attack chains, federated console takeover, and newer additions targeting Bedrock agents and AgentCore identity confusion, each deployed and torn down through simple commands with configurable regions and IP whitelisting. First committed in 2018, it has drawn 79 contributors and remains active, with 45 commits and 15 releases in the past year.
CloudGoat is Rhino Security Labs' Vulnerable by Design cloud deployment tool for honing cloud cybersecurity skills via capture-the-flag scenarios.
How CloudGoat helps
Can I actually pull off an IAM privilege escalation chain, not just read about one?
deploys a live AWS environment with the misconfigured roles and policies needed for a real escalation path, so the attempt either succeeds or fails against real API responses instead of a diagram
Would my team recognize an S3 or SNS secrets leak if they saw one?
builds a working AWS environment where credentials or keys sit exposed in bucket objects or SNS messages, so finding and extracting them is practiced against a real store rather than a description
Do I know how to move laterally once I've landed inside a container service?
stands up an ECS or Lambda chain with the connecting misconfigurations already in place, so the path from initial foothold to further access is something to actually find and exploit
Can I take over a federated console session the way an attacker would?
provisions the federated identity setup with the abusable trust relationship, so the takeover has to be carried out against a live console session rather than assumed
Am I ready for identity confusion attacks against newer AI agent services?
deploys a Bedrock or AgentCore environment with the identity-confusion flaw built in, giving a current target to attack before encountering it in a real deployment
Have I actually tested an attack path, or only rehearsed it in an environment I already know the answer to?
tears the environment down and can rebuild it fresh, so the same scenario can be re-run cold, against a newly provisioned set of resources, to check the skill rather than the memory of the first run
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for CloudGoat, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail CloudGoat puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
7 entries
No entries match these filters.
- March 20261
- February 20261
- September 20251
- June 20251
- March 20253
Project health
Issue, contributor and maintainer activity in RhinoSecurityLabs/cloudgoat, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 7 −8 vs prior 12 months
- Maintainers 2 +0 joined · −3 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 65 days first maintainer reply 33 days
- Open backlog 17 of 134 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 17
- Contributors / month 0
- Commits / month 0
- Stars 3,731
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
1 article · updated Nov 4, 2026Where CloudGoat turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Tutorials & guides 1
-
AWS CloudGoat EC2 SSRF Exploitation
In this article, we will walk through a CloudGoat EC2 SSRF scenario where an attacker abuses a vulnerable EC2-hosted application to access AWS Instance Metadata Service (IMDS) and ultimately retrieve sensitive IAM…
2 more quotes
This walkthrough was developed using the CloudGoat framework to model a realistic AWS attack scenario, with several steps derived through independent testing to reflect the current lab behavior.
Table of Contents Introduction to CloudGoat Part 1: Lab Setup Create Free Tier AWS Account Configure IAM for CloudGoat Setting up Kali Linux for AWS Pentesting Installing Terraform Configuring AWS CLI and installing…
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.