Why Should You Check a Crypto Custody Provider’s SOC 2 Report?
You should check a crypto custody provider’s SOC 2 report because it is issued by an independent auditor and shows whether the provider’s internal controls are suitably designed and whether they have operated effectively over a period of time, rather than being just a promise on its website. For businesses that entrust private keys and assets to a custodian, this report is one of the most direct pieces of third-party evidence when choosing a provider. That said, SOC 2 covers only organization-level controls, so understanding its scope and limitations matters just as much.
What Is a SOC 2 Report?
A SOC 2 report is an attestation report issued by a certified public accountant on a service organization’s internal controls. The American Institute of Certified Public Accountants (AICPA) defines SOC (System and Organization Controls) as a suite of services that CPAs can provide, and the official SOC 2 guide is titled “SOC 2® Reporting on an Examination of Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy”.
As the title suggests, SOC 2 examines controls relevant to security, availability, processing integrity, confidentiality and privacy. These five areas are what are commonly called the Trust Services Criteria. A provider does not necessarily include every one of them in the audit scope, so the first thing to do when you receive a report is to confirm which ones it covers.
According to the AICPA SOC 2 guide, these reports are intended to give report users information about the service organization’s system to help them assess the risks of working with the provider. The guide also expects users to have sufficient knowledge of the provider and its system, so the full report is usually provided only to specific parties such as customers, business partners and regulators, rather than published openly.
What Is the Difference Between SOC 2 Type I and Type II?
Type I looks at the design of controls at a point in time, while Type II looks at how controls actually operate over a period. The AICPA SOC 2 guide states that Type I examines whether controls are suitably designed as of a specific date; Type II also covers the system description and control design, and further examines whether the controls operated effectively throughout the period.
This distinction is critical for custody. A Type I report can show only that approval workflows, access management and change management were properly designed on the audit date, but it cannot prove that these controls were strictly followed in the months that followed. A Type II report includes the auditor’s tests of controls and the results, and this section appears only in Type II reports.
The length of the audit period is also worth noting. As Safeheron explained when it achieved SOC 2 Type II certification again, Type II requires the auditor to examine how controls actually operate throughout a longer period (typically 6 to 12 months), verifying consistency of execution rather than completeness of documentation. If a provider can produce only a Type I report, it is worth asking about its Type II timeline.
Which Parts of a SOC 2 Report Should You Focus On?
The parts to read first are the auditor’s opinion, the system description and the results of control testing. According to the AICPA SOC 2 guide, a report consists of a system description prepared by management, management’s assertion and the service auditor’s opinion, and a Type II report also includes the auditor’s tests of controls and their results. The auditor’s conclusions on the system description and controls, along with the test results for each control, directly affect your judgment of the provider.
The system description defines the boundaries of the report. You need to confirm whether the wallets, signing services and management console you plan to use are in scope, and whether the audit period is recent enough. If the provider relies on subservice organizations such as cloud service providers, the guide allows their controls to be included in the report (the inclusive method) or excluded from it (the carve-out method). If the latter is used, you will also need to understand the assurances for the subservice organization separately.
Another section that is easy to overlook is the Complementary User Entity Controls. It lists controls that customers must perform themselves, and the provider’s controls can meet their commitments only when these are in place. For custody customers, this often corresponds to their own team’s account permissions, approver settings and device management. Checking these points together with questions about key shares, transaction policies and asset recovery makes up the questions to ask before choosing an MPC custody provider.
How Is SOC 2 Different From ISO/IEC 27001?
SOC 2 is an auditor’s attestation report on specific controls, while ISO/IEC 27001 is a standard setting requirements for an information security management system. The International Organization for Standardization (ISO) gives ISO/IEC 27001:2022 the full title “Information security, cybersecurity and privacy protection — Information security management systems — Requirements”, and explains that it defines the requirements an information security management system (ISMS) must meet, guiding organizations of all kinds in establishing, implementing, maintaining and continually improving such a system.
The two have different focuses. ISO/IEC 27001 answers whether the provider has a systematic approach to security management; SOC 2 answers whether the controls the provider lists in its system description meet the Trust Services Criteria and (in Type II) whether they operated effectively during the audit period. The former looks at the system, the latter at the evidence, and the two documents complement rather than replace each other.
When checking an ISO/IEC 27001 certificate, look at the certification body, the scope of certification and the validity period; when checking SOC 2, look at the report type, the systems covered and the audit period. Taking Safeheron as an example, its Trust Center displays both ISO/IEC 27001:2022 and SOC 2 certifications: one demonstrates a sound management system, the other demonstrates controls put into practice.
Why Do You Still Need Code Audits When You Have SOC 2?
Because SOC 2 examines a service organization’s system description and internal controls, while the security of MPC custody also depends on cryptographic protocols and their code implementation. None of the SOC 2 components described in the AICPA guide is a review of the correctness of cryptographic protocols. Buyers should therefore ask providers directly: Have your MPC algorithm library and signing nodes undergone independent security audits? Who performed them, what were the scope and dates, and have the issues found been fixed?
The BitForge vulnerability disclosed in 2023 is one example. Tracked as CVE-2023-33241, it affected almost all mainstream open-source GG18/GG20 protocol implementations, and its root cause was the absence of necessary zero-knowledge proofs in the key generation phase. The BitForge vulnerability in GG18/GG20 MPC protocols explains how the attack works and also notes that Safeheron’s commercial service adds the relevant zero-knowledge proofs from CMP20/CGGMP21 to the GG18/GG20 protocols, so it is not affected by the vulnerability. Protocol-level risks like this fall outside the scope of what SOC 2 examines.
Safeheron’s security page lists several third-party audits: Kudelski Security audited the MPC algorithm library, Least Authority audited the MPC-ECDSA algorithm, SlowMist audited Safeheron MPC Node, and Cure53 audited Safeheron Snap. Only by looking at these code audits together with SOC 2 and ISO/IEC 27001 can you cover both organizational controls and technical implementation.
Conclusion
A SOC 2 report shows you whether a custody provider’s controls stand up to scrutiny by an independent auditor, especially through a Type II report’s testing of how controls actually operated during the audit period. Verifying it together with an ISO/IEC 27001 certificate and MPC code audits lets you assess a provider across three layers: management system, internal controls and cryptographic implementation.
Safeheron’s MPC Wallet-as-a-Service provides businesses with MPC key management and a policy engine.
Want to know how Safeheron’s SOC 2 and security audits apply to your custody scenario?
Looking for a secure way to manage digital assets?
Talk to our experts and find the right solution for your business.
Request a DemoLooking for a secure way to manage digital assets?
Talk to our experts and find the right solution for your business.