Home / Method
Method, read 13 Nov 2026
Seven criteria, weighted for a team that runs several frameworks, fixed before any score
The question the index answers
Which compliance automation tool keeps several frameworks current at once on one control set, without a larger team? A security or GRC lead who runs several frameworks at once and wants them kept current without a larger team. The weights are the ones that buyer uses: how many frameworks the control set carries, whether the tool tests continuously, whether its agents act under approval, whether experts come with it, whether risk and vendor work sits in the same product, whether the price is published, and whether the vendor can be checked.
The weights and the scoring anchors
| Criterion | Weight | What is scored | Anchors |
|---|---|---|---|
| Framework coverage and reuse | 25 | Frameworks supported as published, control cross-mapping, custom frameworks. | Add: (a) matrix coverage: 6 x (supported + half of partial) / 20, rounded to the nearest 0.5; (b) documented control cross-mapping, so one control and its evidence satisfy several frameworks 2; (c) custom frameworks 1; (d) headline framework count as published: 80 or more 1, 40 to 79 0.5. Cap 10. Vendor-only evidence caps the total at 7. |
| Continuous monitoring and integrations | 20 | Automated tests, drift alerts and the integrations list as published. | Add: (a) automated control tests running continuously, documented 3; (b) alerts when a control drifts or a test fails, documented 2; (c) integration count as published: 300 or more 2, 150 to 299 1.5, 75 to 149 1, 1 to 74 0.5, none stated 0; (d) Integration Ledger coverage: 0.5 for each of cloud, identity, HR, code, ticketing and endpoint with at least one named integration published. Cap 10. Vendor-only evidence caps the total at 7. |
| Agents that act under control | 15 | AI agents that gather evidence, answer questionnaires and flag gaps, with approval and an audit trail. | Add: (a) AI or an agent that gathers evidence or carries out compliance tasks, documented 3; (b) AI that answers security questionnaires 2; (c) AI that flags gaps or proposes remediation 2; (d) documented human approval before AI output is used, or an audit trail of agent actions 3. Cap 10. An AI feature with no documented approval or audit trail scores 0 on (d). Vendor-only evidence caps the total at 7. |
| Human expertise | 15 | Experts, audit support or advisory included with the product. | Add: (a) compliance experts or advisory documented as included with the product 5 (sold only as a separate purchase: 1; generic customer success or support only: 1); (b) audit support: auditor coordination, an auditor network or an affiliated audit firm 3; (c) a dedicated or assigned expert or team per customer 2. Cap 10. Vendor-only evidence caps the total at 7. |
| Risk and vendor modules | 10 | Risk register, vendor risk and a trust center in the same product. | Add: (a) a risk register or risk management module in the product 3.5; (b) vendor or third-party risk management in the product 3.5; (c) a trust center in the product 3. Cap 10. Vendor-only evidence caps the total at 7. |
| Pricing transparency | 10 | A published price and published plan contents. | Add: (a) a published price figure for at least one plan on the vendor's own pages 6; (b) published plan or tier contents 4. Third-party price reports do not count here. The vendor-only cap does not apply to this criterion. |
| Proof | 5 | Customers as published, public review counts, certifications the vendor itself holds. | Add: (a) named customers as published by the vendor: 10 or more 3, 1 to 9 1.5; (b) public review count on G2 or Capterra as published there or as quoted: 1,000 or more 4, 500 to 999 3.5, 200 to 499 3, 50 to 199 2, 1 to 49 1; (c) the vendor's own SOC 2 report or ISO 27001 certificate, as published on its trust center or security page 3. Cap 10. |
Each criterion is scored 0 to 10 from the evidence files, in steps of 0.5. The total is the weighted mean on a 0 to 10 scale: sum(score x weight) / 100, published to two decimals. Totals are shown to two decimals so that close results are visible. Each criterion has its own page with all 16 scores, reasons and sources.
The rules every score follows
- A claim published only by the vendor itself (its site, documentation, press releases, customer stories it publishes) scores at most 7 of 10 on a criterion until a second source not controlled by the vendor confirms it. Pricing transparency is the exception: there the vendor's own publication is the thing measured.
- None found scores 0 for that element and is written 'none found on <date>', never 'has no'.
- Breadth facts (integration counts, framework counts, module counts, headcount, funding) carry at most 10 percent of any ranking. Here the headline framework count is at most 1 of the 10 points of Framework coverage and reuse (2.5 percent of the total) and the integration count at most 2 of the 10 points of Continuous monitoring and integrations (4 percent).
- Framework coverage is read from the Framework Coverage Matrix: each of the twenty frameworks is supported, partial or none found, with source and date. Partial means the vendor publishes the framework as a template, a mapping or a beta without full control and evidence support, or names it only as a service.
- Scores are given blind: the scorer sees coded vendors, the rubric and the evidence, and is not told which vendor any code is.
- No weight or criterion changes after the first score exists. A score changes only when a sourced fact changes, and the change is logged with the fact.
- Equal totals share a rank (shown as 1=) and are listed alphabetically. Tied tools have totals equal to the second decimal.
- A score changes only when a sourced fact changes. Every change is logged on the corrections page.
How the scores were made
Evidence was collected first: 697 fact records and 320 matrix cells for 16 tools, each with its source URL and read date. Each criterion was then scored for all 16 tools by a scorer that saw the anchors and the evidence with vendor names replaced by codes. The framework fit scores below are computed from the matrix cells by a fixed rule, with no judgment involved.
Second evidence pass, 13 Nov 2026
A second evidence pass ran on 13 Nov 2026, with one search plan applied to every vendor alike. It added 134 records from 95 distinct source URLs, 48 of them third-party sources. Blind scorers read only the new evidence and only the criteria it touches. 10 criterion scores moved on this site, 7 matrix cells gained a second source, and every change is on the corrections page. Weights, criteria and anchors did not change.
Situation weights
Each of the five buyer situations ranks the same scores on its own weights, written for that buyer and committed with the default weights. The situation pages name the top three.
Scroll the table sideways for every column.
| Situation | Coverage | Monitoring | Agents | Human | Risk and vendor | Pricing | Proof |
|---|---|---|---|---|---|---|---|
| Startup that needs a first SOC 2 report this quarter | 10 | 20 | 10 | 25 | 5 | 20 | 10 |
| Scaleup adding ISO 27001 and one more framework | 35 | 20 | 10 | 15 | 10 | 5 | 5 |
| Company holding health or payments data | 30 | 20 | 10 | 15 | 15 | 5 | 5 |
| Lean security team with no compliance hire | 15 | 15 | 20 | 35 | 5 | 5 | 5 |
| Enterprise replacing spreadsheets and a legacy GRC tool | 30 | 25 | 15 | 5 | 20 | 0 | 5 |
Framework view weights
Each framework page ranks all 16 tools on its own weights, where framework coverage and reuse is replaced by that framework's fit. From the framework's cell in the Framework Coverage Matrix: supported, confirmed by a source the vendor does not control 10; supported, vendor's own pages only 7; partial 4; none found 0. The cell alone decides the score.
Scroll the table sideways for every column.
| Framework | Fit | Monitoring | Agents | Human | Risk and vendor | Pricing | Proof |
|---|---|---|---|---|---|---|---|
| HIPAA | 30 | 20 | 10 | 15 | 15 | 5 | 5 |
| PCI DSS | 30 | 25 | 10 | 15 | 10 | 5 | 5 |
| CMMC 2.0 | 35 | 15 | 10 | 20 | 10 | 5 | 5 |
| NIS2 | 30 | 15 | 10 | 15 | 20 | 5 | 5 |
| DORA | 30 | 15 | 10 | 15 | 20 | 5 | 5 |
| GDPR | 30 | 15 | 10 | 15 | 20 | 5 | 5 |
The ranked views
- index: All profiled tools ranked on the weights above.
- frameworks: Each framework page ranks all tools on the weights in data/weights/complianceautomationtools-frameworks.json, where Framework coverage and reuse is replaced by that framework's own fit score.
- situations: Each situation page ranks all tools on its own weights in data/weights/complianceautomationtools-situations.json and names the top three.
- criteria: each criterion page ranks all 16 tools on that criterion alone.
Evidence limits
- Of 320 matrix cells, 76 read none found on 12 Nov 2026. None found is a statement about the pages read, not about the product.
- G2, Capterra, TrustRadius and Software Advice returned 403 to the research runner for every tool on 12 Nov 2026, and G2 and Capterra still returned 403 on 13 Nov 2026, so review counts rest on counts that vendors quote on their own pages, labeled as theirs, and on PeerSpot.
- sprinto.com returned 403 to the research runner on 12 Nov 2026; Sprinto's evidence comes from docs.sprinto.com and third-party pages, and its scores reflect what could be read that day.
- Prices are scored on what each vendor publishes on its own pages; third-party price reports are recorded but not scored.
Ties and rounding
Totals are computed from the unrounded weighted mean and published to two decimals. Tools whose totals are equal share a rank; the next rank is skipped, so two tools at 1= are followed by 3.
Sources
- creativecommons.org/licenses/by/4.0, read 12 Nov 2026
- nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-137.pdf, read 12 Nov 2026
Last reviewed 13 Nov 2026.