Techbanq

Aramco supply chain · requirements

A requirement about a relationship, not a company

Suppliers read the requirement as a statement about their business. It is closer to a statement about one contract: which of your systems process the customer's data or connect to their environment in the course of that work.

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

Control areas

What each area asks for, and what the audit looks at

The published standard is the authority and this is not a substitute for reading it. What it adds is the translation a first reading needs: what the auditor will actually ask to see.

Scope and boundary

A defensible statement of which systems perform the contracted work and which connections cross the boundary.

What the audit asks to see: A network diagram the auditor can follow, and the reasoning for what sits outside.

Segregation

The scoped estate separated from the rest of the business at the network level.

What the audit asks to see: Firewall rules and VLAN configuration, and evidence they were reviewed rather than set once.

Access to customer data

Who in your organisation can reach it, through which accounts, and on what authorisation.

What the audit asks to see: The access list with approvals, and the dated review record — not the list alone.

Remote access

Multi-factor authentication on every route into the scoped estate, including vendor and support routes.

What the audit asks to see: Configuration plus a sample of authentication logs across the period.

Endpoint and patching

Protection deployed across the scoped estate, and patching against a stated timeframe.

What the audit asks to see: Coverage figures and remediation timelines measured against your own policy.

Logging and incident response

Collection with retention, a response procedure, and a route for notifying the customer.

What the audit asks to see: The incident register including minor incidents, and one rehearsal record.

Subcontractors

Anyone inside your boundary named, with security terms in their contract and an assessment behind it.

What the audit asks to see: The register and the assessments. The area most often owned by nobody.

Scoping

Wrong in either direction is expensive

Scoped too widely, a supplier remediates systems the requirement never reached and pays for an audit across an estate that did not need to be in it. Most first attempts over-scope, because the safe-feeling move is to include everything and the cost of that only appears later.

Scoped too narrowly, the audit finds a connected system outside the declared boundary and stops while the scope is redrawn — which usually means booking the auditor a second time. The audit follows connections, so a boundary that a connection crosses is not a boundary, however it is drawn on the diagram.

Common misreadings

Four things suppliers assume that are not asked

  1. 01

    "Our whole company needs certifying"

    The requirement follows the contracted work. A supplier whose work for the customer runs on three systems and one cloud account has a genuinely small scope, and drawing that boundary accurately is what makes the project proportionate.

  2. 02

    "We need a new security platform"

    Most control text describes an outcome and the record that shows it holding. Several areas are met by an existing tool configured properly plus a signed review, and buying a product for those closes nothing the auditor will look at.

  3. 03

    "The certificate covers us for other customers"

    It is issued in respect of a specific requirement, not as a general security certification. The work behind it carries across and answers much of what the next customer asks; the certificate itself does not.

  4. 04

    "Our hosting provider handles it"

    A provider's own certifications cover their platform, not your configuration on it or your people's access to it. The boundary between what they hold and what you hold is published by the provider and is worth reading before assuming.

Our role

Our role in meeting the requirement

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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

Which standard applies to us?+

That comes from your contract, not from a supplier reading it for you. Get the clause and the referenced standard in writing from your Aramco contract contact — requirements differ by the nature of the work and the data involved, and a supplier preparing from a second-hand description frequently prepares for the wrong one. It is a short email and it is the cheapest step in the whole project.

Do we need the certificate before we can bid?+

That depends on the contract and the stage, and your contract contact is the one who can answer it. What is generally true: a supplier with a credible readiness plan and a booked audit date is in a different position from one with neither, and that difference is worth establishing before the question is asked rather than after.

Can we reuse work from an ISO certification?+

Much of it, and it shortens the preparation meaningfully. An organisation with a management system already has documented processes, an asset register and the habit of producing evidence, which is most of what makes an audit cheap. What does not carry is scope: an ISO certificate covers the boundary its holder defined, and the auditor here reads the boundary the contract defines.

Map the requirement to your systems

A written scope statement naming the systems in and out, with the reasoning, before any remediation is priced.

Start the conversation