PAGES
← all tools
◆ Cloud Security Posture

Cloudsplaining

0.9.1 open-source

Cloudsplaining is an AWS IAMAWS IAMAWS Identity and Access Management is Amazon's service for controlling who and what can call AWS APIs, by attaching policies that allow or deny actions on resources. Cyber tools use it to scope credentials to least privilege. Security Assessment tool that identifies violations of least privilege and generates a risk-prioritized report.

Summary

Cloudsplaining is an open-source, free command-line tool that scans AWS 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. policies for violations of least privilege and generates a risk-prioritized HTML report. It works across a single policy file or an entire account, and can assume a specified AWS role to scan across multiple accounts, flagging policies that permit data exfiltrationdata exfiltrationMoving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels., infrastructure modification, or resource exposure without restriction. It is built for cloud security and IAM teams auditing AWS permissions rather than for general infrastructure engineers, and its findings now link to pathfinding.cloud for privilege-escalation path context. It sits in the cloud IAM policy-analysis space rather than general cloud security posture managementcloud security posture managementCloud security posture management, checking cloud resources for risky settings and policy violations. It helps teams find exposed services, overly broad permissions and other configuration gaps.. First committed in 2020, it has drawn 38 contributors and 134 commits in the past year, with a release only 68 days ago.

Cloudsplaining is an AWS IAM Security Assessment tool that identifies violations of least privilege and generates a risk-prioritized report.

How Cloudsplaining helps

Which IAM policies in my account let a principal read secrets or exfiltrate data without any resource restriction?

scans all policies in the account (or a single policy file) for actions like reading objects, parameters, or secrets values and flags the ones with no resource constraint, prioritized by risk in the HTML report

Which of my policies would let someone modify infrastructure or expose resources to the outside world?

checks each policy for actions that modify infrastructure or that can alter resource-based policies, and lists them as separate risk categories in the report

Do any of my IAM policies grant a path to privilege escalation?

matches policy statements against known privilege-escalation paths and links each finding to pathfinding.cloud for the attack-path context

Which accounts in my organization have the same least-privilege gaps?

can assume a specified role to pull authorization details from multiple AWS accounts and scan them in the same pass, rolling the results into one report

Which findings are acceptable risks I don't want flagged every time?

takes a file of exclusions so named policies or principals are left out of future scans, keeping the report focused on unreviewed issues

Which IAM actions across my policies are missing resource-level restrictions altogether?

inspects every statement for actions granted without a resource constraint and surfaces them regardless of category, so overly broad grants aren't missed

all 16 features, with the evidence for each →

Languages

Not documented

Features

16 capabilities · 3 backed by code, an API document or a real run

Built from Cloudsplaining'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 Cloudsplaining offers you

  • Command-line interface4
All capabilities 16 capabilities
Privilege-escalation path detection shipped Detects privilege-escalation paths across cloud accounts and surfaces them with pathfinding.cloud-linked findings in the HTML report. 6 releases · 3 other sources · first seen May 2020

release

  • Integrates pathfinding.cloud onboarding skill pipeline and safety tooling for guided privilege-escalation analysis. 0.9.0 · Jun 2026 · source · release history
  • Adds 37 new privilege-escalation path detections integrated with pathfinding.cloud, surfaced and linked directly in the HTML report. 0.9.0 · Jun 2026 · source · release history
  • Adds 37 new IAM privilege-escalation path detections linked to pathfinding.cloud for enriched attack-path context in reports. 0.9.0 · Jun 2026 · source · release history
  • Adds --flag-all-risky-actions CLI argument to force all risky actions flagged regardless of conditions 0.6.1 · Aug 2023 · source · release history
  • Adds support for optional noisy results that flag risky actions even when resource constraints or conditions are used. 0.5.0 · Feb 2022 · source · release history
  • Added "Attached to Principals" dropdown card for Customer-Managed and AWS-Managed Policies 0.1.1 · May 2020 · source · release history

