Cybersecurity credentials
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The problem
What is usually behind this search
We do not have an office in Jubail
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.
Most organisations do not have a security problem they can name. They have an assessment coming, a customer requirement they cannot evidence, or a suspicion that the estate has grown faster than the controls over it. All three produce the same underlying question: what is actually exposed, and how would we know if something happened?
The answer usually is not more tooling. Security products accumulate in the same way applications do, and an environment running four overlapping tools with nobody reading the output is less secure than one running two that someone acts on. The work is generally to establish what exists, reduce what is unnecessary, and make what remains produce evidence somebody uses.
Capabilities
What we actually deliver
Assessment and gap analysis
Technical assessment of the environment mapped against whichever control set applies to you, producing a prioritised list of findings with an owner and an effort estimate against each.
Penetration testing and VAPT
Testing of web applications, APIs, mobile applications, internal and external networks and cloud configuration, reported with reproduction steps rather than tool output.
Remediation engineering
Fixing what the assessment found — segmentation, identity and access, hardening, logging, key and secret management — rather than handing over a report and leaving.
Detection and monitoring
Log collection, detection rules written for your environment rather than a vendor default set, and an alerting model tuned so the volume is something a real team can work through.
Operating technology and industrial security
Passive asset discovery, protocol-aware monitoring, segmentation between plant and corporate networks, and controlled remote access for vendors — designed around a maintenance calendar, not against it.
Compliance evidence
Assembling the documentation, logs and change records an assessor will ask for, and putting a process in place so the next cycle does not start from nothing.
Local context
Why this is different in Jubail
Jubail is an industrial city in the literal sense: the Royal Commission plans, builds and regulates the industrial estate, its utilities and its supporting infrastructure. Petrochemical plants, desalination and power, and the heavy manufacturing that sits around them make up the economic base.
Technology risk here is concentrated almost entirely in operating technology. Distributed control systems, safety instrumented systems, plant historians and the networks connecting them govern processes where an unplanned stop is measured in millions and, in the wrong circumstances, in safety consequences.
That changes the nature of every engagement. A change that would be routine in a corporate environment requires a management-of-change process, a defined maintenance window and an operations sign-off. Vendors who do not work this way are not slow in Jubail — they are unsafe, and they do not get a second project.
What buyers in Jubail run into
- 01
IT security practice does not transfer to the plant
Vulnerability scanning, forced patching and endpoint agents can disrupt control systems that were never designed to tolerate them. Industrial environments need passive discovery, protocol-aware monitoring and change scheduled around the maintenance calendar. Applying a corporate playbook to a plant is the most common and most damaging mistake.
- 02
Nobody has a complete asset inventory
Control-system estates accumulate over decades of projects, each with its own contractor and documentation standard. Most sites cannot produce an accurate list of what is connected. Passive asset discovery is almost always the first useful deliverable, because every subsequent decision depends on it.
- 03
Remote access is the widest exposure and the hardest to remove
Vendor support connections into control networks are operationally necessary and frequently undocumented, shared or permanently open. Replacing them with brokered, monitored, time-bound access is high-value work, but it has to be done without stripping engineers of the support they genuinely rely on.
How an engagement runs
The stages, and what happens in each
Scope
Agree what is in scope, what is off limits, and what a finding has to look like to be actionable.
Assess
Technical assessment and testing, run to the agreed rules of engagement and windows.
Report
Findings with reproduction steps, business impact and a prioritised remediation plan.
Remediate
Fix the findings, either with your team or as an engineering workstream we run.
Verify
Retest what was fixed, so closure is evidenced rather than asserted.
Operate
Monitoring and periodic reassessment, or handover to your team with the runbooks to do it.
Regulatory frame
What governs this work
References for buyers. Techbanq does not issue certifications, approvals or compliance determinations — those rest with the authority and its assessors.
The full frame in Saudi Arabia- NCA ECC
The Essential Cybersecurity Controls — the national minimum baseline for government entities and for private operators of critical national infrastructure. The 2024 revision expanded both scope and control depth.
- NCA CCC
Cloud Cybersecurity Controls — the requirements applied to cloud service providers and to the entities consuming their services.
- Aramco SACS-002 / CCC
Saudi Aramco's third-party cybersecurity standard. Vendors are classified into CCC or the on-site CCC+ tier, with audits carried out by firms Aramco authorises.
- PDPL
The Personal Data Protection Law, enforced by SDAIA. Sets lawful basis, transfer, retention and breach-notification duties for anyone processing personal data in the Kingdom.
- SAMA Cyber Security Framework
The mandatory framework for SAMA-regulated entities, organised across governance, risk, operations, third-party security, resilience and compliance.
Technologies
What we work with
Cost
What moves the price
We do not publish fixed prices, because any figure quoted before the scope is known is a guess. These are the variables that actually determine it.
Scope size
The number of applications, network ranges, cloud accounts and sites in scope is the single largest driver.
Depth of testing
An automated scan, an authenticated application test and a full red team are different orders of effort. Ask which you actually need.
Control framework
Mapping against a published control set with an evidence format adds documentation effort beyond the technical work.
Environment type
Industrial and operating technology environments take longer because testing has to be planned around production.
Remediation scope
Assessment is predictable; remediation depends entirely on what the assessment finds. We estimate it afterwards, not before.
Common questions
What buyers usually ask
How long does a penetration test take?+
For a single web application or API, typically one to two weeks of testing plus reporting. A network or multi-application scope runs longer. The variable that matters most is scope size, so we would rather agree a precise scope than quote a duration against a vague one.
What do you need from us to start?+
A scope definition, written authorisation to test, technical contacts, and — for authenticated testing — test accounts at the privilege levels you want covered. For industrial environments we also need the maintenance calendar and an operations contact before anything active happens.
Do you help fix the findings or only report them?+
Both are available, and we would usually recommend the first. A report without remediation capacity tends to sit until the next assessment finds the same things. Where your team will do the fixing, we support them and retest; where they do not have capacity, we run it as an engineering workstream.
Can you test without disrupting live systems?+
Yes, with planning. Testing that carries any disruption risk is scheduled in an agreed window with a rollback and an operations contact on call. In industrial environments we default to passive techniques and treat any active step as a change requiring approval.
Other services in Jubail
Related
Cybersecurity services in other cities
Discuss cybersecurity in Jubail
Send us the scope as you understand it today, even if it is incomplete, and we will tell you what we need to know before giving an estimate.
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
