
SOC 2 or ISO 27001: which one your client wants, and what to send if you do not have it
A client asks for your SOC 2 report and you hold an ISO 27001 certificate. Or the other way round. They are two kinds of evidence for almost the same question: is my information safe with you? This piece explains what SOC 2 is, how it differs from ISO 27001, and how to answer the request without starting a programme you do not need.
ISO 27001 is a certificate on a management system, issued by an accredited certification body. SOC 2 is an auditor’s report on your controls, with an opinion in it.
The question behind a SOC 2 request is almost always the same as behind an ISO request. Ask what the client needs it for before you start a second programme.
A SOC 2 Type 2 looks back over a period, a Type 1 at a single point in time. If you need one, start recording evidence early.
What the client is really asking
A request for “your SOC 2” usually comes out of procurement: a client assesses its suppliers and has a form with a box that says those words. Often it is a client with a US parent or a US software platform, because there SOC 2 is the most common kind of evidence. In the UK and Europe, ISO 27001 is.
The question behind it is nearly always the same: does this supplier have its information security in order, and has an independent party looked at it? A SOC 2 report and an ISO 27001 certificate both answer that, in different ways.
So ask three questions back before you commit to anything:
- Does it have to be SOC 2, or will the client accept equivalent evidence? Many assessors list “SOC 2 or ISO 27001” and only ask for the first because it sits at the top.
- Which service is in question? A report or certificate covers a defined scope. What the client buys has to fall inside it.
- What will they do with it? An attachment in their own file is a different ask from a contract condition with a deadline.
SOC 2 in brief
SOC 2 is a reporting framework from the AICPA, the American professional body for accountants. A CPA firm examines a service organisation’s controls and writes a report with the auditor’s opinion in it. There is no certificate and no pass or fail: there is a report, and the reader draws their own conclusion.
The framework tests against five Trust Services Criteria: security (always required), availability, processing integrity, confidentiality and privacy. The service organisation chooses which of the other four to include, and that is the first thing to read in anyone else’s SOC 2 report.
- Type 1 assesses whether the controls are suitably designed at a point in time.
- Type 2 assesses whether they actually operated over a period, usually several months to a year. That is what most clients mean.
The report itself is restricted and shared under a non-disclosure agreement. There is also a SOC 3, a short public summary, but procurement teams rarely accept it in place of the full report.
ISO 27001 in brief, and where the difference lies
ISO/IEC 27001 is an international standard for an information security management system. An accredited certification body audits whether your system meets the standard and issues a certificate. In the UK, UKAS accredits those bodies, which is why clients look for the UKAS mark. A certificate runs for three years, with a surveillance audit each year in between.
How you implement the controls in the standard is covered in our ISO 27001 checklist. Here the point is the difference a client notices:
- Who issues it. ISO: a certification body. SOC 2: a CPA firm.
- What you get. ISO: a one-page certificate with a scope, which you may show publicly and a client can verify with the body. SOC 2: a report of dozens of pages listing the controls, the tests and any exceptions, only for those who sign an NDA.
- What it looks at. ISO tests whether your system works: risk assessment, policy, improvement. SOC 2 Type 2 tests whether specific controls operated over a period, by sampling.
- Where it is usual. ISO worldwide and especially in Europe, SOC 2 mainly in North America and among software companies selling there.
SOC 2 vs ISO 27001: which one you need
The deciding question is not which is stricter, because that varies by scope and auditor. It is who your clients are and what they accept.
- Your clients are in the UK or Europe: ISO 27001 is the evidence they recognise, and in UK public sector work Cyber Essentials is often asked for alongside it.
- You sell software or a cloud service to US clients: SOC 2 Type 2 is often a condition for getting onto the shortlist.
- Both: start with whichever carries the most revenue. The controls overlap to a large extent, so the second programme is mainly new evidence about work that already exists, not new work.
What either programme costs depends on the same things: how wide the scope is, how many sites and systems fall within it, how mature your record keeping already is and, for SOC 2, how many criteria you include and how long the Type 2 period runs.
What to send when you do not have what they asked for
If you hold ISO 27001 and a client asks for SOC 2, do not just write “no” in the box. Send what you do have and make it easy to accept:
- The certificate with its scope, and the name of the certification body so they can verify it.
- An extract of your Statement of Applicability for the controls their questions touch, under NDA.
- A short mapping table from their SOC 2 criteria to your ISO controls. It is an afternoon’s work and saves them an interpretation.
- Evidence from practice, such as how access is removed when someone leaves, how long logs are kept and when the last backup restore test was.
And never: claim a SOC 2 you do not have, or write “in preparation” when no auditor has been engaged. An assessor will come back to that later, with a date.
What an auditor will want to see from your IT
In both programmes much of the evidence comes from the IT environment, and that is where it tends to fall down: not on the control but on the record of it. A Type 2 is strictest here, because the auditor samples across the whole period.
- Access: who got which rights when, who approved it, and that rights were removed on the day someone left.
- Changes: a ticket per change to systems, showing who made it and who approved it.
- Logging and monitoring: what is logged, how long it is kept, and what happened with an alert.
- Backup and recovery: not that a backup exists, but that a restore was tested and the test recorded.
- Suppliers: which third parties touch your data, and how you assessed their evidence.
If a supplier manages your IT, it falls under that last point itself. Ask for its own certificate or report, and check that the service it provides you sits inside the scope.
Where our work stops
What we do. ITproposal is ISO/IEC 27001 certified, as well as ISO 9001 and ISO 14001. As your supplier we send that certificate with its scope on request and answer your supplier questionnaire. If we manage your IT, we deliver the technical controls and the evidence beneath them: access reviews, change tickets, logging and restore tests, recorded so an auditor can use them.
What we do not do. We do not hold a SOC 2 report and do not claim to. We are not a CPA firm or a certification body: we do not issue SOC 2 reports, we do not certify anyone, we do not judge whether you meet a standard and we do not tell you whether a client should accept your evidence. That judgement belongs to the auditor, the certification body and your client.
Questions we get about this
The five that come up most often.
What is SOC 2?
SOC 2 is a reporting framework from the AICPA, the American professional body for accountants. A CPA firm examines a service organisation’s controls for security and, optionally, availability, processing integrity, confidentiality and privacy, and writes a report on them. There is no certificate; the report is shared with clients under NDA.
What is the difference between SOC 2 Type 1 and Type 2?
A Type 1 assesses whether controls are suitably designed at a single point in time. A Type 2 assesses whether they actually operated over a period, usually several months to a year, by sampling. Most clients ask for a Type 2.
Is SOC 2 the same as ISO 27001?
No. ISO 27001 is a certificate on an information security management system, issued by an accredited certification body and publicly verifiable. SOC 2 is a restricted report by an auditor on specific controls, with an opinion in it. ISO is usual in the UK and Europe, SOC 2 mainly in North America.
Will ISO 27001 do if a client asks for SOC 2?
Often, but the client decides. Ask whether they accept equivalent evidence, then send your certificate with its scope, an extract of your Statement of Applicability and a short mapping from their criteria to your controls. If they will not accept it, a SOC 2 programme is the only route.
Do you have a SOC 2 report, and can you give us one?
No. ITproposal is ISO/IEC 27001 certified and does not hold a SOC 2 report. We are not an auditor or a certification body, so we do not issue SOC 2 reports or certificates and do not judge whether you meet a standard. What we do, as the manager of your IT, is deliver the technical controls and the evidence an auditor asks for.
Further reading
What this evidence connects to.
A client wants evidence? We deliver the technical part
Send us the questions you have received. We will tell you which part has to come from your IT and what needs recording for it; the judgement we leave to your auditor.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.