CloudFox
v2.0.0 open-sourceThe section your link pointed to isn't on CloudFox's page any more, so we've brought you to the top.
CloudFox is an open source command line tool that helps penetration testers find exploitable attack pathsattack pathsA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. in cloud infrastructure.
cloudfox aws resource-trusts cloudfox aws route53 cloudfox aws iam-simulator --admin-check-only cloudfox cape --pmapper-basepath ./loot cloudfox aws workloads cloudfox aws api-gws -o loot.txt cloudfox aws inventory -o wide cloudfox azure -t my-tenant-name -s 01234567-89ab-cdef-0123-456789abcdef cloudfox azure vms cloudfox aws resource-trusts cloudfox aws org cloudfox aws network-ports cloudfox aws sns cloudfox azure inventory cloudfox --aws-profile default -g 50 cloudfox azure --output-strategy az_instance_latest cloudfox azure --output-strategy az_rbac_latest
Summary
CloudFox is an open-source command-line tool that helps penetration testers and other offensive security professionals map exploitable attack paths in cloud infrastructure they're unfamiliar with. It runs as a modular CLI, with commands like all-checks running a full sweep of AWS enumeration modules with sane defaults, or individual commands scoped to specific services like 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., KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves., or Route53. What began as an AWS-focused tool has grown to cover Azure and GCP, including org-wide enumeration, privilege-escalation detection, and network diagram generation, aimed squarely at red teamers and pentesters rather than defenders. It surfaces questions like which workloads hold admin permissions, which role trusts are overly permissive, and what's reachable from an external or internal starting point. With 30 contributors, 170 commits and 21 releases in the past year, and a release just 87 days ago, it's actively maintained.
CloudFox is an open source command line tool that helps penetration testers find exploitable attack paths in cloud infrastructure.
How CloudFox helps
Which workloads in this account hold administrative permissions?
scans compute and container resources and cross-references their attached roles against admin-equivalent permission sets, flagging the ones with effectively unrestricted access
Which role trusts would let someone pivot in from another account?
reads resource and trust policies across the account and lists the principals allowed to assume in, highlighting cross-account and wildcard trust relationships
What can be reached from a foothold inside the VPC versus from the open internet?
builds a network map from security groups, subnets and routing data and separates what is exposed externally from what is only reachable once already inside
What secrets are sitting in plaintext on compute resources?
pulls instance userdata and service environment variables and surfaces hardcoded credentials or keys found inside them
What does a given principal actually have permission to do?
runs the requested actions against IAM policy simulation for that principal and reports which ones succeed, without needing to touch the resource itself
How exposed is my subdomain footprint to takeover?
enumerates DNS records including alias records and points out ones pointing at unclaimed or reassignable targets like load balancers or CDNs
Languages
Command line
No command matches.
| 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 CloudFox, 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 CloudFox 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
15 entries
No entries match these filters.
- March 20261
- December 20251
- October 20241
- July 20241
- April 20241
- January 20241
- December 20232
- August 20231
- June 20231
- February 20231
- January 20231
- October 20221
- September 20222
Project health
Issue, contributor and maintainer activity in BishopFox/cloudfox, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 6 −1 vs prior 12 months
- Maintainers 1 +1 joined · −2 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 307 days first maintainer reply 6.7 days
- Open backlog 7 of 31 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 7
- Contributors / month 0
- Commits / month 0
- Stars 2,581
- bugs 33%
- other 67%
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
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.