Techbanq

Aramco supply chain · readiness

Draw the scope before you measure anything

Most suppliers arrive knowing they need a certificate and not knowing which of their systems the requirement touches. Measuring before the scope is drawn produces a report against the wrong estate.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
CISO, CIO
Decision
Establish the distance to CCC readiness before booking an authorised auditor

Credentials for Aramco compliance

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • Saudi Aramco

    Aramco CCC

    CCC certified

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Scope first

The question is which of your systems the contract touches

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

A supplier told to obtain a certificate usually reads that as a statement about the company. It is closer to a statement about a relationship: which of your systems process, store or connect to the customer's data and networks in the course of the contracted work. That set is frequently much smaller than the whole business, and occasionally much larger than the supplier expected because of an integration nobody was thinking about.

Getting this wrong is expensive in both directions. Scoped too widely, the supplier remediates systems the requirement never touched and pays for an audit across an estate that did not need to be in it. Scoped too narrowly, the audit finds a connected system outside the declared boundary, and the engagement stops while the scope is redrawn — which usually means booking the auditor a second time.

So the first deliverable is a scope statement with a boundary that can be defended: the systems in it, the connections crossing the boundary, and the reasoning for what sits outside. It is written to be read by the auditor rather than by us, and where a boundary decision is genuinely arguable we say so rather than choosing the convenient reading.

Sequence

From here to an audit that passes

STAGE 01

1 · Scope determination

The contracted work, the data it involves, the systems that touch it and the connections crossing the boundary. Written as a defensible statement rather than a list. A scope the auditor can accept or challenge before any remediation is bought.

STAGE 02

2 · Control-by-control readiness review

Each applicable control assessed against what exists in the scoped estate, with the evidence that would demonstrate it identified at the same time. A gap list with the evidence requirement attached to each item.

STAGE 03

3 · Remediation, sequenced by dependency

The work itself, ordered so that the controls other controls depend on land first. Timelines set against what the team can actually deliver rather than against the contract date. A closed gap list and the artefacts that show each closure.

STAGE 04

4 · Evidence assembly and audit support

The pack organised the way the audit will ask for it, and someone available to answer questions during the audit. The audit itself is conducted by the authorised firm, not by us. An audit that measures the controls rather than the preparation.

Recurring gaps

Where suppliers usually fall short

  1. 01

    No boundary between the contract estate and the rest

    The systems doing the contracted work sit on the same flat network as everything else, so the scope cannot be drawn anywhere defensible. Segmentation is the single most common structural gap and the one with the longest lead time.

  2. 02

    Access to customer data that nobody can enumerate

    Who in the supplier organisation can reach the customer's data, through which accounts, is a question the audit will ask directly. Answering it requires the access enumeration most suppliers have never run.

  3. 03

    Subcontractors outside the picture

    A development partner, a hosting provider, a support firm with remote access. Each is inside the boundary in practice and outside the supplier's documentation, and the audit will find the connection before it finds the paperwork.

  4. 04

    Controls in place with nothing to show

    The same pattern as any assessment: the control runs and produces no dated record. The remedy is the same and it is not technical work.

Our role

What the readiness engagement covers

The gap assessment is the first part of a body of work that has to be finished before an audit is worth booking. All of it is ours.

  1. 01

    Scope, then readiness

    We determine the scope, review readiness control by control against what is actually running, do the remediation and assemble the evidence.

  2. 02

    The date, early

    Where the realistic date falls after the contract date we say so at the start, so the conversation with your customer happens while it is still a schedule question.

  3. 03

    Through the audit

    We stay available while the audit runs, to answer questions about the work we did and the records behind it.

The audit itself is conducted through an audit firm Saudi Aramco authorises for that purpose, selected from the published list — its independence from the preparation is the point of the arrangement.

Saudi Aramco publishes its third-party cybersecurity requirements and maintains the list of firms authorised to conduct the compliance audit. Take the scope and applicability questions to your Aramco contract contact and to the authorised auditor, and select the auditor from the published list rather than from a supplier's recommendation. Source

Common questions

What buyers ask

How long does readiness take from a standing start?+

Where the estate is already segmented and access is managed, three to five months is realistic. Where the contract systems share a flat network with everything else, the segmentation work alone is usually the longest item and can add several months. The variance is almost entirely in that one structural question, which is why the scope determination comes first — it tells you which of those two situations you are in before you commit to a date.

Can we narrow the scope to reduce the work?+

You can draw the boundary where the work genuinely sits, and doing so accurately usually reduces it — most suppliers over-scope at first. What does not work is drawing it to exclude a system that connects across it. The audit follows the connections, and a boundary that a connection crosses is not a boundary. Where a reduction is legitimate, document the reasoning so the auditor can evaluate it rather than discovering it.

Does the certificate transfer to other customers?+

It is issued in respect of a specific requirement and is not a general security certification, so treat it as evidence for the relationship it was obtained for. The work behind it does carry across — segmentation, access management and evidence discipline built for one customer answer a large part of what the next one asks. What does not carry is the certificate itself as a claim about the company generally.

Next step

Draw the scope first

A scope determination and readiness review that lets the authorised audit be booked once, at a date the remediation plan supports.

Draw the scope first

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.