:fox_face: CloudFox :fox_face:

CloudFox helps you gain situational awareness in unfamiliar cloud environments. It’s an open source command line tool created to help penetration testers and other offensive security professionals find exploitable attack paths in cloud infrastructure.

CLOUDFOX UPDATE REQUIRED: (12/2025): If you are using cloudfox, you need to use v1.17.0 or greater. All earlier versions stopped working after a format change in AWS's public service mapping file.

Overview

CloudFox helps you answer the following common questions (and many more):

• What regions is this AWS account using and roughly how many resources are in the account?
• What secrets are lurking in EC2 userdata or service specific environment variables?
• What workloads have administrative permissions attached?
• What actions/permissions does this [principal] have?
• What role trusts are overly permissive or allow cross-account assumption?
• What endpoints/hostnames/IPs can I attack from an external starting point (public internet)?
• What endpoints/hostnames/IPs can I attack from an internal starting point (assumed breach within the VPC)?
• What filesystems can I potentially mount from a compromised resource inside the VPC?

Demos, Examples, Walkthroughs

• Blog - Introducing: CloudFox
• Video - CloudFox + CloudFoxable A Powerful Duo for Mastering the Art of Identifying and Exploiting AWS Attack Paths
• Video - Penetration Testing with CloudFox
• Video - CloudFox Intro Demos
• Video - Tool Talk: CloudFox AWS sub-command walkthroughs

Intentionally Vulnerable Playground

• CloudFoxable - A Gamified Cloud Hacking Sandbox

Want to chat about CloudFox?

Join us on the RedSec discord server

Quick Start

CloudFox is modular (you can run one command at a time), but there is an aws all-checks command that will run the other aws commands for you with sane defaults:

cloudfox aws --profile [profile-name] all-checks

White Box Enumeration

CloudFox was designed to be executed by a principal with limited read-only permissions, but it's purpose is to help you find attack paths that can be exploited in simulated compromise scenarios (aka, objective based penetration testing).

Black Box Enumeration

CloudFox can be used with "found" credentials, similar to how you would use weirdAAL or enumerate-iam. Checks that fail, do so silently, so any data returned means your "found" creds have the access needed to retrieve it.

Documentation

For the full documentation please refer to our wiki.

Supported Cloud Providers

Install

Option 1: Download the latest binary release for your platform.

Option 2: If you use homebrew: brew install cloudfox

Option 3: Install Go, use go install github.com/BishopFox/cloudfox@latest to install from the remote source

Option 4: Developer mode:

Install Go, clone the CloudFox repository and compile from source # git clone https://github.com/BishopFox/cloudfox.git # cd ./cloudfox # Make any changes necessary # go build . # ./cloudfox

Option 5: Testing a bug fix git clone git@github.com:BishopFox/cloudfox.git git checkout seth-dev go build . ./cloudfox [rest of the command options]

Prerequisites

AWS

• AWS CLI installed
• Supports AWS profiles, AWS environment variables, or metadata retrieval (on an ec2 instance)
• To run commands on multiple profiles at once, you can specify the path to a file with a list of profile names separated by a new line using the -l flag or pass all stored profiles with the -a flag.
• A principal with one recommended policies attached (described below)
• Recommended attached policies: SecurityAudit + CloudFox custom policy

Additional policy notes (as of 09/2022):

Azure

• Viewer or similar permissions applied.

GCP

• Google Cloud SDK installed and authenticated
• Application Default Credentials configured (gcloud auth application-default login)
• Recommended permissions at appropriate hierarchy levels (see below)

GCP Permissions: Minimal vs Comprehensive

Minimal Permissions (Single Project):

For basic enumeration of a single project, the roles/viewer role provides read access to most resources (includes logging, monitoring, and compute/network viewing).

Comprehensive Permissions (Organization-Wide):

For thorough security assessments across an entire organization:

Note: The basic roles/viewer role includes permissions from roles/logging.viewer, roles/monitoring.viewer, and roles/compute.networkViewer, so these don't need to be granted separately.

GCP API Requirements

APIs must be enabled in each project you want to assess. GCP APIs are project-scoped.

For detailed setup instructions, see the GCP Setup Guide.

AWS Commands