Techbanq

Blocked contract

The date is the problem, not the controls

The controls are achievable. What is usually not achievable is achieving them by the date already in the contract, and the sooner that conversation happens the more options remain in it.

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

Market
Saudi Arabia
Written for
Commercial Director, CIO
Decision
Unblock a contract held up on a cybersecurity requirement

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

First week

Four things to establish before spending anything

None of these costs money and all of them change what the project is. Suppliers who skip them commonly buy a remediation programme scoped against an assumption.

STAGE 01

1 · Which requirement, exactly

Get the clause and the referenced standard in writing from your contract contact. Requirements differ by the nature of the work and the data involved, and a supplier working from a second-hand description frequently prepares for the wrong one. The actual applicable requirement, in writing.

STAGE 02

2 · Which of your systems it touches

The systems doing the contracted work, holding the customer's data, or connecting to their environment. This is the scope, and it determines the size of everything downstream. A boundary, and an early view of whether it can be drawn at all.

STAGE 03

3 · Whether the estate is segmented

The single question that determines whether this is a three-month project or a nine-month one. If the contract systems share a flat network with the rest of the business, the segmentation work dominates the timeline. Which of the two timelines you are on.

STAGE 04

4 · The date conversation

Go back to the customer with a plan and a realistic date rather than silence followed by a missed one. A supplier presenting a credible schedule is in a different position from one that stops responding. A conversation about a plan rather than about a delay.

Timelines

Why the honest date is later than you want it to be

Two positions account for most suppliers. In the first, the systems doing the contracted work already sit behind their own boundary, access is managed through a directory, and there is some logging. From there, readiness is a matter of closing specific control gaps and building the evidence record: three to five months, most of it evidence rather than engineering.

In the second, everything is on one network, administrative accounts are shared, and there is no directory. Here the scope cannot be drawn until the estate is separated, and separating a working environment without interrupting delivery is slow — not because the work is difficult but because it has to be done in stages against a business that is still operating. Six to nine months is realistic and shorter promises usually turn into a second audit booking.

What compresses a timeline legitimately is narrowing the scope to what the requirement genuinely touches, and starting the evidence record on day one rather than after the technical work finishes. What does not compress it is booking the audit earlier. The audit measures a state; bringing it forward measures an earlier state.

What goes wrong

Four expensive responses to a blocked contract

  1. 01

    Buying a certificate rather than readiness

    A supplier promising to obtain the certificate on your behalf is describing something that does not work that way. It is issued through an authorised audit firm against your actual controls; nobody can supply it as a product.

  2. 02

    Starting remediation before scope

    Money spent hardening systems that turn out to be outside the boundary, while a connected system inside it goes untouched. The scope determination costs a fraction of what it saves.

  3. 03

    Not telling the customer until the date passes

    Silence reads as inability. A schedule presented three months early, with progress against it, is a very different conversation from an explanation offered the week after the deadline.

  4. 04

    Treating it as a one-off

    The requirement recurs on renewal and the same questions come from other customers. Building the controls to be maintained is barely more expensive than building them to pass once, and it is much cheaper than doing it twice.

Our role

What we can honestly offer here

  1. 01

    Triage in the first week

    We triage quickly, because the first week decides whether the conversation about the date happens usefully or late.

  2. 02

    A timeline we believe

    You get a schedule we stand behind, including the case where the achievable date is later than the contract date. That is the number your customer conversation needs.

  3. 03

    The work itself

    We do the remediation and assemble the evidence for the audit — the engineering, the procedures and the records, in the order the requirement reads them.

The certificate is then issued through an audit firm Saudi Aramco authorises, against your own controls, which is why the readiness work has to be real before the audit is booked.

Saudi Aramco publishes its third-party cybersecurity requirements and maintains the list of firms authorised to conduct the compliance audit. Select the auditor from the published list rather than from a supplier's recommendation. Source

Common questions

What buyers ask

Can we get an extension?+

That is a commercial conversation with your contract contact and it goes better with a plan attached. What tends to be received well is a written schedule showing the scope, the gaps, the sequence and the date, with the first milestone already met. What tends not to be is a request for more time with nothing behind it. We can produce the schedule; the conversation is yours to have and it is worth having early.

Our subcontractor holds the systems. Whose problem is it?+

Yours, contractually, and theirs practically. The requirement follows the data and the connection rather than the ownership of the hardware, so a subcontractor inside your boundary is inside your scope. Bring them into the readiness work early — the alternative is discovering during the audit that a system in scope belongs to someone with no obligation to you and no plan.

Is there a shorter route for a small supplier?+

The scope is the route. A small supplier whose contracted work runs on three systems and one cloud account has a genuinely small scope, and drawing that boundary accurately is what makes the project proportionate. Where the work runs on the same laptops and file shares as everything else, the honest answer is that separating it is the first project, and there is no version of readiness that skips it.

Get a timeline you can take to the customer

A triage in the first week that produces a defensible timeline, so the conversation with the customer is about a plan rather than about a delay.

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.