PAGES
← all tools
◆ Cloud Security Posture

CloudGoat

v2.5.0 open-source

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

all 7 features, with the evidence for each →

Languages

Not documented

Features

7 capabilities · 1 backed by code, an API document or a real run

Built from CloudGoat's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What CloudGoat offers you

  • CI/CD pipeline integration1
  • Command-line interface1
  • Python scripting support1
  • Scripting language support1
All capabilities 7 capabilities
Scenario library shipped Provides a collection of pre-configured capture-the-flag scenarios targeting specific cloud service vulnerabilities and attack chains. 20 releases · first seen Mar 2025

release 20 total

  • New iam_enum_basics scenario for practicing foundational AWS IAM enumeration techniques. v2.5.0 · Mar 2026 · source · release history
  • New scenario data_secrets: focuses on secrets discovery in data services. v2.4.0 · Feb 2026 · source · release history
  • New scenario Static: adds a static-credential abuse training scenario. v2.4.0 · Feb 2026 · source · release history
  • New scenario bedrock_agent_hijacking: simulates hijacking of Amazon Bedrock agents. v2.4.0 · Feb 2026 · source · release history
  • New scenario agentcore_identity_confusion: covers identity confusion attacks targeting AWS AgentCore. v2.4.0 · Feb 2026 · source · release history
  • New scenario s3_version_rollback_via_cfn: trains practitioners on S3 version rollback attacks via CloudFormation. v2.4.0 · Feb 2026 · source · release history
ECR image building and publishing verified Builds a Docker image from a specified Dockerfile and pushes it to an AWS ECR repository in a given region with a specified tag. 1 release · 5 other sources · first seen Mar 2025

release

  • Adds Docker support for running CloudGoat in a containerized environment. v2.0.1 · Mar 2025 · source · release history

command line

example

  • Run CloudGoat Docker with AWS credentials docker run -it -v ~/.aws:/root/.aws/ rhinosecuritylabs/cloudgoat:latest
Core execution environment shipped Provides the necessary runtime and command-line interface for defining, creating, and managing vulnerable infrastructure. 1 release · 2 other sources · first seen Mar 2025

Also counts toward: Command-line interface, Python scripting support, Scripting language support

release

example

  • Create IAM privilege escalation scenario cloudgoat create iam_privesc_by_rollback
  • Create EC2 SSRF scenario cloudgoat create ec2_ssrf
Environment configuration shipped Automates the setup of cloud profiles, subscriptions, and security whitelists required to run scenarios safely. 3 other sources

example

  • Configure CloudGoat Azure subscription cloudgoat config azure
  • Configure CloudGoat AWS profile cloudgoat config aws
  • Auto-configure IP whitelist cloudgoat config whitelist --auto
Infrastructure compatibility and portability shipped Maintains compatibility with modern infrastructure-as-code tools and dynamic cloud resource resolution to ensure reliable deployment across regions. 2 releases · first seen Mar 2025

release

  • Dynamic Ubuntu AMI lookup replaces hardcoded AMI in the cloud_breach_s3 scenario, improving portability across regions. v2.4.0 · Feb 2026 · source · release history
  • Adds Terraform v0.14+ compatibility. v2.0.1 · Mar 2025 · source · release history
Scenario management and contribution shipped Standardizes the creation, testing, and integration of new scenarios through templates and automated CI/CD pipelines. 2 releases · first seen Mar 2025

Also counts toward: CI/CD pipeline integration

release

  • Adds scenario template and contribution guide to standardize community-created scenarios. v2.0.1 · Mar 2025 · source · release history
  • Adds GitHub Actions-based automated testing for scenarios. v2.0.1 · Mar 2025 · source · release history
Cloud platform support shipped Deploys vulnerable scenarios across multiple cloud providers, starting with AWS and expanding to Azure. 1 release · first seen Mar 2025

release

  • Adds Azure cloud platform support, expanding CloudGoat beyond AWS. v2.2.0 · Mar 2025 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Releases

7 entries

  1. March 20261
  2. February 20261
  3. September 20251
  4. June 20251
  5. March 20253

    7 entries

    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.

    1. Contributors 7 −8 vs prior 12 months
    2. Maintainers 2 +0 joined · −3 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 65 days first maintainer reply 33 days
    6. Open backlog 17 of 134 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 17
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 3,731
    Issue themes, last 12 months
    • 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, 2026

    Where 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 Hacking Articles
      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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →