- Market
- Saudi Arabia
- Written for
- CISO, CIO, Procurement
- Decision
- Reach CCC or CCC+ readiness before a contractual deadline
- Languages
- EN · AR
Credentials for Aramco compliance
NCA registration
Registered cybersecurity service provider

Aramco CCC
CCC certified

ISO/IEC 27001
ISO/IEC 27001 certified
The programme
From the environment you have to an audit worth booking
Six stages. The first five are ours and are where the elapsed time is; the sixth is the formal process, and the plan is built so it starts on a date that holds.
01
Current environment
What is actually running, which systems perform the contracted work, and which connections cross the boundary you are about to declare.
- Inventory
- Network
02
Readiness assessment
Each requirement measured against the scoped estate, sorted by what it takes to close rather than by control number.
- Gap register
03
Gap remediation
The engineering itself — segmentation, access control, logging, hardening — done by us, with the procedure recorded as it is implemented.
- IAM
- SIEM
- Firewalls
04
Evidence preparation
Artefacts generated by the control that runs, covering a period the audit can measure. This is the stage money cannot shorten.
- Evidence pack
05
Assessment readiness
The pack read against the requirement before anyone else reads it, with the weak answers found by us rather than in the room.
- Dry run
06
Authorised assessment
Conducted through an audit firm Saudi Aramco authorises for that purpose, selected from the published list. We stay available throughout it.
- Audit firm
The stage that decides the date is evidence preparation, because a control implemented in the final month has no operating history for the assessment to measure.
Who this applies to
The requirement usually arrives with a commercial deadline attached
Most organisations do not go looking for this. They are told — by Aramco directly, or by a prime contractor passing the obligation down — that they need a Cybersecurity Compliance Certificate, by a date, and that continued trading depends on it. The work then has to fit inside a commercial window rather than an IT roadmap.
The first thing worth understanding is that this is not a single requirement applied uniformly. Aramco classifies third parties, and the classification determines both which controls are in scope and how the assessment is carried out. A vendor supplying office consumables and a vendor with a network connection into Aramco systems are not being asked for the same thing, and scoping the work before the classification is confirmed is how organisations end up paying for the wrong assessment.
The second is that most of the gap is documentary rather than technical. Organisations that have been operating safely for years frequently already do much of what the controls require — they just cannot prove it in the format an auditor accepts. Logging exists but is not retained long enough. Changes are approved but in email. Access is controlled but there is no review record. Closing that kind of gap is faster than building controls from nothing, but it is not free, and it is the part that gets underestimated.
Classification
CCC and CCC+ are not the same engagement
Your classification is determined by Aramco, not by you and not by us. Confirm it with Aramco before scoping anything — this table is here so you know what each answer implies.
| Option | How it is validated | Who it applies to | What it means for you | Best for |
|---|---|---|---|---|
| CCC | Self-assessment against the scoped controls, validated remotely by an Authorized Audit Firm | Third parties that do not fall under the Network Connectivity or Critical Data Processor classifications | The quality of your own evidence package largely determines how the validation goes | Suppliers without a network connection into Aramco systems or custody of critical data |
| CCC+ | On-site assessment conducted by an Authorized Audit Firm | Third parties classified as Network Connectivity or Critical Data Processor | Controls must hold up to inspection in place, so remediation has to be real rather than documented intent | Suppliers with connectivity into Aramco systems, or handling data Aramco classifies as critical |
The work
What readiness actually involves, and what each stage produces
Scope confirmation
Establish which systems, sites and data are in scope for your classification, and — as important — which are not. Over-scoping is the most common way this work becomes more expensive than it needs to be.
What you hold afterwards: A written scope boundary you can show the auditor
Gap assessment
Assess the in-scope environment control by control against the published scoped controls, separating what is genuinely missing from what exists but cannot be evidenced.
What you hold afterwards: Control-by-control status with effort against each gap
Technical remediation
Close the engineering gaps: segmentation, access control and review, logging and retention, patch and vulnerability process, backup and tested recovery, secure configuration.
What you hold afterwards: Working controls, plus the change record showing how they got there
Documentation and evidence
Assemble the policies, procedures, records and screenshots the assessment expects, in the structure an auditor reads rather than as a folder of files.
What you hold afterwards: A compliance package ready for submission
Audit support
Answer the auditor's technical questions during validation, and remediate anything raised. We support your submission; we are not party to the audit decision.
What you hold afterwards: Findings closed with evidence, before they become a re-submission
Maintaining it
The certificate has a fixed validity period, so the evidence set needs an owner and a maintenance rhythm. Without one, the next cycle starts from scratch after the original team has moved on.
What you hold afterwards: A named owner and a maintained evidence set
Our role
From gap assessment to assessment-ready evidence
Five workstreams, in the order they run. Each one ends in something the assessment will ask to see.
- 01
Scope determination
Which of your systems perform the contracted work, which connections cross the boundary, and the reasoning for what sits outside it — written to be read by the assessor rather than by us.
- 02
Gap identification
Each applicable control measured against what exists in the scoped estate, sorted into what is missing, what exists undocumented and what has no owner. Those three cost very different amounts to close.
- 03
Technical remediation
Segmentation, access control, remote access hardening, logging and vulnerability management — sequenced so the controls other controls depend on land first.
- 04
Control implementation and documentation
Policies and procedures written against what the organisation will actually do, with an owner named against each. A policy describing a process nobody runs is a worse finding than an absent one.
- 05
Evidence preparation
Each control producing its own dated record as a by-product of running, so the month before the assessment is collation rather than reconstruction. This is the workstream that decides how the assessment goes.
Formal assessment then follows the applicable Aramco-authorised process, and we stay available through it to answer questions on the work and remediate what the assessor raises.
Saudi Aramco publishes the requirement and the list of firms authorised to conduct the assessment. Take scope and applicability questions to your contract contact, and select the assessor from the published list. Source
Common gaps
Where supplier assessments usually come unstuck
These are the findings that recur across readiness engagements. None of them is exotic, and all of them take longer to fix under deadline than in advance.
- 01
Log retention shorter than the requirement
Logging is usually switched on somewhere. The gap is retention: storage was sized for troubleshooting, not for an audit window, so the records that would demonstrate a control was operating have already rolled off. This is cheap to fix and impossible to fix retroactively, which is why it should be the first thing checked.
- 02
No access review record
Access is controlled in practice — the wrong people genuinely cannot get in — but nobody has produced a periodic review showing that someone checked. The control exists; the evidence of it operating does not. Establishing a review cadence and recording the first one is straightforward, but it takes a cycle to have anything to show.
- 03
Flat networks between office and operational systems
Common in contractors whose estate grew with the business. Segmentation is the finding most likely to require real project work rather than configuration, and the one where doing it badly can affect operations — so it needs planning against the maintenance calendar rather than a weekend.
Common questions
What buyers ask
What is the difference between CCC and CCC+?+
Under Aramco's SACS-002 standard, CCC requires the third party to complete a self-assessment against the scoped controls, which an Authorized Audit Firm then validates remotely. CCC+ requires an Authorized Audit Firm to conduct an on-site assessment, and applies to third parties classified as Network Connectivity or Critical Data Processor. Aramco determines the classification — confirm yours with Aramco rather than assuming it from your contract type.
Is Techbanq an Aramco-approved or certified cybersecurity firm?+
No. Aramco authorises specific audit firms to perform the assessment behind the certificate and publishes that list; Techbanq is not on it. What we provide is readiness support — interpreting the standard, gap assessment, remediating technical findings and assembling the evidence an Authorized Audit Firm will ask for. Verify any supplier's claim on this against Aramco's published list rather than taking it from a website.
How long does readiness work take?+
It depends almost entirely on the starting position and the size of the in-scope environment, so we do not quote a duration before the gap assessment. As a shape: the assessment itself is typically a matter of weeks. Remediation runs from a few weeks where the gaps are documentary to several months where segmentation or logging work is needed. Log retention is the one item worth fixing immediately, because you cannot create history you did not keep.
How long is the certificate valid?+
Aramco's programme material states the CCC is valid for two years from issuance, provided the third party's classification has not changed in that period, and must then be renewed. In practice the useful consequence is that someone has to own the evidence set between cycles — otherwise renewal becomes a second full project rather than an update.
We are a subcontractor, not a direct Aramco supplier. Does this apply to us?+
It depends on what your client has contracted with you, not on your distance from Aramco. Prime contractors routinely pass equivalent cybersecurity obligations down their supply chain, and the flow-down clauses are where you will find what you actually owe. Read those first — we can help interpret them against what your environment does today, and the answer is sometimes that a lighter scope applies than you feared.
In this cluster
Next step
Request a gap assessment
A gap assessment scoped to your classification, returning a control-by-control status and a remediation plan with effort against each item. We give an estimate after that assessment, not before it.
Request a gap assessment
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
