Credentials for Aramco compliance
NCA registration
Registered cybersecurity service provider

Aramco CCC
CCC certified

ISO/IEC 27001
ISO/IEC 27001 certified
The checklist
Twelve checks, and what each answer means
Answer honestly rather than optimistically — the audit will. Three of these set the timeline more than the other nine combined, and they are marked.
1 · Can you name the systems in scope? ▲
A written list with the connections crossing the boundary marked.
A fail means: The scope work is the first project. Nothing else can be estimated until it exists.
2 · Are those systems on their own network? ▲
Separate segment with rules you can produce.
A fail means: Segmentation is the longest item in the plan. This single answer moves the date by months.
3 · Is multi-factor on every remote route? ▲
Including vendor and support access, not only staff VPN.
A fail means: Usually weeks rather than months, and it is the cheapest large improvement available.
4 · Who can reach the customer's data?
A list you can produce from the systems, not from memory.
A fail means: An access enumeration is needed, and it usually returns more people than expected.
5 · Is that access reviewed, with a record?
A dated review with a named reviewer, at a stated frequency.
A fail means: The control probably exists and is unevidenced. Weeks, and it is writing rather than engineering.
6 · Do you know what is unpatched today?
A current scan you can show, with remediation dates against it.
A fail means: Vulnerability management has to be turned on before anything else is measured.
7 · Are logs kept, and for how long?
A stated retention period and an export you can produce.
A fail means: Configuration work, and the retention clock starts when it is done.
8 · Is there an incident procedure that was used?
A register with entries, including minor ones, and one exercise.
A fail means: An empty register reads as absent detection. A tabletop exercise costs an afternoon.
9 · Who else is inside your boundary?
Subcontractors named, with security terms in their contracts.
A fail means: Contract work with third parties, which runs on their timetable rather than yours.
10 · Are your policies approved and current?
Approval dates, an owner, and a review that happened.
A fail means: Writing, and it is quick — provided the policy describes what you actually do.
11 · Can you produce a network diagram?
Current, and matching what is actually deployed.
A fail means: The auditor will ask on day one. Producing it also tests answer two.
12 · Has anyone read the contract clause?
The clause and the referenced standard, in writing, from your contract contact.
A fail means: You may be preparing for the wrong requirement. Free to fix, expensive not to.
Reading your answers
Three answers set the date; the rest set the effort
Checks one, two and three are marked because they behave differently from the others. A supplier who passes all three is looking at a project measured in months of documentation and configuration. A supplier who fails the second is looking at separating a working estate without interrupting delivery, which is slow for reasons that have nothing to do with the difficulty of the work — it has to be staged against a business that is still operating.
The rest sort into the same three groups every assessment produces: controls that exist and are unevidenced, controls that exist and have no owner, and controls that genuinely do not exist. The first two close in weeks and need writing rather than spend. The third is where money goes, and it is usually the smallest of the three.
What to do next
Four moves that cost nothing
1 · Get the clause in writing
From your Aramco contract contact: the clause and the standard it references. One email. Certainty about which requirement you are preparing for.
2 · Draw the boundary on paper
The systems doing the work, and every connection leaving them. Imperfect is fine; absent is not. The input everything else is estimated from.
3 · Start the evidence clock
Turn on logging, run one access review and record it, hold one tabletop exercise. All three produce dated records from today. A period of operation the audit can measure, starting now rather than after remediation.
4 · Talk to the customer about the date
With the checklist attached. A supplier presenting a position is in a different conversation from one that has gone quiet. A conversation about a plan rather than about a delay.
Our role
What we do with the items you cannot tick
CCC readiness is a body of engineering, documentation and evidence work that has to be finished before an audit is worth booking. That work is ours.
- 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
Readiness review
Each requirement measured against what exists in the scoped estate, sorted by what it will take to close rather than by control number.
- 03
Remediation and documentation
The engineering work itself — segmentation, access control, logging, hardening — with the procedure and the ownership recorded as it is implemented rather than written up afterwards.
- 04
The realistic date
Where the achievable date falls later than the contract date we say so early, while there is still time to have that conversation with your customer rather than after it has become a delivery problem.
The audit then follows through an audit firm Saudi Aramco authorises for that purpose, selected from the published list, and we stay available through it to answer questions about the work we did.
Saudi Aramco publishes the requirement and maintains the list of firms authorised to conduct the audit. Take scope and applicability questions to your Aramco contract contact, and select the auditor from the published list rather than from a supplier's recommendation. Source
Common questions
What buyers ask
If we pass all twelve, are we ready?+
You are in good shape and you are not ready, because the audit measures a period of operation rather than a state on one day. Passing all twelve means the controls exist; what remains is the record showing they operated across the period the auditor will ask about. That is why the third step above is starting the evidence clock rather than booking the audit.
We failed most of these. Is it hopeless?+
No, and the shape of the failure matters more than the count. Failing the documentation checks is weeks of writing. Failing check two is months, and that is the honest number to take to the customer. What makes this hard is not the work; it is discovering the timeline late, which is exactly what running the checklist early prevents.
Should we hire someone before or after running this?+
After. A supplier who arrives with the twelve answers gets a scoped proposal; one who arrives without them gets a discovery engagement first, which is the same work billed. The checklist is deliberately answerable without us, and a supplier who will not tell you that is worth noticing.
In this cluster
Send us your checklist answers
The completed checklist, so a scoping conversation starts from facts rather than from a questionnaire we send you.
Start the conversation