Techbanq

Aramco · contractors

The laptop that goes into the plant

A contractor's exposure is not the corporate network. It is the engineering laptop that connects to a control system, the rotating crew whose accounts outlive their rotation, and the support connection nobody closed when the project finished.

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

Market
Saudi Arabia
Written for
Plant Manager, CISO
Decision
Meet cybersecurity requirements as an on-site contractor

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

What changes

Four requirements a site contract adds

Each is ordinary in an operating environment and unfamiliar to a supplier whose other clients are offices.

Site devices

Managed, hardened, encrypted laptops with controlled removable media, and a defined process for devices that enter an operating area.

Where it usually fails: The engineer's personal laptop, used because the managed one lacked a vendor tool.

Workforce access

Accounts created on mobilisation and removed on demobilisation, including subcontracted staff.

Where it usually fails: A rotation ends and the accounts stay, because demobilisation is an HR process nobody connected to identity.

Engineering data

Drawings and configuration held in a controlled repository, with a rule for what may leave the site and how.

Where it usually fails: A copy on a personal drive for convenience, which is discovered during the audit rather than before it.

Remote support

Time-bounded, approved, logged connections that close when the work does.

Where it usually fails: A permanent tunnel opened for commissioning three years ago and never reviewed.

Working around the plant

The maintenance window is the schedule

Anything that touches a control system waits for a window, and windows come once or twice a year. A plan that assumes IT-style change control will slip by months, and the slippage is not recoverable by adding people. The sequencing rule is that anything requiring a window is identified in the first weeks and everything else is arranged around it.

The same constraint shapes assessment method. Active scanning is not appropriate against live control systems, so the work is passive collection, configuration review and interviews — slower to produce and read differently from an IT report, which is worth explaining to a customer expecting the latter.

Recurring gaps

Three that appear on almost every contractor review

  1. 01

    Subcontractors outside the controls

    Your obligations flow down and the paperwork frequently does not. A subcontracted crew with site access and no security schedule is a finding against you, not against them.

  2. 02

    Devices that never come back

    Laptops issued for a mobilisation and written off when a crew rotates. An asset register that does not match reality undermines every device control on top of it.

  3. 03

    Photographs of screens

    A phone photograph of a control screen sent to a colleague is the most common data leaving an operating area, and it is a training and policy problem rather than a technical one.

Our role

What we cover for a site contractor

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

  2. 02

    Remediation

    The engineering work itself — segmentation, access control, logging, hardening — with the procedure recorded as it is implemented rather than written up afterwards.

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

Work inside an operating area is always performed under the operator's own authorisation and permit process, and the audit is conducted through an authorised firm from the published list.

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

Do the requirements apply to our subcontractors?+

The obligation sits with you and flows down through your contracts with them. In practice that means a security schedule in the subcontract, named contacts, and access that is issued and removed by you rather than by them. A subcontractor with independent site access and no flow-down is the gap most often found.

Can you assess systems inside the plant?+

Under the operator's authorisation and permit process, and with passive methods appropriate to live control systems. Active scanning against operating equipment is not something we will propose; where a customer expects an IT-style report, that expectation is worth resetting before the work starts rather than after.

We are a small contractor. Is this proportionate?+

The requirement follows the access rather than the headcount, so a small crew with a connection into an operating environment carries real obligations. What is proportionate is the scope: a narrow, well-documented boundary around the systems that do the work keeps the programme small, and that scoping is the first thing worth spending money on.

Next step

Scope the site and the systems together

A review covering the site work as well as the office estate, so the controls match how the contract is actually delivered.

Scope the site and the systems together

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.