Home / Method
Method, read 13 Nov 2026
Seven criteria, weighted for the work a SOC 2 buyer needs done, fixed before any score
The question the index answers
Which SOC 2 compliance software gets a company with no compliance team to a SOC 2 report, and how much of the work is done with it? The weights follow what that buyer needs: someone to do the work with them and to deal with the auditor, evidence collected from the systems they already run, an audit that is booked and managed, an agent that drafts under review, controls that carry to the next framework, a price known before the call and proof that other companies have done it.
The weights and the scoring anchors
| Criterion | Weight | What is scored | Anchors |
|---|---|---|---|
| Expert help included | 25 | Named compliance experts who guide the work and deal with the auditor, inside the subscription and not as a separate purchase. Every vendor's score | Add: (a) compliance experts who guide implementation, documented as included in the subscription 4 (sold only as a separate purchase or add-on: 1; generic customer success or support only: 1); (b) a dedicated or assigned expert or team per customer 2; (c) the experts coordinate with or deal with the auditor, or support the customer through the audit 2; (d) experts do hands-on work (gap assessment, policy writing, readiness review), not only advice 2. Cap 10. Vendor-only evidence caps the total at 7. |
| Automation depth | 20 | Evidence collection, continuous control monitoring and integrations, as documented. Every vendor's score | Add: (a) automated evidence collection from connected systems, documented 3; (b) continuous control monitoring or automated tests with failure alerts, documented 3; (c) integration count as published: 200 or more 2, 100 to 199 1.5, 50 to 99 1, 1 to 49 0.5, none stated 0; (d) public integration documentation, an API, or custom integrations or custom tests 2. Cap 10. Vendor-only evidence caps the total at 7. |
| Audit path | 15 | Audit management in the product, an auditor network or partner auditors, penetration testing offered, and what is included against billed separately. Every vendor's score | Add: (a) audit management in the product (auditor access, audit workspace or portal, evidence requests handled in the product) 3; (b) an auditor network, partner audit firms or an affiliated audit firm the customer can use 3; (c) penetration testing offered by the vendor or a named partner 2; (d) a published statement of what is included in the subscription and what is billed separately for the audit or the penetration test 2. Cap 10. Vendor-only evidence caps the total at 7. |
| AI that does the work under control | 15 | An agent that collects evidence, drafts policies and answers questionnaires, with review and approval before anything is submitted. Every vendor's score | Add: (a) AI or an agent that collects evidence or carries out compliance tasks, documented 3; (b) AI that drafts or tailors policies 2; (c) AI that answers security questionnaires 2; (d) documented human review or approval before AI output is submitted or used, or an audit trail of AI actions 3. Cap 10. An AI feature with no documented review step scores 0 on (d). Vendor-only evidence caps the total at 7. |
| After SOC 2 | 10 | Control reuse when the next framework arrives. Every vendor's score | Add: (a) documented control cross-mapping, so one control satisfies several frameworks 5; (b) frameworks supported as published: 20 or more 3, 10 to 19 2, 5 to 9 1, fewer 0; (c) custom frameworks 2. Cap 10. Vendor-only evidence caps the total at 7. |
| Pricing transparency | 10 | A published price, published plan contents, and what the audit costs. Every vendor's score | Add: (a) a published price figure for at least one plan on the vendor's own pages 5; (b) published plan or tier contents 3; (c) a published audit cost, or a published statement with a figure for what the audit costs or that the audit fee is included 2. Third-party price reports do not count here; they appear in the SOC 2 Cost Ledger. The vendor-only cap does not apply to this criterion. |
| Proof | 5 | Customers as published and public review counts quoted as published. Every vendor's score | Add: (a) named customers as published by the vendor: 10 or more 3, 1 to 9 1.5, none 0; (b) public review count on G2 or Capterra as published there or as quoted: 1,000 or more 7, 500 to 999 6, 200 to 499 5, 50 to 199 3, 1 to 49 1, none found 0. 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.
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 'lacks'.
- Breadth facts (integration counts, framework counts, module counts, headcount, funding) carry at most 10 percent of any ranking. Here the integration count is at most 2 of the 10 points of Automation depth (4 percent of the total) and the framework count at most 3 of the 10 points of After SOC 2 (3 percent).
- 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.
- A second source on a host the vendor does not control takes precedence over a vendor claim.
- Equal totals share a rank (shown as 2=) and are listed alphabetically; a head-to-head with equal totals is a tie.
How the scores were made
Evidence was collected first: 861 dated records for 16 vendors, each with its source URL and read date. Each criterion was then scored for all 16 vendors by a scorer that saw the anchors and the evidence with vendor names replaced by codes, so the scorer was not told which vendor was which. A second reviewer checked every score against its evidence. 14 scores have moved since the first publication, all in the second evidence pass of 13 Nov 2026; each change is listed on the corrections page with its reason and sources.
The second evidence pass, 13 Nov 2026
On 13 Nov 2026 a second evidence pass ran the same searches for each of the 16 vendors on this index, at most 35 fetches per vendor, the same plan applied to every vendor alike. It logged 524 fetches for them, plus the audit-firm partner pages read once for all, and added 156 new records from 106 distinct source URLs, 53 third-party sources (pages the vendors do not publish), plus 6 discussion threads. The new evidence was scored blind, as in the first pass, and checked by a second blind reviewer. 14 scores moved on this index, and every ranked view was recomputed and is published as scored. The weights, the criteria and the anchors did not change. The corrections page lists every moved score, the old and new value, the reason and the sources.
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 on 12 Nov 2026.
Scroll the table sideways for every column.
| Situation | Expert help | Automation | Audit path | AI | After SOC 2 | Pricing | Proof |
|---|---|---|---|---|---|---|---|
| First report this quarter | 25 | 15 | 25 | 10 | 0 | 15 | 10 |
| Adding ISO 27001 and one more framework | 15 | 20 | 10 | 10 | 35 | 5 | 5 |
| Health and payments data | 20 | 20 | 15 | 10 | 25 | 5 | 5 |
| Lean security team | 40 | 15 | 10 | 20 | 5 | 5 | 5 |
| Enterprise replacing a legacy tool | 10 | 30 | 15 | 15 | 20 | 5 | 5 |
The ranked views
- Index: all 16 vendors ranked on the weights above.
- Head-to-head: two vendors compared on the weights above; the higher total wins. 7 pairs are published, each setting Scytale against one other vendor.
- Situations: each of the five situation pages ranks all 16 vendors on weights written for that buyer (shown in the table above) and names the top three.
One page per criterion
- Expert help included: all 16 scores with the reason for each.
- Automation depth: all 16 scores with the reason for each.
- Audit path: all 16 scores with the reason for each.
- AI that does the work under control: all 16 scores with the reason for each.
- After SOC 2: all 16 scores with the reason for each.
- Pricing transparency: all 16 scores with the reason for each.
- Proof: all 16 scores with the reason for each.
Evidence limits
- Vendor pages were read on 12 Nov 2026 and re-read in part on 13 Nov 2026 in the second evidence pass. A fact the vendor publishes only behind a login, a demo or a gated document could not be read, and is written "none found on" the date of the read, with the page checked.
- A price shown only after a demo request scores 0 on the price element of pricing transparency; a third-party price report does not count there, and appears in the SOC 2 Cost Ledger instead.
- Review counts on G2 or Capterra are quoted as the page showed them on the read date and weigh 5 percent of the total at most.
Sources
Last reviewed 13 Nov 2026.