Counter-Drone Requirements for Saudi Oil, Gas, and Port Sites

Unmanned aircraft are now a planning assumption for every perimeter in the Kingdom, not an edge case. Consumer drones are cheap, widely available, and capable of carrying a payload or streaming video over a site boundary in minutes. For oil and gas plants, water infrastructure, and ports, the question is no longer whether to defend against drones, but which layers to deploy, in which order, and under whose authority.

Why counter-UAS is different from other security systems

Most security systems observe. Counter-UAS spans two very different activities: detection, which is passive and broadly deployable, and mitigation, which transmits energy or interferes with a vehicle and is therefore treated as a regulated act. Mixing the two in a single procurement is the most common source of non-compliant designs. A system that can see a drone is not automatically a system that is allowed to stop it.

The distinction matters commercially as well as legally. Sensors can be purchased, installed, and integrated by a security contractor. Active mitigation is delivered under government authority, through licensed programmes, with rules of engagement and accountability that sit outside a normal facilities contract. Any bid that blurs that line should be treated as a compliance risk.

Licensing matrix: detection layers

The matrix below summarises how detection layers typically map to approval paths in the Kingdom. Exact requirements depend on the site, the equipment, and the authority exercising jurisdiction; the design should document each layer against its approval before purchase.

• Long-range radar — passive sensing. Requires equipment type approval and site security approval; deployable for private critical infrastructure.
• RF spectrum monitoring — passive listening. Requires CST type approval for the receiver and coordination of the monitored bands; deployable.
• Electro-optical and thermal imaging — standard security equipment. Requires HCIS or site security approval, plus privacy controls for the field of view; deployable.
• Acoustic sensors — passive cueing. Site approval only; best used as a secondary sensor rather than a primary track source.
• Command and control — integration layer with no transmit licence of its own, but it must document data flows, operator roles, and escalation paths.

Licensing matrix: mitigation layers

Mitigation is where authority, not technology, determines what is possible. The rows below describe the approval context rather than a procurement menu; none of these effects should be deployed by a private operator without written authorisation.

• RF disruption or jamming — active transmitter. Restricted to authorised government entities under CST spectrum authority and Ministry of Interior coordination; not a commercial facility capability.
• GNSS interference or spoofing — active and high-risk. Government-authorised programmes only; unlawful use can affect aviation and other critical systems far beyond the site.
• Protocol takeover or cyber effects — active. Requires an authorised counter-UAS programme, legal oversight, and defined rules of engagement.
• Kinetic interception — military or law-enforcement authority only; outside the scope of commercial facility design.
• Mitigation integration — a commercial integrator can design the handover, escalation, and interface to the licensed authority; the effect itself remains under that authority's control.

What a compliant architecture looks like

A defensible design starts with detection and identification, then routes decisions to people who are authorised to act. The sequence we use is Detect · Identify · Defend · Report:

• Detect — layer radar, RF, and EO/IR so a single sensor failure does not create a blind spot, and correlate tracks in one command-and-control view.
• Identify — classify the track, estimate intent from flight behaviour, and separate a nuisance overflight from a credible threat.
• Decide — apply written escalation rules: who is called, at what threshold, and which authority takes control of any mitigation.
• Report — preserve time-stamped track evidence and operator actions for investigations, insurers, and regulators.

Integration with the existing security estate is part of compliance, not an afterthought. A counter-UAS track that never reaches the video wall, the access-control system, or the incident workflow is an expensive dashboard. Conversely, a command-and-control platform connected to the plant network inherits the site's OT cyber obligations — segmentation, logging, patch governance, and vendor access controls under ECC-2 and the NCA OT Controls.

Site-specific considerations for oil, gas, and ports

Radar performance is shaped by the environment. Flare stacks, rotating equipment, cranes, and reflective structures create clutter; RF congestion in a port or industrial city limits what spectrum monitoring can hear. Thermal contrast changes with sun angle, and a detection layout that works at noon may miss a small drone at dusk. These are engineering problems, solved with sensor placement, multi-sensor correlation, and a tested concept of operations — not by buying a bigger box.

Ports add a second dimension: traffic. A drone track that crosses a channel, a terminal, and a public road passes through several jurisdictions and operational owners. The design has to define who owns the track at each boundary and how handover happens in real time.

Procurement questions that expose non-compliant bids

• Which layers transmit, and under whose licence will they operate?
• Who holds the spectrum approval, and what happens if it is withdrawn?
• After detection, who is authorised to act — and how is that authority documented?
• How does the system hand evidence to the relevant authority after an incident?
• Can detection operate independently of any mitigation module, so the site remains compliant while approvals are pending?
• How is the command-and-control platform segmented and monitored under the site's OT cyber controls?

The bottom line

Counter-UAS in the Kingdom is a licensing problem wrapped around an engineering problem. Detection is deployable today and should be designed first. Mitigation is a government-authorised activity; the commercial integrator's job is to build the detection, decision, and handover architecture that lets the authorised authority act on trustworthy information. Sites that plan in that order avoid buying capability they cannot legally use.

Lantern designs detection-first counter-UAS architectures for critical facilities — radar, RF, thermal, command-and-control integration, and the escalation workflow to licensed authorities — inside the Detect · Identify · Defend · Report framework.