
Compliance
SOC 2 Badge: What the Logo on a Trust Page Proves
A SOC 2 badge says a CPA issued a report, not its period, scope or carve-outs. What the AICPA logo allows, and a trust page with facts you can check.
Procurement reads a SOC 2 logo in a website footer as a pass mark. It was never designed to be one. It says an examination happened at some point, by some firm, over some scope. Every fact a buyer needs lives in the report, which is the part a trust page rarely shows.
Below: what the AICPA's logo programme publicly permits, the facts a badge omits read off a real public report, how to check the signing firm, and a trust page that fails its own build when its facts go stale. Reading a full report's exceptions is covered in SOC 2 reports: reading a vendor's exceptions and CUECs.
What a SOC 2 Badge Is a Claim Of
Treat a badge as a sentence and parse it. The AICPA says its SOC logos are "designed to help service organizations communicate they have received a SOC report issued by a licensed, independent CPA." That is the whole assertion: a report exists, and a licensed firm issued it.
What a buyer needs before relying on a vendor's controls, checked against the logo:
- Period. Which months the controls were tested over.
- Categories. Security alone, or other trust services categories too.
- Boundary. Which services and components were examined, and which excluded.
- Carve-outs and opinion limits. Which subservice organisations the examination excluded, and what the report says it was not conducted to evaluate.
- Issuer and date. Which firm signed, when, and whether it was licensed.
- Freshness. Whether any of the above still describes the system today.
None of the six travel with the image. The file renders identically whether the report behind it is current or has aged out, and whether the scope has grown or shrunk. The rule that should retire it lives in the AICPA's guidelines, which a buyer looking at a footer cannot see.
What the AICPA SOC Logo Programme Actually Permits
There are two programmes, and they badge different parties.
The first is for service organisations. The AICPA's public guidelines page describes a logo that "may be used by any service organization that has received at least one of the following reports: SOC 1, SOC 2, or SOC 3 from a licensed CPA or a non-U.S. equivalent" — and there the public page breaks off mid-sentence, after "non-U.S. equivalent (such as", with nothing following. No examples are visible, and no opinion-type, report-type or display-period condition is visible either; what the parenthetical was meant to list is not on the page. Note the threshold: at least one report, of any of the three types, from a licensed CPA or a non-U.S. equivalent. A company holding only a SOC 1 clears that sentence as surely as one holding a SOC 2.
The binding usage rules are not on that page. It lists two guideline files, SOC Logo for SO Guidelines.pdf and SOC 2 Logo for SO Guidelines.pdf, and both sit behind an AICPA & CIMA sign-in that needs a free account. The current editions were not opened for this article. An earlier edition circulates publicly: the AICPA's Terms, Conditions and Guidelines for Service Organizations, September 2020, whose paragraph 4 reads "You may use of [sic] the SOC for Service Organizations - Service Organizations Logo only for a period of twelve (12) months following the date of the SOC report issued by a licensed CPA. If after twelve months a new report is not issued, you must immediately cease use of the SOC for Service Organizations - Service Organizations Logo." That edition has no opinion-type condition. Vendor pages ranking for this query state further conditions about opinion type and report type; whether the current edition keeps, changes or adds to the twelve-month rule cannot be confirmed from public text, so this article claims neither that it was dropped nor that it still stands. If a display rule matters to a contract, read the current guidelines file, not a vendor's summary.
The second programme badges the auditor. The AICPA's SOC Logo for CPAs "may be displayed by licensed CPAs (or CPA firms) that perform SOC 1®, SOC 2®, or SOC 3® examinations by completing and submitting the required registration form." That page is reserved for AICPA & CIMA members. A firm's logo says it registered, nothing about any report it issued.
Attestation, Not Certification: Why 'SOC 2 Certified' Is the Wrong Noun
"SOC 2 certified" describes something that does not happen. The AICPA defines SOC as "a suite of service offerings CPAs may provide in connection with system-level controls of a service organization," used "to provide assurance reports" that users need "to assess and address the risks associated with outsourcing services." The output is a report, not a certificate.
In AWS's public SOC 3, the auditor writes that its "examination was conducted in accordance with attestation standards established by the American Institute of Certified Public Accountants" and ISAE 3000 (Revised), and that "Our responsibility is to express an opinion on the Assertion" — management's assertion about its own controls. Management asserts; a CPA examines and opines on that assertion. The output is an opinion on an assertion, not a certificate issued to the company.
An opinion is bounded by its period, its criteria and its stated limitations. The full comparison with a certification regime is in ISO 27001 vs SOC 2: certificate or auditor's opinion. On a trust page, write "received a SOC 2 Type 2 report" and say for which period.
Five Facts a Badge Cannot Carry, Read Off a Real Public Report
A SOC 3 is the useful specimen here because it is public. The AICPA says SOC 3 reports address the same trust services categories as SOC 2 without the same level of detail, and are "therefore" general use reports that "can be freely distributed"; where that report fits is covered in SOC 1 vs SOC 2. AWS's SOC 3 is used below purely as a worked example of where each fact sits. Whether that edition is the latest is beside the point.
1. The period
The cover reads "For the Period April 1, 2024 to March 31, 2025." The opinion repeats it: controls "were effective throughout the period April 1, 2024 to March 31, 2025, to provide reasonable assurance" that commitments were achieved "based on the applicable trust services criteria." Throughout a period, to reasonable assurance, against named criteria — not today.
2. The categories, and who chose them
The cover lists "Security, Availability, Confidentiality, and Privacy" — four of the five trust services categories; processing integrity is not among them. In the management assertion, AWS lists among its own responsibilities "Selecting the trust services categories and associated criteria that are the basis of our assertion." The company picks the categories, not the auditor and not the AICPA. A badge that just says SOC 2 hides which ones were picked.
3. The system boundary and its exclusions
Attachment A's system overview lists the in-scope services, and the list carries service-level exclusions: "Amazon Bedrock [excludes Amazon Bedrock Marketplace]" is one. If the feature you are buying sits behind an exclusion like that, the report does not cover it, and a logo cannot tell you. How a description draws that boundary is the subject of the AICPA SOC 2 guide article.
4. The limits of the opinion
The opinion also states its own limits. The examination "was not conducted for the purpose of evaluating AWS' cybersecurity risk management program," so no opinion is expressed on it. Nor was it conducted "for the purpose of evaluating the performance or integrity of AWS' Artificial Intelligence (AI) services," so no opinion is expressed on the performance or integrity of those services either. These are limits of the opinion, not carve-outs. In SOC vocabulary a carve-out is a subservice organisation whose controls the examination excluded, which is how the exceptions and CUECs article uses the term. A buyer needs both: the carve-outs say whose controls were left out, and the limits say which questions the opinion was never conducted to answer. Neither appears on a badge.
5. The issuer, the date and the projection limitation
The opinion appears under Ernst & Young LLP's letterhead as an "Independent Service Auditor's Assurance Report" addressed to AWS management and dated June 3, 2025 — about two months after the period ended. Then the clause every badge silently overrides: "the projection of any evaluations of effectiveness to future periods … is subject to the risk that controls may become inadequate because of changes in conditions." The ellipsis hides two more risks in the same sentence: that compliance with the controls may deteriorate, and that changes to the system or controls, or the failure to make needed changes, may alter the evaluation. Each of the three is a way the period's result stops describing today's system. The auditor declines to vouch for the future. A logo on a page implicitly vouches for the present.
Who Signed It: Checking the Firm Behind the Logo
The logo's own eligibility test is a licensed CPA, so check the licence. NASBA's CPAverify is "a CPA and accounting firm license search tool populated by official, publicly available, licensing data sent directly from the Boards of Accountancy," with "53 jurisdictions currently participating." NASBA calls it "the only free, single-source national database of licensed CPAs and accounting firms available to the public," and says it "includes markers of enforcement, non-compliance and disciplinary actions that have been issued by state boards."
Two limits. CPAverify is fed by US state boards, so it answers for US licences only; the logo wording admits a non-U.S. equivalent, which must be checked with its own regulator. And a lookup confirms standing, not the quality of a specific examination.
The reason to bother is on the AICPA's own SOC 2 page. A notice there says the AICPA "is looking into allegations published anonymously about the business practices of a compliance vendor that offers Systems and Organization Control (SOC) services." If auditors involved are found "to have not performed audits in accordance with professional standards, not been enrolled in peer review, and/or are unlicensed, the AICPA will take action with respect to its members," and it "assists governmental regulators – including referrals to state boards of accountancy and other entities as appropriate – regarding unlicensed firms and practitioners." The same notice says "SOC services should be thoroughly evaluated by service organizations and CPA firms" — the evaluators it names are the company buying the examination and the firm performing it.
AICPA ethics staff add a structural warning: "AICPA members increasingly enter business arrangements with SOC 2 tool providers and these relationships can raise significant threats to compliance with the Code of Professional Conduct." The page goes on to discuss the threats to independence and objectivity such arrangements raise, and how the Code's conceptual framework applies when the Code does not address an arrangement directly. Neither statement condemns any given report. Together they show the AICPA treats licensing, peer review and independence as live questions — which a badge cannot answer.
What to Ask For Instead of the Logo
- The SOC 2 report itself, under NDA. Read the opinion, the boundary, the exceptions and the complementary user entity controls — the method is in SOC 2 reports: reading a vendor's exceptions and CUECs.
- A bridge letter covering the gap since the period ended. It is the vendor's own statement, not a second opinion from its auditor; record it as such.
- The SOC 3, if one exists, for colleagues who cannot sign the NDA.
- The system description's boundary, checked against the service you are actually buying; the AICPA SOC 2 guide article explains what it must disclose.
A Trust Page That Carries Checkable Facts
Now the publisher's side. A trust page is a public claim about your report, and it should carry the facts a buyer would otherwise ask for — as data the page renders and anyone can fetch, not a logo and adjectives. The same discipline applies to privacy claims, covered in GDPR compliance statement examples.
The precedent for the one field that matters most is RFC 9116, already part of the Secure by Design procurement checklist. Its Expires field "indicates the date and time after which the data contained in the "security.txt" file is considered stale and should not be used"; it "MUST always be present," and it is "RECOMMENDED that the value of this field be less than a year into the future to avoid staleness." The RFC goes further: "Not having a "security.txt" file may be preferable to having stale information in this file." The same is true of a trust page.
{
"schemaVersion": 1,
"reportType": "SOC 2 Type 2",
"periodStart": "2025-10-01",
"periodEnd": "2026-09-30",
"categories": ["security", "availability", "confidentiality"],
"issuingFirm": {
"name": "Example Assurance LLP",
"licenceJurisdiction": "US-CO",
"verifyUrl": "https://cpaverify.org/"
},
"reportDate": "2026-11-12",
"scopeSummary": "Production platform for the Example Ledger service in two regions; marketing site and internal tooling excluded.",
"carveOuts": [
"Colocation provider carved out; its own SOC 2 Type 2 is available on request"
],
"requestUrl": "https://example.com/trust/request",
"bridgeLetterAvailable": true,
"soc3Url": null,
"expires": "2027-09-30"
}The schema assumes a Type 2. periodStart and periodEnd come from the opinion. issuingFirm carries the licensing jurisdiction so a buyer can look it up. scopeSummary and carveOuts restate the boundary and the subservice carve-outs — the part most likely to disappoint, so state it first. Features released after periodEnd are outside the opinion by definition; say that in the page's prose rather than listing it as a carve-out, because nothing was carved out. soc3Url stays null until a SOC 3 exists. expires is the commitment: after that date, do not rely on this file.
Making Staleness Fail the Build
An expiry date helps only if something reads it. The check below (Node 20+, no dependencies) fails when a required field is missing, a date is malformed, the period runs backwards, the report predates its own period end, expires has passed, or periodEnd is older than MAX_PERIOD_AGE_DAYS.
That threshold is the publisher's policy, not an AICPA or auditor rule: the default 455 days is a twelve-month period plus a ninety-day reporting lag. Pick your own. The motive is the auditor's projection clause — the further the period end recedes, the more the opinion describes the past.
// scripts/check-trust-facts.mjs — fail when published trust facts are incomplete or stale.
import { readFile } from "node:fs/promises";
import process from "node:process";
const DAY_MS = 86_400_000;
const REQUIRED = [
"reportType", "periodStart", "periodEnd", "categories", "issuingFirm",
"reportDate", "scopeSummary", "carveOuts", "requestUrl", "expires",
];
const file = process.argv[2] ?? "trust-facts.json";
const maxAgeDays = Number(process.env.MAX_PERIOD_AGE_DAYS ?? "455");
const facts = JSON.parse(await readFile(file, "utf8"));
const errors = [];
if (!Number.isInteger(maxAgeDays) || maxAgeDays <= 0) {
errors.push("MAX_PERIOD_AGE_DAYS must be a positive integer");
}
for (const key of REQUIRED) {
if (facts[key] === undefined || facts[key] === null || facts[key] === "") {
errors.push(`missing field: ${key}`);
}
}
if (!Array.isArray(facts.categories) || facts.categories.length === 0) {
errors.push("categories must be a non-empty array");
}
if (!facts.issuingFirm?.name || !facts.issuingFirm?.licenceJurisdiction) {
errors.push("issuingFirm needs name and licenceJurisdiction");
}
// Parse YYYY-MM-DD strictly: reject 2026-02-30 instead of rolling it forward.
function day(key) {
const value = facts[key];
const ms = typeof value === "string" && /^\d{4}-\d{2}-\d{2}$/.test(value)
? Date.parse(`${value}T00:00:00Z`)
: Number.NaN;
if (Number.isNaN(ms) || new Date(ms).toISOString().slice(0, 10) !== value) {
errors.push(`${key} must be a real YYYY-MM-DD date`);
return null;
}
return ms;
}
const now = Date.now();
const start = day("periodStart");
const end = day("periodEnd");
const issued = day("reportDate");
const expires = day("expires");
if (start !== null && end !== null && start >= end) {
errors.push("periodStart must be before periodEnd");
}
if (end !== null && issued !== null && issued < end) {
errors.push("reportDate precedes periodEnd: a type 2 opinion covers a finished period");
}
// expires is valid through that whole UTC day; fail from the next midnight.
if (expires !== null && now >= expires + DAY_MS) {
errors.push(`expired after ${facts.expires}: renew the facts or take them down`);
}
if (end !== null && maxAgeDays > 0) {
const ageDays = Math.floor((now - end) / DAY_MS);
if (ageDays > maxAgeDays) {
errors.push(`periodEnd is ${ageDays} days old; policy allows ${maxAgeDays}`);
}
}
if (errors.length > 0) {
for (const error of errors) console.error(`trust-facts: ${error}`);
process.exit(1);
}
console.log(`trust-facts OK: ${facts.reportType}, period ends ${facts.periodEnd}, expires ${facts.expires}`);
Run it on every push and pull request so a careless edit cannot ship, and on a schedule so the calendar alone can turn it red. Make it a required status check and a stale file blocks the next release. A scheduled failure also opens one reminder issue.
name: trust-facts
on:
push:
branches: [main]
pull_request:
workflow_dispatch:
schedule:
# Weekly, Monday 06:00 UTC. In a public repository GitHub disables
# scheduled workflows after 60 days with no repository activity.
- cron: "0 6 * * 1"
permissions:
contents: read
jobs:
check:
runs-on: ubuntu-latest
permissions:
contents: read
issues: write
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 22
- name: Check trust facts
env:
MAX_PERIOD_AGE_DAYS: "455"
run: node scripts/check-trust-facts.mjs trust-facts.json
- name: Open a renewal reminder
if: failure() && github.event_name == 'schedule'
env:
GH_TOKEN: ${{ github.token }}
RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
run: |
title="Trust facts are stale: request the bridge letter or new report"
open=$(gh issue list --repo "$GITHUB_REPOSITORY" --state open \
--search "in:title \"$title\"" --json number --jq length)
if [ "$open" = "0" ]; then
gh issue create --repo "$GITHUB_REPOSITORY" --title "$title" \
--body "Scheduled trust-facts check failed: $RUN_URL"
fiOne trap. GitHub's documentation warns that "In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days." A quiet trust-page repository is exactly where that bites: the check can switch itself off before the date it exists to catch. Watch the workflow's enabled state. The same page adds two related facts. A fork of a public repository starts with its scheduled workflows disabled by default, so a team that forks a template trust-page repository inherits a check that never runs until someone turns it on. And a disabled workflow is re-enabled from the GitHub UI, the REST API, or the GitHub CLI. Re-enabling is easy; noticing is the hard part. Put the enabled state on the same review calendar as the bridge-letter request.
Failure Modes and the Exit Ramp
Trust pages fail quietly, and each failure maps to a field:
- The logo outlives the report. The September 2020 AICPA terms say to cease use twelve months after the report date absent a new report; nothing on the page enforces that.
expiresand the period-age check turn that into a red build. - Scope narrows silently. A service drops out of the boundary between reports; the badge is unchanged.
scopeSummaryandcarveOutschange in a reviewed diff, and that diff is the disclosure. - Categories drop. Availability was examined last year and not this year.
categoriesshows it. - The audit firm changes. Not a problem in itself, but
issuingFirmchanging is a signal to re-check the licence. - The page claims certification.
reportTypemakes the honest wording the default.
The exit ramp is the format. A plain JSON file in your own repository renders on any static host, can be read by any tool that parses JSON, and survives a change of audit firm — only the values change. A badge means what its supplier says it means. A facts file is yours, diffable, and versioned; when a vendor portal or contract ends, the facts move with you. The wider case for keeping exit evidence of this kind is in third-party risk when one vendor runs your platform.
It works in the buying direction too: keep one such file per vendor whose SOC 2 you rely on and run the same check over them. Controls evidence for your own platform, the other half of that loop, is in SOC 2 on self-hosted Kubernetes.
The Long Game: Claims That Age Honestly
Every assurance claim decays. The auditor says so in the report, and RFC 9116 says so about a one-line contact file. What separates an honest trust page from a decorative one is whether the decay is visible: a period you can read, a firm you can look up, an expiry a machine enforces. Over a decade auditors, scope and categories change; a versioned file records that history, a logo erases it. Publish claims that carry their own expiry, and let them fail loudly when they lapse.
§FAQ/Common questions
Frequently asked
What does a SOC 2 badge on a website prove?
That the company has received a SOC report from a licensed CPA. The AICPA's public guidelines page describes its service-organization logo as usable by any service organization that has received at least one SOC 1, SOC 2 or SOC 3 report from a licensed CPA or a non-U.S. equivalent. The badge carries no period, categories, boundary, carve-outs or issuer; display duration is set in the AICPA's logo guidelines, and the September 2020 edition limits it to twelve months after the report date.
Is a company 'SOC 2 certified'?
No. A SOC 2 is an examination performed under the AICPA's attestation standards, ending in a CPA's opinion on management's assertion about its controls over a stated period. It produces a report, not a certificate. 'Received a SOC 2 Type 2 report for the period …' is the accurate wording.
How can I verify the CPA firm behind a SOC 2 report?
Look the firm up in NASBA's CPAverify, a free licence search populated by US state boards of accountancy with 53 participating jurisdictions, which also shows enforcement and disciplinary markers. A non-US issuer has to be checked with its own national regulator.
What should I ask a vendor for instead of the logo?
The SOC 2 report under NDA, a bridge letter from the vendor covering the gap since the period ended, and the SOC 3 if one exists. Then read the opinion, boundary, exceptions and complementary user entity controls rather than relying on the badge.
Further reading
- SOC 2 Reports: Reading a Vendor's Exceptions and CUECs
- ISO 27001 vs SOC 2: Certificate or Auditor's Opinion
- AICPA SOC 2 Guide: The System Description Sets the Scope
- SOC 1 vs SOC 2: Which Report Your Customer's Auditor Needs
- GDPR Compliance Statement Examples: What You Can Claim
- Secure by Design Is Now a Procurement Question
- SOC 2 on Self-Hosted Kubernetes: Own the Evidence
- Third-Party Risk When One Vendor Runs Your Whole Platform
Executive Briefing
Thirty minutes to clarify your infrastructure risk
Walk us through your vendor footprint and regulatory constraints. We will tell you honestly where sovereignty creates leverage — and where it does not. No pitch deck. No obligation.