
GUIDE
How to Read a SOC 1 / SOC 2 Report for a Custodian
Crypto Bank Editorial Team · November 17, 2026
A SOC report is one of the more substantive documents a custodian can hand you, and also one of the more commonly misread. It is not a financial audit, not a security guarantee, and not an endorsement by the accounting firm that issued it — it is a structured description of specific controls, tested against a specific standard, over a specific period. Knowing how to read one is largely a matter of knowing what to look for in four or five particular places, rather than needing deep accounting expertise.
SOC 1 and SOC 2 answer different questions
Both are issued under American Institute of Certified Public Accountants (AICPA) attestation standards, and both are prepared by independent accounting firms, but they test different things. A SOC 1 report addresses controls relevant to a client’s financial reporting — it exists mainly for a client’s own external auditor, to help that auditor rely on the service organization’s controls rather than re-testing them directly. A SOC 2 report addresses a custodian’s own operational and security controls against the AICPA’s Trust Services Criteria: security, availability, processing integrity, confidentiality and privacy. Security is the one mandatory category; the other four are included only if the custodian chose to have them tested. For a crypto custodian specifically, a SOC 2 report is usually the more directly relevant document to a client evaluating operational security, since it speaks to access controls, key-management procedures and change management rather than financial-reporting mechanics.
Type I and Type II: a distinction inside the distinction
Either report type can be issued as a Type I or a Type II, and this difference matters as much as the SOC 1/SOC 2 split. A Type I report describes the custodian’s controls as designed, as of a single point in time — essentially, “these controls exist and are suitably designed, as of this date.” A Type II report goes further: it tests whether those controls actually operated effectively over a defined period, typically six to twelve months, based on the auditor’s testing of actual operation during that window. A Type I report is weaker evidence than a Type II, because a control can be well designed on paper and still fail in practice; always check which type you are looking at before weighing how much it tells you.
Reading the actual document, section by section
- The report title and the period or date covered. This tells you immediately whether it is Type I (a date) or Type II (a period), and how current the report is — a SOC 2 Type II covering a period that ended over a year ago is far less informative about current practice than a dated inclusion in the latest version.
- Management’s description of the system. This section, written by the custodian itself (not the auditor), describes what the system does and what controls management asserts are in place. It sets the scope of everything that follows; a narrow description means a narrow test, regardless of how thorough the testing within that scope was.
- The auditor’s opinion. Look for whether it is “unqualified” (the controls, as described and tested, met the criteria without exception) or “qualified” (one or more exceptions were found and are described). A qualified opinion is not automatically disqualifying, but the specific exception should be read, not skipped.
- The description of tests performed and results. In a Type II report, this is usually the most substantive section — for each control, the auditor describes exactly what it tested and whether the control operated effectively throughout the period, including any exceptions found even within an overall unqualified opinion.
- Complementary user entity controls. Most SOC reports include a list of controls the custodian expects its clients (or itself as an intermediary in a sub-custody chain — see our sub-custodian guide) to operate on their own side. The custodian’s own controls are only as effective as assumed if these complementary controls are actually in place too.
What a SOC report does not tell you
A clean SOC 2 Type II report is evidence of sound operational and security practices during the period tested. It is not evidence of solvency — it says nothing about the custodian’s balance sheet, its liabilities, or whether client assets are segregated from the custodian’s own in a legal sense. It is also not evidence about anything outside its defined scope: if the report covers one specific system or service, conclusions about a different product the same company offers are not supported by it. And it is backward-looking by construction — even a Type II report covering a recent period describes what already happened, not a live, ongoing guarantee about today.
Not the only framework in use
SOC reports are an American attestation framework, built under AICPA standards, and they are not the only control framework a custodian might hold. ISO/IEC 27001 certification, for instance, is a separate, internationally recognized information-security management standard, issued by accredited certification bodies rather than accounting firms, and tested against a different set of requirements than the AICPA’s Trust Services Criteria. A custodian operating internationally may hold a SOC 2, an ISO 27001 certification, both, or neither. Neither framework is simply “better” than the other, and a report or certificate under one framework is not directly equivalent to one under the other, even though both are commonly cited as evidence of strong security practice. Where a custodian cites a credential under either framework, confirm the issuing body and the scope rather than treating the label alone as sufficient.
Signs a cited SOC report deserves closer scrutiny
- The custodian references “SOC compliant” or “SOC certified” without naming SOC 1 or SOC 2, or Type I or Type II — phrasing that avoids the specific, checkable claim a genuine report would support.
- The report, or even a summary of it, is not made available to a prospective institutional client under any circumstances, including under a non-disclosure agreement.
- The period covered is unusually old relative to when it is being cited, suggesting the custodian has not kept the engagement current.
- The description of the system in scope is vague enough that it is unclear whether it actually covers the custody service being marketed, as opposed to some narrower or unrelated part of the business.
How this fits with attestation versus audit
A SOC report is itself a form of attestation engagement, in the same broad family as the reserves attestations discussed in our attestation vs. audit guide, just testing a different subject matter (operational controls, rather than an asset balance). Neither a SOC report nor a reserves attestation is a substitute for a full financial statement audit, and a custodian with a strong SOC 2 report and no audited financials has disclosed something real about its operations while leaving the solvency question entirely open.
Where this sits in the Custody Question
A SOC 2 report, particularly a recent Type II, is some of the stronger available evidence for the operational side of the first row of our Custody Question — who holds the keys, and how carefully. It contributes very little to the second row (insurance) and essentially nothing to the third (insolvency treatment), which are governed by separate documents entirely.
FAQ
- Will a custodian usually share its full SOC report?
- Often only under a non-disclosure agreement, particularly for institutional clients, because the detailed description of systems and controls is itself sensitive information. A custodian may publish only a summary or a statement that a current report exists and is available on request.
- Is an unqualified opinion the same as “no problems found”?
- Not exactly. It means the controls, as scoped and described, met the relevant criteria; it says nothing about risks outside that defined scope, and even an unqualified opinion can sit alongside noted exceptions on individual controls within the detailed testing section.
- Does a SOC 1 report matter for evaluating a custodian directly?
- Less than a SOC 2 for most client purposes, since it is oriented toward financial-reporting controls rather than the operational security questions most clients actually care about. It is more relevant to the custodian’s own clients’ external auditors.
- Can a custodian write its own control objectives for a SOC 2?
- Security is the one mandatory Trust Services Criterion, and the custodian chooses which of the other four categories (availability, processing integrity, confidentiality, privacy) to include, but the criteria themselves within each chosen category are set by the AICPA, not written by the custodian the way some older attestation formats allowed. This standardization is part of why SOC 2 reports from different custodians are more directly comparable than many other forms of self-published security claims.
Risk note
This guide explains how to read these reports generally; it does not assess whether any specific provider holds a current SOC 1 or SOC 2 report, of either type, or what that report says. Request and read the actual document, including its scope and period, before relying on it.
Not a bank. Not a deposit-taking institution. No FDIC, FSCS or deposit-insurance cover. Editorial only.
Not financial advice.