example

  • Generate a full account scan report that now includes pathfinding.cloud-linked privilege-escalation findings for all 37 new detection paths. cloudsplaining scan --input-file examples/files/example.json --exclusions-file examples/example-exclusions.yml --output examples/report/ 0.9.0 · Jun 2026 · source
  • Force the tool to flag every risky action without suppressing findings based on conditions. cloudsplain --flag-all-risky-actions ./policy.json 0.6.1 · Aug 2023 · source
  • View which IAM principals are attached to specific policies via the UI dropdown. Navigate to the IAM Principals tab and use the new "Attached to Principals" dropdown card for Customer-Managed and AWS-Managed Policies 0.1.1 · May 2020 · source
File and diff scanning verified suggested Scans specific files via explicit paths or uses git-diff mode when no paths are provided. 3 releases · 5 other sources · first seen Aug 2020

Suggested capability: Static application security testing. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Python 3.7 support is dropped; the tool no longer runs on Python < 3.8 0.7.0 · Sep 2024 · source · release history
  • --input flag renamed to --input-file for all commands 0.1.8 · Aug 2020 · source · release history
  • The --input flag is renamed to --input-file, so existing commands using --input will fail. 0.1.8 · Aug 2020 · source · release history

command line

  • --path — Scan exactly this file (repeatable). Omit to use git-diff mode. 0.8.3 · Jun 2026 · command-line history
  • --old — baseline example-iam-data.json 0.8.3 · Jun 2026 · command-line history

example

  • Use the new flag name to specify an IAM policy file for analysis. cloudsplaining scan-policy-file --input-file my-policy.json 0.1.8 · Aug 2020 · source
  • Scan a single IAM policy file cloudsplaining scan-policy-file --input-file examples/policies/explicit-actions.json
  • Scan account with custom exclusions cloudsplaining scan --input-file default.json --exclusions-file exclusions.yml
PR check polling and status waiting verified Polls for CI check results on a pull request, with configurable polling interval and timeout for checks to register. 1 release · 3 other sources · first seen Sep 2024

release

command line

  • --no-checks-timeout-seconds — Maximum time to wait for checks to register before reporting no checks 0.8.3 · Jun 2026 · command-line history
  • --pr — PR number (defaults to current branch PR) 0.8.3 · Jun 2026 · command-line history
  • --poll-seconds — Polling interval while checks are pending or gh is transiently failing 0.8.3 · Jun 2026 · command-line history
Credential exposure detection shipped Detects potential credential exposure risks within IAM policy definitions. 3 releases · 1 other source · first seen Sep 2020

Also counts toward: Command-line interface

release

  • Extends the list of actions exposing credentials 0.6.2 · Oct 2023 · source · release history
  • Credentials Exposure findings are now included in the data.json output file. 0.2.2 · Oct 2020 · source · release history
  • scan-policy-file command now returns findings about Credentials Exposure 0.2.0 · Sep 2020 · source · release history

example

  • Identify potential credential exposure risks within an IAM policy definition. cloudsplaining scan-policy-file ./role-policy.json --json 0.2.0 · Sep 2020 · source
Service wildcard detection shipped Identifies findings related to Service Wildcard usage in IAM policies. 4 releases · first seen Sep 2020

Also counts toward: Command-line interface

release

  • Adds Credentials Exposure as a new finding type in the UI. 0.2.3 · Oct 2020 · source · release history
  • Adds Service Wildcard as a new finding type in the UI. 0.2.3 · Oct 2020 · source · release history
  • Service Wildcard findings are now included in the data.json output file. 0.2.2 · Oct 2020 · source · release history
  • scan-policy-file command now returns findings about Service Wildcard 0.2.0 · Sep 2020 · source · release history
Exclusion management shipped Supports generating exclusion templates and applying custom exclusions during scanning. 2 releases · 2 other sources · first seen Aug 2020

release

  • Exclusions are applied earlier in the scan pipeline, resulting in faster execution. 0.2.2 · Oct 2020 · source · release history
  • Exclusions configuration now correctly displays in the report 0.1.8 · Aug 2020 · source · release history

