- Market
- Saudi Arabia
- Written for
- CISO, CTO, Procurement
- 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 patterns
The four gap shapes that dominate certificate readiness work
Different suppliers, different estates, the same shapes. Each pattern below survives ordinary security programmes because its cause is organisational, not technical.
- 01
The inventory that stops at the obvious
The formal asset list covers the ERP and the file server, and omits the estimation workstation, the shared mailbox and the engineer's laptop that actually hold Aramco drawings and pricing. The audit scopes by where the data is, not by where the register says it is — so the omitted systems become findings.
- 02
Access shared across customers
One team, one set of accounts, every customer's work — so the folder of Aramco material is readable by staff who never touch that contract, and by tools connected for other clients. What was efficient as a small firm reads, at audit, as an inability to say who can reach the data.
- 03
Controls that run without leaving records
Backups happen, access is revoked when people leave, patches go on — and none of it is written anywhere an auditor can read. The control exists; the evidence does not. This is the most galling pattern, because the fix is administrative, and the finding is identical to not doing the work at all.
- 04
Scope drawn by guesswork
Without a deliberate boundary around the systems that handle Aramco data, the practical scope defaults to everything — or to an optimistic subset the audit will not accept. Either way the supplier does the wrong amount of work: hardening systems that never needed it, or defending a perimeter the data does not respect.
The causes
Why these gaps survive suppliers with capable security teams
None of the four patterns indicates a weak team. They indicate a change of vantage point: a security programme protects the estate as the organisation sees it, while the certificate assessment reads the estate as Aramco's data travels through it. A workstation that matters little to your own risk model matters entirely once it holds a customer's drawings, and no internal prioritisation would have surfaced it — the question was never asked from that seat.
The evidence pattern has the same structure. Operational teams optimise for the work being done, not for the work being provable; records feel like overhead until the day a third party is entitled to ask for them. And the access pattern is simply a firm's history made visible: the account structure grew with the company, and nobody had a reason to partition it until a customer's standard required saying, precisely, who can reach what. Reading the gaps as patterns rather than as failures matters practically — it tells you the causes are shared, so the fixes can be shared too, and it takes the defensiveness out of the room where the remediation gets planned.
The order
A remediation sequence that closes certificate gaps without rework
The patterns are coupled: scope depends on inventory, access design depends on scope, and evidence depends on the controls being final. Work the sequence and each fix is done once.
Trace the data before trusting the register
Follow Aramco-related data through the estate — from receipt, through processing and sharing, to storage and backup — and let the trace correct the inventory. Everything after this step is scoped by what the trace found, which is why it comes first. An inventory that matches where the data actually is.
Draw the boundary on purpose
Decide which systems will handle Aramco data and contain it there — consolidating scattered copies where that shrinks the scope honestly. A deliberate boundary is defensible to an auditor; a default one is not. A defensible scope, smaller than the estate and larger than a guess.
Partition the access inside the boundary
With the scope fixed, the sharing pattern is closed: named accounts, access granted by contract role rather than by team membership, and the connected tools of other customers moved outside the boundary. An answer to "who can reach the data" that survives the audit.
Wire the records into the routines
Last, because evidence should record the final state: the controls that already run get their trail — tickets, reviews, exports — generated by the routine itself, so the proof accumulates from here to the audit date and beyond it. Evidence produced by operating, not assembled the week before.
Our role
What gap work we carry, and what belongs to the authorised audit firm
- 01
The trace and the diagnosis
We follow the data, correct the inventory and name which of the patterns your estate carries — against Aramco's published third-party material, not a generic checklist.
- 02
The sequenced closure
Scope, access and evidence work is delivered in the order that avoids rework, with your teams, so each fix is built once and owned in-house afterwards.
- 03
Readiness for the real assessment
We prepare the estate and its evidence to be read by the audit firm you select from Aramco's published list — the assessment itself, and the certificate, are theirs and Aramco's alone.
The Cybersecurity Compliance Certificate is issued through audit firms Aramco authorises, on their assessment and Aramco's process — our work ends where theirs begins, with an estate whose gaps have been closed in an order that will read coherently to them.
Aramco publishes the certificate programme, its third-party manual and the list of authorised audit firms on its own supplier pages. Choose your auditor from that list, and take scope questions to Aramco's published material and your auditor. Source
Common questions
What buyers ask
Our controls genuinely run but we cannot show records for them. Does the audit treat that as a gap?+
Expect it to, because an assessment can only weigh what can be demonstrated — an auditor attesting to a control on the strength of your word would be defeating the purpose of the exercise. The practical reading is more hopeful than it sounds: a control that runs but leaves no trail is usually weeks from evidenced, not months, since the work is wiring records into an existing routine rather than building the routine. Start early enough and the trail has real history by the audit date, which reads far better than records that all begin the month before.
Our asset register passed internal audit. How did it still miss systems handling Aramco data?+
Because the two audits ask different questions. An internal review checks that the register is well-maintained against its own definition of an asset — typically infrastructure and managed endpoints. The certificate assessment asks where one customer's data actually is, and data ignores register definitions: it sits in a shared mailbox, an estimator's spreadsheet, a subcontractor upload folder, a personal device used on one urgent evening. The only method that finds those places is tracing the data's real journey through the firm, then correcting the register with what the trace found. That is why data tracing, not register review, is the first step of readiness.
The audit is not booked yet. Which certificate gaps should we close first?+
Work the dependency order, not the anxiety order. Trace the data and fix the inventory first, because every later decision inherits its accuracy; then draw the scope boundary deliberately, because access design and control work are both sized by it; then partition access inside the boundary; and wire evidence into the routines last, so the records describe the final state rather than a configuration you are about to change. Suppliers who invert this — usually by starting with evidence collection because it feels like progress — document an estate they then modify, and pay for the same work twice. The unbooked audit is an advantage: it lets you run the cheap order.
In this cluster
Find your gap patterns
A supplier who knows which gap patterns its estate carries, and holds a remediation order that closes them once, in the sequence the audit will read them.
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
