SOC 2 compliance: Attestation vs. certification, and why it’s important to get it right
Compliance and security demand precision, especially when data, assets, and huge investments are on the line. Even the way we talk about compliance deserves consideration because language sets the precedent for what actually happens in the world.
Without getting too philosophical, we want to briefly take the opportunity to discuss common terms surrounding SOC 2 Type I and Type II compliance. Specifically, what’s the difference between attestation and certification?
Semantics aside, it doesn’t really seem important at first glance, but ignoring semantics in the realm of compliance can be costly in every sense of the word. So what is the difference and why does it matter? Let’s hash it out.
The SOC 2 certification dilemma
You don’t have to Google too hard to find the phrases “SOC 2 certified” or “SOC 2 certification.” LinkedIn posts, blog announcements, and PR headlines all seem to be typical places to communicate the win, and you definitely should communicate it.
Achieving compliance success is a proud moment for any business, and one worth shouting across the rooftops. Investing the time and effort to plan, prioritize, and finally receive a SOC 2 report is a venerable benchmark of progress. But there’s a catch.
Technically, there’s no such thing as “SOC 2 certification.” Every time you’ve heard it or read it, it’s been wrong. A more detailed look into compliance jargon across the internet will also reveal another, more accurate phrase: “SOC 2 attestation.”
What is SOC 2 attestation?
The vast majority of companies that comply with SOC 2 are not under a legal or regulatory requirement to do so. In other words, SOC 2 is not a mandatory compliance framework. It is a voluntary attestation, which is then proven by a third-party auditor. That proof is your SOC 2 report—a living document providing interested parties information about your company’s commitment to security.
Since any CPA can attest to being compliant with SOC 2 controls, there is no certifying body. The American Institute of CPAs (AICPA) designs the SOC 2 standards, but it does not award certifications.
Therefore, there is no universally accepted SOC 2 certification. When a CPA reviews your company, there is no “pass or fail.” An auditor is simply an objective reference providing a report, for better or worse, that testifies to the state of your company’s security posture. “Failure” in SOC 2 generally comes in the form of a “qualified opinion,” meaning the auditor is telling the reader that your controls, or their execution, do not meet these particular criteria.
When a prospect or vendor inquires about your company’s security, they are asking for your attestation, not a certification. With this understanding in mind, your typical celebratory SOC 2 announcement headline should change.
from this: Llama Time, Inc. completes SOC 2 certification!
to this: Llama Time, Inc. successfully receives SOC 2 Type II attestation report.
To give a little more context, it also helps to understand what companies are actually attesting when it comes to SOC 2. Here’s a quick breakdown of the difference between SOC 2 Type I vs. SOC 2 Type II.
SOC 2 Type I attestation
SOC 2 Type I is a point-in-time, static snapshot that captures your business’s compliance frameworks as of a certain date or point in time. When an auditor is reviewing your business, they will investigate that snapshot to see whether or not the appropriate controls are present. Whether or not the controls are accurately present, an auditor will attest to, not certify.
SOC 2 Type II attestation
SOC 2 Type II is a compliance review that takes place over a period of time, usually 6-12 months, in contrast to a point-in-time snapshot. The auditor will collect evidence and investigate the operating effectiveness of your business’s controls over the period. This is the reason why Type II is more intensive and expensive, but it’s also why it’s more meaningful. Just like Type I, an auditor will produce an objective report, not a certification, that is neither “pass nor fail.”
About the author: Matt leads the Privacy and Compliance team at Vanta. He has spent his 20+ year career in security and information technology. Prior to joining Vanta, Matt was the U.S. Director for the Cyber, Risk & Advisory practice at BSI where he led an information security consultancy providing risk management and readiness consulting for common industry frameworks such as ISO 27001, SOC2, HIPAA, and PCI. At Vanta, Matt works closely with audit partners, advises customers on security and compliance, and provides input to the product team.
Learn more about SOC 2 compliance
PCI Compliance Selection Guide
Determine Your PCI Compliance Level
If your organization processes, stores, or transmits cardholder data, you must comply with the Payment Card Industry Data Security Standard (PCI DSS), a global mandate created by major credit card companies. Compliance is mandatory for any business that accepts credit card payments.
When establishing strategies for implementing and maintaining PCI compliance, your organization needs to understand what constitutes a Merchant or Service Provider, and whether a Self Assessment Questionnaire (SAQ) or Report on Compliance (ROC) is most applicable to your business.
Answer a few short questions and we’ll help identify your compliance level.
Does your business offer services to customers who are interested in your level of PCI compliance?
Identify your PCI SAQ or ROC level
The PCI Security Standards Council has established the below criteria for Merchant and Service Provider validation. Use these descriptions to help determine the SAQ or ROC that best applies to your organization.
Good news! Vanta supports all of the following compliance levels:
A SAQ A is required for Merchants that do not require the physical presence of a credit card (like an eCommerce, mail, or telephone purchase). This means that the Merchant’s business has fully outsourced all cardholder data processing to PCI DSS compliant third party Service Providers, with no electronic storage, processing, or transmission of any cardholder data on the Merchant’s system or premises.
Get PCI DSS certified
A SAQ A-EP is similar to a SAQ A, but is a requirement for Merchants that don't receive cardholder data, but control how cardholder data is redirected to a PCI DSS validated third-party payment processor.
Learn more about eCommerce PCI
A SAQ D includes over 200 requirements and covers the entirety of PCI DSS compliance. If you are a Service Provider, a SAQ D is the only SAQ you’re eligible to complete.
Use our PCI checklist
A Report on Compliance (ROC) is an annual assessment that determines your organization’s ability to protect cardholder data. If you’re a Merchant that processes over six million transactions annually or a Service Provider that processes more than 300,000 transactions annually, your organization is responsible for both a ROC and an Attestation of Compliance (AOC).
Automate your ROC and AOC