A customer asked for your SOC 2 report
SOC 2 is the one framework on this site that no Saudi regulator requires. It is asked for by buyers — and if you already carry the NCA ECC or the SAMA CSF, you have built most of it without calling it that.
This page reflects how we see SOC 2 applied in practice. It is not an official reference. The authoritative source is TSP Section 100 as published by the AICPA, which may be revised — confirm what applies to your organisation against it and with the CPA firm performing your examination.
What is SOC 2?
From the compliance programmes we build and run in Saudi Arabia: SOC 2 is an attestation report produced by a licensed CPA firm, examining a service organisation's controls against the AICPA's Trust Services Criteria. It is voluntary and buyer-driven rather than regulatory, and it results in a report you share under NDA — not a certificate you display.
The distinction from every other framework on this site matters. The NCA ECC, the SAMA CSF, the CST CRF and the PDPL are imposed by Saudi authorities, and the consequence of ignoring them is regulatory. SOC 2 is imposed by your customers, and the consequence of not having it is a stalled deal.
That changes how you should scope it. A regulator tells you what applies. With SOC 2, you decide the scope — which criteria, which systems, which period — and your buyers decide whether that scope satisfies them.
The five Trust Services Criteria
Defined in AICPA TSP Section 100 — the 2017 criteria, with revised points of focus issued in 2022. Only the first is mandatory.
Protection of systems and data against unauthorised access, use, and disclosure. This category is the common criteria — governance, risk assessment, access control, operations, change management, and monitoring — and it is reused by the other four rather than repeated.
Whether the system is available for operation and use as committed. Relevant where you have made uptime commitments to customers, and usually the first category added after Security.
Protection of information designated as confidential. Frequently requested where you hold commercially sensitive customer material rather than personal data.
Whether processing is complete, valid, accurate, timely and authorised. Relevant where your service performs calculations or transactions on the customer's behalf, and often unnecessary otherwise.
Collection, use, retention, disclosure and disposal of personal information. Distinct from Confidentiality — Privacy is specific to personal data, and its criteria sit closer to what the PDPL asks of you than most teams expect.
The most useful thing to know when scoping: because Security is the common criteria, adding a second category is not double the work. The category-specific criteria layered on top are a short tail — you do not re-test risk assessment or change management for each one.
Type 1 and Type 2
The difference is time, and it is the single most common misunderstanding we see when a team is asked for "a SOC 2".
This is where evidence discipline decides the outcome. A Type 2 examination samples across the observation period, so evidence assembled the week before fieldwork does not help — the auditor is looking for artefacts produced while the control was running. Teams that treat evidence as an annual exercise fail Type 2 having passed Type 1 comfortably.
| Type 1 | Type 2 | |
|---|---|---|
| What it examines | Whether controls are suitably designed | Whether controls are suitably designed and operated effectively |
| Time covered | A single point in time | A period, typically several months to a year |
| What it proves | You built the controls | You ran them, and can evidence that you did |
| Evidence required | Design documentation as at the date | Operating evidence sampled across the whole period |
| What buyers usually want | Accepted as a first step, often with a commitment to follow | The one enterprise buyers actually ask for |
Why a Saudi organisation ends up needing SOC 2
Nobody in the Kingdom requires it. It arrives through the commercial door instead.
A Saudi SaaS or services company selling into the US or Europe will be asked for SOC 2 rather than the ECC, because the buyer's procurement team recognises SOC 2 and has never heard of the ECC.
A Saudi subsidiary of a multinational is often pulled into a group SOC 2 scope, which means demonstrating the same controls locally that the group demonstrates elsewhere.
A Saudi bank assessing you under SAMA CSF domain 3.4, or a government entity under the ECC's third-party component, may accept a SOC 2 report as evidence — which turns one report into an answer for several assessments.
A current Type 2 report answers most of a security questionnaire before it is asked. That is the commercial argument, and it is usually the real reason a company starts.
Growth-stage diligence in software increasingly treats SOC 2 as a baseline signal of operational maturity, independent of any customer asking.
SOC 2 sits alongside the ECC, the SAMA CSF, the CST CRF and the PDPL. It does not discharge any of them, and a regulator will not accept it in place of the framework that actually applies to you.
Running SOC 2 in Govrly
Six things that change once SOC 2 sits on the same control library as your Saudi frameworks instead of in a separate readiness project.
Access control, change management, risk assessment and monitoring already implemented for the ECC or the SAMA CSF map onto the Security common criteria from the same record. For most Saudi organisations this is the majority of a Security-only scope, already done.
Security is set as mandatory and the other four are included or excluded with the reasoning attached — so the scope decision is a record you can defend to a buyer rather than something remembered from a meeting.
Evidence is requested from the owner who produces it, reviewed before it counts, and carries a validity period — which is what makes a Type 2 observation window survivable rather than a scramble.
Each applicable criterion carries a named owner and a target date. Where no owner exists, that surfaces during scoping rather than during fieldwork.
An exception raised during readiness or examination carries root cause, owner and a verification step — so it does not reappear in the next period's report.
If you add the Privacy category, the processing records, lawful bases and retention decisions supporting it are the same records carrying your PDPL obligations.
SOC 2 and ISO 27001
The two most common voluntary frameworks, and the pair teams most often try to choose between when they should be mapping both.
In our experience the choice is usually settled by geography rather than merit: if your buyers are North American, they will ask for SOC 2; elsewhere, and particularly in the Gulf, ISO 27001 carries further. Organisations selling into both stop choosing and map both, which is far cheaper than it sounds once the control library is shared.
| SOC 2 | ISO 27001:2022 | |
|---|---|---|
| Issued by | AICPA | ISO and IEC |
| What you receive | An attestation report, shared under NDA | A certificate, publicly displayable |
| Who performs it | A licensed CPA firm | An accredited certification body |
| Structure | Criteria, with controls you design yourself | A management system, plus 93 Annex A controls |
| Scope | You define it; buyers judge it | Defined in the Statement of Applicability |
| Recognised by | North American buyers, strongly | Recognised internationally, including the Gulf |
| In Govrly | Both, on one control library — an access control satisfies a common criterion and an Annex A control from the same record | Both, on one control library — an access control satisfies a common criterion and an Annex A control from the same record |
A practical path to a SOC 2 report
The sequence matters more here than in a regulatory programme, because you are choosing the scope rather than being given it.
- 01/08Find out what your buyer actually needs
Type 1 or Type 2, and which categories. Ask before scoping. Teams routinely build a five-category Type 2 when the customer would have accepted Security-only, and the difference is months.
- 02/08Define the system in scope
Which product, which environments, which supporting infrastructure. A scope that is broader than the thing being bought costs time and buys nothing.
- 03/08Map the common criteria against what you already run
If you carry the ECC or the SAMA CSF, start here and expect to find most of Security already implemented. This step is where a multi-framework programme earns its keep.
- 04/08Close the design gaps
Write what is missing, assign owners, and record the decisions. This is readiness, and it is the part a consultant is genuinely useful for.
- 05/08Choose the observation window before it starts
A Type 2 covers a period, and the period begins when you say it does. Starting it before evidence collection is reliable is the most common self-inflicted delay we see.
- 06/08Run the controls, and let evidence accumulate
Evidence produced as operations run, not assembled beforehand. If your team can only produce the artefact when asked, the control is not operating in a way a Type 2 will accept.
- 07/08Select the CPA firm early
They will have views on scope and readiness, and hearing those before the window opens is cheaper than hearing them during fieldwork.
- 08/08Plan for the next period from the first one
SOC 2 is annual. A report is a photograph of a period, and the second period starts the day the first ends — which is why programmes that treat it as a project rather than a rhythm find the second year as hard as the first.
Your SOC 2 scope sits on the same control library as your NCA ECC or SAMA CSF programme, so a control implemented once satisfies a common criterion and a Saudi requirement from the same record — and the evidence collected across the observation window is the evidence your regulator sees too.
SOC 2 — FAQs
An attestation report produced by a licensed CPA firm, examining a service organisation's controls against the AICPA's Trust Services Criteria. It is voluntary and buyer-driven rather than regulatory, and it results in a report shared under NDA rather than a certificate you display.
No. No Saudi regulator requires SOC 2. It arrives commercially — from customers, particularly those outside the Kingdom, from a parent company's group scope, or from investor diligence. It also does not discharge your NCA ECC, SAMA CSF, CST CRF or PDPL obligations, which apply regardless.
Security, Availability, Processing Integrity, Confidentiality, and Privacy, defined in AICPA TSP Section 100 — the 2017 criteria with revised points of focus issued in 2022. Security is the only mandatory category; it forms the common criteria that the other four build on rather than repeat.
Type 1 examines whether controls are suitably designed at a single point in time. Type 2 examines whether they were suitably designed and operated effectively across a period, typically several months to a year. Enterprise buyers generally ask for Type 2, because it evidences that controls actually ran rather than that they exist on paper.
No, and they are not substitutes. SOC 2 gives you a report shared under NDA from a CPA firm; ISO 27001 gives you a publicly displayable certificate from an accredited certification body. The choice is usually settled by where your buyers are, and organisations selling into both markets map both onto one control library rather than choosing.
More than most teams expect. The Security common criteria cover governance, risk assessment, access control, change management, operations and monitoring — all of which are implemented for the ECC. The work that remains is usually mapping, documenting the scope decision, and establishing evidence collection that survives a Type 2 observation window.
No. SOC 2 is an attestation, not a certification, and there is no certificate to hold. The accurate phrasing is that you have completed a SOC 2 Type 1 or Type 2 examination for a stated period and scope. Security reviewers notice the difference, and using the wrong term costs credibility with exactly the audience the report is meant to convince.
It depends far more on the state of your existing controls and evidence than on the framework. Readiness — closing design gaps and establishing reliable evidence collection — is the substantive work. After that, a Type 2 additionally requires the observation period itself to elapse, which no amount of preparation shortens.
Ask your buyer before deciding. Security is mandatory. Availability follows where you have made uptime commitments, Confidentiality where you hold commercially sensitive material, Processing Integrity where your service performs calculations or transactions on a customer's behalf, and Privacy where you handle personal data. Adding a category is not double the work, because the common criteria are shared.
In practice yes. A report covers a stated period, and buyers treat a report whose period has lapsed as stale. The second period begins where the first ends, which is why programmes that run SOC 2 as an annual project rather than a continuous rhythm find each year as difficult as the last.
You have probably built more of this than you think
See what your existing NCA ECC or SAMA CSF controls already cover against the Trust Services Criteria.
