ScubaGear
v2.0.0 open-sourceThe section your link pointed to isn't on ScubaGear's page any more, so we've brought you to the top.
ScubaGear is an assessment tool that verifies a Microsoft 365 tenant's configuration conforms to CISA SCuBA Secure Configuration Baseline policies.
Get-ScubaGearContext
Invoke-SCuBA -ConfigFilePath 'C:\scuba\config.yaml' -Organization 'example.onmicrosoft.com' -ProductNames *
Invoke-SCuBADiff -BeforePath "C:\Runs\Q1\ScubaResults_abc123.json" -AfterPath "C:\Runs\Q2\ScubaResults_def456.json" -OutPath "C:\Runs\Diff\Q1-Q2" -DarkMode
Invoke-SCuBADiff -BeforePath "\before\ScubaResults.json" -AfterPath "\after\ScubaResults.json" -OutPath "\diff" -OutJsonFileName "Q2Delta" -OutCsvFileName "Q2Delta" -OutReportFileName "Q2DiffReport"
ProductNames:
- aad
- securitysuite
- exo
SecuritySuite:
MS.SECURITYSUITE.2.1v1:
SensitiveUsers:
- jdoe@example.com
OmitPolicy:
MS.SECURITYSUITE.1.1v1:
Rationale: 'Handled by our third-party mail gateway.'
Install-Module -Name ScubaGear
New-Config
ScubaGear -c default-config.yaml --cmdline_config_vars 'scan_target: "my-tenant.onmicrosoft.com"; output_dir: "/tmp/report'"
Invoke-SCuBA -CertificateThumbprint '<thumbprint>' -ConfigFilePath './sample-config-files/sample-config.yaml'
Invoke-SCuBA -M365Environment GCC-H -ProductNames *
Summary
ScubaGear is an open-source assessment tool, free to use, that checks whether a Microsoft 365 tenant's configuration matches the CISA Secure Configuration Baselines under the SCuBA program. It runs as a PowerShell command-line tool: it queries M365 APIs for configuration settings, hands them to Open Policy Agent for evaluation against Rego policies, and outputs the results as HTML, JSON, and CSV, with a GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands. now available for building configuration files. It's built for M365 administrators rather than security teams doing general auditing, and its baselines cover Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments., Exchange Online, SharePoint, Teams, Power BI, and Power Platform, mapped to NIST SP 800-53 and MITRE ATT&CKMITRE ATT&CKA publicly maintained knowledge base of adversary tactics and techniques observed in real attacks, maintained by MITRE. Cyber tools use it as a common taxonomy to classify, map, and communicate threat behavior.. First committed in 2022, it has 67 contributors and stayed active with over 700 commits in the past year, most recently releasing 106 days ago.
ScubaGear is an assessment tool that verifies a Microsoft 365 tenant's configuration conforms to CISA SCuBA Secure Configuration Baseline policies.
How ScubaGear helps
Which settings in my M365 tenant fall short of the CISA baselines?
queries Entra ID, Exchange Online, SharePoint, Teams, Power BI, and Power Platform through their APIs and evaluates every setting against the Rego policies, listing each control that passes or fails
Which risky applications or service principals have access to my tenant?
flags Entra ID registered apps and third-party service principals holding high-risk permissions, surfaced as named entries in the results with the permissions that triggered them
Are my conditional access policies actually enforcing what I think they are?
evaluates conditional access rules automatically against the baseline conditions and reports a pass only when the configured conditions are genuinely met, rather than requiring a manual read of the policy
Which of my failing checks are exceptions I've already accepted?
lets a practitioner exclude named applications, guests, or Power Platform environments from scope, and lets results for specific policies be annotated so accepted exceptions show up in the HTML report instead of as unexplained failures
How do my hybrid Exchange settings measure up against the baseline?
collects legacy Exchange hybrid configuration and dedicated hybrid app configuration alongside the standard cloud settings, so hybrid-specific gaps show up in the same report
Can I check just one M365 product instead of re-running everything?
runs the assessment workflow against an individual product rather than requiring a full suite run, producing that product's report on its own
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 ScubaGear, 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 ScubaGear 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
17 entries
No entries match these filters.
- October 20264
- September 20261
- May 20261
- February 20261
- July 20251
- February 20251
- November 20241
- June 20241
- May 20241
- February 20241
- December 20231
- March 20231
- December 20221
- October 20221
Project health
Issue, contributor and maintainer activity in cisagov/ScubaGear, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 25 +4 vs prior 12 months
- Maintainers 6 +3 joined · −6 left, last 12 months
- Bus factor 3 committers behind half the commits
- Community-filed 15% of issues opened, last 12 months
- Median time to close 56 days first maintainer reply 6.6 days
- Open backlog 213 of 1,524 issues ever filed
- Issues opened / month 3 · 14 communitymaintainers
- Open backlog 213
- Contributors / month 10
- Commits / month 15
- Stars 2,672
- bugs 38%
- features 51%
- questions 1%
- docs 0%
- other 10%
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.