Trust center
The trust center criterion, tested by Black October
Short answer
Between 20 and 22 October 2026 the eMudhra certificate authority compromise, the PHP2Shell flaws and the Node2Shell flaw landed within two days. Drata reported that updates published in its customers' trust centers ran 8x a normal week, 36% of its enterprise customers posted an update, most within 24 hours, and subscriber emails rose from 2,506 to 33,359. The ledger's trust center and questionnaires column scores published features; a week like this is what those features are for. Here is how to read the column against it.
By the SOC 2 Vendor Compare ledger desk · Published 2026-11-04 · Editorial assessment
What happened?
On 20 October The Register reported that eight eMudhra intermediate certificate authorities had private keys weak enough to recover; eMudhra said on 22 October it was leaving the TLS certificate business. On 21 October PHP patched CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell, scored 9.2 on CVSS v4.0 and fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35; Node.js patched CVE-2026-111497 the same day. CISA listed the PHP flaws as exploited with a federal deadline. Researchers called the month Black October.
What did Drata publish?
Figures from what it calls its Trust Graph for 19 to 23 October: vulnerability and incident updates at 8x a typical week; 36% of enterprise customers publishing an update about the three events, most within 24 hours of the patches; 33,359 emails sent to trust center subscribers against 2,506 the week before, more than four times the previous high during the Citrix vulnerabilities in late September; and subscriptions nearly doubling week over week. Drata's own trust center shows a Node.js update stating production services were patched as of 23 October and an eMudhra statement dated 27 October.
How does the ledger score trust centers?
On published features, weight 10. Vanta scores 9: Trust Center on every plan, questionnaire automation from Plus, advanced Trust Center on Professional. Scytale and Drata score 8: Scytale's Trust Center is pre-filled from compliance data with human-reviewed AI questionnaire answers; Drata's Trust Center Standard is on Foundation with a separate Assurance platform. Sprinto and Secureframe score 7: a public trust center with a custom domain and a 20-a-year questionnaire cap on Sprinto Foundation; Trust Center on Secureframe Fundamentals with questionnaire automation on Complete. Thoropass scores 2: no trust center or questionnaire product described.
What can the column not tell you?
How fast an update reaches subscribers, whether a technical update can be scoped to reviewers under NDA while the public sees status only, whether one approved answer can feed every questionnaire reply, and what analytics you get afterwards. Those are behaviors, and the only vendor that published any behavior for the week is Drata. We do not score usage figures from one vendor against feature lists from five.
What should a buyer test?
In the trial, on a weekday evening: publish a test update and time the notification; import a subscriber list; scope an update to an NDA audience; add an approved answer to the questionnaire knowledge base and send yourself a questionnaire; read the analytics the next morning. Then ask the vendor for its own trust center's updates from 20 to 27 October, which are public, and read how it handled its own week.
Does this change the ledger?
No. Each vendor profile now links to its own public trust center under the trust center entry where we have the URL, so you can read the vendor's own Black October updates as a sample of the product.