Type a vendor's name into a search bar and add 'trust center' and you will usually land on one of three things: a page built on Vanta's trust centre product, Microsoft's sprawling Trust Center hub, or SAP's own compliance catalogue. All three are self-published. The vendor controls the copy, chooses which badges to show, and decides when to update a status line. None of that makes the page worthless: a trust centre is still the fastest way to find a SOC 2 report request form or a subprocessor list. It is not, however, the same thing as independently dated evidence. This article compares what each type of trust centre discloses against the dated rows held elsewhere, in a registry, in an audit report, in a government marketplace, and shows where the gap between 'we claim this' and 'here is the certificate, dated, from the registry' actually opens up.
What a trust centre is, and is not
A trust centre is a public page, not a piece of software a buyer can click through to see access logs or audit trails inside the vendor's own systems. That distinction matters enough that we wrote a separate explainer: What Is a Trust Centre? Vendor Evidence vs Office Settings covers the difference between a vendor's public disclosure hub and the admin console a buyer manages inside their own tenant. A trust centre sits firmly on the vendor's side of that line. It exists to shorten the sales cycle: instead of emailing a security team for a SOC 2 report or a subprocessor list, a buyer finds a page with badges, a request form, and sometimes a downloadable document. The page is written, hosted and updated by the vendor. Nobody audits the page itself, only the underlying certificate, report or registry entry that the page claims to summarise.
Three operators, three different models
Most vendors a buyer actually evaluates fall into one of three patterns. Some buy a trust centre product, usually Vanta's, and get a templated page with a framework list down the side, uploaded documents and a subprocessor table. Some are large enough to run their own, like Microsoft's Trust Center or SAP's Trust Center, both of which catalogue compliance claims across dozens of product lines rather than one product. The software differs, the layout differs, but the underlying problem is the same: the page is an index of claims the vendor chose to publish, not a feed of independently verified status.
| Trust centre type | Who writes it | What it typically shows | What it rarely shows |
|---|---|---|---|
| Vanta-built (a typical SaaS vendor's page) | The vendor, using Vanta's templates | Framework badges, uploaded reports, a subprocessor list, a request form | The underlying audit period dates, or whether a DPF listing is still active in the registry |
| Microsoft Trust Center | Microsoft, centrally | A compliance offerings matrix across hundreds of Azure, Microsoft 365 and Dynamics 365 services | A single expiry date per product; reports sit behind the Service Trust Portal and an NDA |
| SAP Trust Center | SAP, centrally, by cloud product line | Certification status per product, such as SuccessFactors, Ariba or S/4HANA Cloud | A consolidated view across product lines; each line's status has to be checked separately |
How three trust centre operators structure self-published compliance claims.
Where self-assertion and dated evidence diverge
The badge on a trust centre and the dated row in a registry or an audit report answer different questions. The badge says, in effect, that the vendor believes a framework applies to them. The dated row says that as of a specific date, a specific auditor, registrar or government programme confirmed a specific scope. The gap between the two shows up in predictable places.
- A HIPAA badge displayed on the page with no business associate agreement actually captured for the customer looking at it.
- A Data Privacy Framework listing still shown as active on the trust centre well after the underlying registry entry has gone inactive.
- An ISO 27001 statement that still cites the 2013 edition after the deadline; see ISO 27001:2013 lapsed on 31 October 2025 for what the index found when it checked vendor pages against the IAF transition deadline.
- A SOC 2 claim with no Type I or Type II stated, so a buyer cannot tell whether the report describes a design at a single point in time or an operating period of evidence.
- 31 Oct 2025
- ISO 27001:2013 lapse date
- under IAF MD 26, certificates citing the 2013 edition stopped being valid evidence
- 4 Jul 2026
- FedRAMP Certified effective date
- the Consolidated Rules for 2026 made this the single designation; Ready became legacy on 28 Jul 2026
- 3
- trust centre operating models compared here
- Vanta-built, Microsoft Trust Center, SAP Trust Center
FedRAMP Certified is now the programme's single designation under the Consolidated Rules for 2026; agencies and vendors should no longer treat a 'Ready' listing as current.
Microsoft Trust Center: breadth without a single expiry date
Microsoft's Trust Center is organised around products, not a single corporate status line. It lists compliance offerings across Azure, Microsoft 365, Dynamics 365 and a long list of other services, each with its own scope. A SOC 2 report for Azure covers a different boundary to one for Microsoft 365, and both sit behind the Service Trust Portal, which requires a Microsoft account and a signed agreement before the actual report downloads. The trust centre page states which frameworks apply to which product, which is genuinely useful for navigating a large catalogue, but it does not carry a per-product expiry date the way a registry row does. A buyer still has to go and open the actual report to see the audit period it covers, and still has to match the product named in that report to the product they are actually buying.
SAP Trust Center: one brand, many cloud product lines
SAP's Trust Center works the same way, organised by cloud product rather than by company. SuccessFactors, Ariba, Concur and S/4HANA Cloud each carry a separate certification status, and a badge that applies to one does not automatically apply to another. SAP links out to certificates for frameworks such as ISO 27001, and to audit report request forms for SOC reports, gated in a similar way to Microsoft's. The practical effect for a buyer is that 'SAP has ISO 27001' is not a complete answer. The real question is which SAP cloud service, under which certificate number, issued by which registrar, and valid until when, because the answer changes from one product line to the next.
The Vanta-built middle ground
A large share of the vendors a mid-market buyer actually evaluates do not run their own trust centre infrastructure. They buy a trust centre product, most commonly Vanta, and populate it themselves. Vanta's role is to automate evidence collection internally and to give the vendor a public page template with a framework list, uploaded documents, a subprocessor table and a request button for gated items such as a SOC 2 report. Vanta does not audit the vendor and does not act as a verifier of the public page's content. It does not confirm that a HIPAA badge has a signed business associate agreement behind it for every customer, or that a Data Privacy Framework listing is still active in the registry rather than lapsed. Those checks remain the vendor's job to keep current, and the buyer's job to verify independently.
A worked example: reading the claim against the row
Intercom runs its trust centre on Vanta, which makes it a useful worked example of exactly this gap. Rather than quoting figures here, look at three things directly on the live card below: how the HIPAA row is worded next to whether a business associate agreement has actually been captured, whether the Data Privacy Framework listing shows as active or lapsed, and whether a subprocessor list sits alongside the framework badges rather than being available only on request. Those three checks generalise to any Vanta-built page, not just this one, so the habit matters more than the specific vendor.

Intercom · Trust report
Customer support · Public evidence as of 16 Nov 2026
Framework overview
CertReports state for each framework with public evidence: 10 vendor-stated, 1 expired.
HIPAAVendor-statedBadge only, BAA not captured
SOC 2Vendor-statedTrust centre · 30 Sep 2026GDPRVendor-statedTrust centre · 30 Sep 2026
ISO 27001Vendor-statedTrust centre · 30 Sep 2026CSA STARVendor-statedTrust centre · 30 Sep 2026
ISO 27701Vendor-statedTrust centre · 30 Sep 2026
ISO 42001Vendor-statedTrust centre · 30 Sep 2026
ISO 27018Vendor-statedTrust centre · 30 Sep 2026
DPFExpiredListing inactive
2Documents and agreements
Legal and review documents Intercom publishes or offers, as of 30 Sep 2026.
- Subprocessor list · Public
- Privacy policy · Public
1Security practices
Public statements from Intercom, shown as statements, not attestations, as of 30 Sep 2026.
- Penetration testing · annual
14Subprocessors
Named on Intercom's public subprocessor list, last seen 30 Sep 2026.
Ably
Amazon Web Services, Inc.
Anthropic, PBC- CACartesia AI, Inc.
Cloudflare, Inc.
Eleven Labs, Inc.
Google
Mailgun Technologies, LLC- and 6 more on the evidence page
Reading any of the three in ten minutes
The checking process is the same whichever operator built the page. We cover it in full in How to read a trust centre in ten minutes; the short version is five steps.
- 1
Identify who built the page
A Vanta ribbon, a Microsoft or SAP domain, or a bespoke build each sets different expectations for what is self-service versus centrally maintained.
- 2
Separate the badge from the document
A framework name in a list is a claim. The certificate, report or registry entry behind it is the evidence. Open the document, not just the badge.
- 3
Check the date on the document, not the page
Trust centres rarely show when a badge was last confirmed. The certificate, the SOC 2 report cover page, or the registry entry always carries a date.
- 4
Check scope against product, not company name
A compliance claim for one product line, one Azure service or one SAP cloud offering, does not extend to every product the vendor sells.
- 5
Before you accept the badge
A short checklist closes most of the gap between a self-published trust centre and the evidence a risk review actually needs on file.
- Ask for the audit report itself if the trust centre only shows a badge, not a document.
- Check whether the subprocessor list is public on the page or only available on request; see How to check a vendor's subprocessor list for what a complete list should include.
- Note the scope: one product line's certificate rarely covers the whole company, especially for Microsoft and SAP.
- Record the date you checked, because trust centres update silently and a badge seen today may not match the certificate in six months.
The badge answers a different question to the date
A trust centre tells a buyer what a vendor is willing to claim in public. A registry, a report or a certificate tells a buyer what was actually confirmed, by whom, and until when. Both are useful. Only one is independently dated.
People also ask
What is microsoft trust center?
Microsoft Trust Center is a Microsoft-operated hub that lists the compliance offerings, certifications and audit reports claimed across its many cloud product lines, from Azure to Microsoft 365. It links to the Service Trust Portal for documents such as SOC 2 reports, usually gated behind an NDA. It is self-published: Microsoft decides what to list and when to update it, so a buyer should still check the dated certificate or report behind each claim rather than the catalogue page alone.
What is sap trust center?
SAP Trust Center is SAP's own compliance catalogue, organised by cloud product such as SuccessFactors, Ariba and S/4HANA Cloud, each carrying its own certification status. It links out to certificates and, for some frameworks, registrar detail. Like Microsoft's page, it is vendor-written and vendor-maintained, so dates and scope can lag behind the underlying certificate. Treat each product line separately rather than assuming one SAP badge covers every SAP service a buyer might use.
What is vanta trust center?
A Vanta trust centre is a public page a vendor builds using Vanta's compliance automation product to display its own compliance status: framework badges, uploaded reports, a subprocessor list and request forms for NDA-gated documents such as a SOC 2 report. Vanta supplies the software and layout; the vendor supplies and updates the content. It is self-asserted, not independently verified, so a buyer should still check the underlying certificate or registry date rather than the badge.
Solomon Amos · Founder, CertReports
Solomon builds CertReports, the public evidence index for vendor security reviews. PhD in machine learning and cybersecurity, two years embedded at HMRC digital programmes, founder of TapTax. He writes about what registries, trust centres and auditors actually publish, and how buyers can use it before the questionnaire goes out.
Read next on CertReports
You might also like
What Is a Trust Centre? Vendor Evidence vs Office Settings
Solomon Amos · 28 Oct 2026 · 10 min read