example

  • Generate exclusions template file cloudsplaining create-exclusions-file
  • Scan account with custom exclusions cloudsplaining scan --input-file default.json --exclusions-file exclusions.yml
Report size minimization shipped Generates smaller reports by minimizing output data through a specific command option. 2 releases · 1 other source · first seen Oct 2020

Also counts toward: Command-line interface

release

  • Sorts IAM principals alphabetically by name (instead of ID) in generated reports, making large reports easier to navigate. 0.9.1 · Jun 2026 · source · release history
  • Adds --minimize option to the scan command for reduced report size. 0.2.3 · Oct 2020 · source · release history

example

  • Generate a smaller report by minimizing output data. cloudsplaining scan --minimize 0.2.3 · Oct 2020 · source
Assumed role scanning shipped Allows IAM policy analysis by assuming a specified AWS role via STS. 1 release · 2 other sources · first seen Sep 2025

release

  • Adds assume role support, enabling Cloudsplaining to scan IAM policies by assuming a specified AWS role. 0.8.1 · Sep 2025 · source · release history

example

  • Download using specific AWS profile cloudsplaining download --profile myprofile
  • Download account authorization details cloudsplaining download
Federated principal analysis shipped suggested Includes federated principals in scan results to provide visibility into cross-account access and trust relationships. 2 releases · first seen May 2020

Suggested capability: Data access governance. This is our guess, not confirmed.

release

Security impact explanations shipped Provides inline explanations in findings to describe the security impact of each issue. 2 releases · first seen Dec 2020

release

  • Added links to API docs for every IAM action in the findings 0.2.5 · Jan 2021 · source · release history
  • Findings now include inline explanations to describe the security impact of each finding. 0.2.4 · Dec 2020 · source · release history
Demo report generation shipped Generates a sample account scan report using an enriched built-in example dataset to produce representative findings. 1 release · first seen Jun 2026

release

  • Enriches the built-in example dataset to produce a higher-quality demo report with more representative findings. 0.9.0 · Jun 2026 · source · release history
Threaded comment posting verified Posts comments to PR threads by accepting alternating thread ID and body argument pairs. 1 other source · first seen Jun 2026

command line

Custom report content shipped Enables embedding organization-specific guidance and appendices into scan reports. 1 release · first seen Oct 2025

release

  • Supports custom guidance and appendices in reports, allowing practitioners to embed organization-specific remediation advice. 0.8.2 · Oct 2025 · source · release history
Role usage analysis shipped suggested Includes RoleLastUsed date information for IAM roles in scan output. 1 release · first seen Dec 2020

Suggested capability: Data access governance. This is our guess, not confirmed.

release

  • scan-policy-file now includes the RoleLastUsed date in its output. 0.2.4 · Dec 2020 · source · release history
Account authorization details download shipped suggested Downloads account authorization details for external analysis. 1 other source

Suggested capability: Data access governance. This is our guess, not confirmed.

example

  • Download account authorization details cloudsplaining download
AWS profile support shipped Allows configuration of AWS access using specific profiles. 1 other source

example

  • Download using specific AWS profile cloudsplaining download --profile myprofile

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 Cloudsplaining, 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 Cloudsplaining 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

Show

18 entries

  1. June 20263
  2. October 20251
  3. September 20251
  4. September 20241
  5. October 20231
  6. August 20231
  7. February 20221
  8. January 20211
  9. December 20201
  10. October 20202
  11. September 20201
  12. August 20201
  13. May 20203
    Show

    18 entries

    Project health

    Issue, contributor and maintainer activity in salesforce/cloudsplaining, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 6 +3 vs prior 12 months
    2. Maintainers 2 +1 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 50% of issues opened, last 12 months
    5. Median time to close 91 days first maintainer reply 4.6 hours
    6. Open backlog 14 of 130 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 14
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 2,246
    Issue themes, last 12 months
    • features 25%
    • other 75%

    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.

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