- Market
- Saudi Arabia
- Written for
- CISO, Procurement
- Decision
- Assemble evidence that will survive a CCC audit
- Languages
- EN · AR
Credentials for Aramco compliance
NCA registration
Registered cybersecurity service provider

Aramco CCC
CCC certified

ISO/IEC 27001
ISO/IEC 27001 certified
Artefacts
What each control area has to produce
The pattern is the same across areas: a configuration showing the control exists, and a record showing it operated. Most failures are the second half.
Access control
The permission model, joiner and leaver procedure, and privileged account inventory.
Operating evidence: Dated access reviews with names against them, and leaver records matched to HR dates.
Network segmentation
A current diagram that matches the estate, and the rule base with a justification per exception.
Operating evidence: Change records for rule modifications, and a periodic review of what is still needed.
Logging and monitoring
What is logged, retention configuration, and who receives an alert.
Operating evidence: Alerts with the response recorded, over the period — the most commonly missing artefact.
Patching and vulnerability
The policy, the tooling, and the exception process for what cannot be patched.
Operating evidence: Cycle records showing what was applied and when, including the exceptions with an owner and a date.
Incident response
A plan naming roles and contacts, aligned to the contract's notification terms.
Operating evidence: A test or a real incident with the timeline recorded. A plan nobody has exercised reads as a document.
The period
The one input money cannot buy back
A control implemented in the final month has no operating history for the audit to look at. Everything else in a readiness programme can be accelerated by adding people; this cannot, because it is time passing while the control runs. It is the reason a plan that ends on implementation is wrong by the length of the period it forgot.
The practical consequence is a sequencing rule: controls that need an operating record go first, even where they are not the largest gaps, and the visible technical work follows. Programmes sequenced by effort rather than by evidence arrive at the audit with the hardest problems solved and the simplest ones undemonstrable.
Findings
Four evidence failures that recur
- 01
Evidence produced for the audit
A review dated three days before the visit, for a control that has existed for two years. It raises exactly the question you did not want raised, and the honest fix is to start the cycle and disclose the start date.
- 02
The scope in the evidence is not the scope declared
An access review covering the corporate domain when the contracted work runs on a separate platform. The document is real and answers a different question.
- 03
No owner named
Artefacts that nobody signed. An auditor asks who is responsible for the control, and a document with no name on it makes that question harder than it should be.
- 04
Retention shorter than the period
Logs configured with a default retention that expires before the audit window opens. The control ran and the record is gone, which is indistinguishable from the control not running.
Our role
What we do on the evidence side
- 01
Scope determination
Which systems perform the contracted work, which connections cross the boundary, and the reasoning for what sits outside it — written to be read by the auditor.
- 02
Remediation
The engineering work itself — segmentation, access control, logging, hardening — with the procedure recorded as it is implemented rather than written up afterwards.
- 03
Evidence assembly
Artefacts generated by the control that runs, covering a period the audit can measure, reviewed against the requirement before anyone else reads them.
The audit that reads the pack is conducted through an audit firm Saudi Aramco authorises, selected from the published list, and the pack is written to be read by them.
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
How long an operating period is enough?+
Long enough that the control has run through its own cycle more than once — a quarterly review needs two quarters to look like a practice rather than an event. Where the contract date does not allow that, the position to take is disclosure: state when the control started and show it running since, rather than presenting a first cycle as a steady state.
Can we reuse evidence prepared for another framework?+
Frequently, and it is the cheapest thing to check first. Access reviews, patch cycles and incident records prepared for ISO 27001 or an NCA assessment usually answer the same underlying question. What has to be verified is scope: the artefact must cover the systems performing the contracted work, and that is where reuse most often fails.
What if a control genuinely was not operating?+
Disclose it, with the date it started and the plan behind it. Auditors see remediation in progress regularly and it is a normal finding; what damages an engagement is an artefact that implies a period the control did not cover, because it turns a control gap into a question about the reliability of everything else in the pack.
In this cluster
Next step
Review the evidence you already hold
A review of the evidence you already hold, with the controls that will need an operating period identified while there is still time to start it.
Review the evidence you already hold
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
