Short answer
An electronic lock cannot prevent a hijacking that involves force, and no vendor should claim it can. What it does is raise the difficulty of unauthorised access and convert an opening or tamper into a detected, located, timestamped record, a security, deterrence and monitoring layer, not a replacement for driver and vehicle procedures.
Key takeaways
- An electronic lock is a deterrence, detection and evidence layer, it does not stop force.
- Its real contribution is speed: an opening becomes known in minutes instead of at delivery.
- Deterrence works against opportunistic theft, not against a planned, equipped attack.
- The lock is worthless without a response process: an alert nobody acts on changes nothing.
- Driver vetting, route planning and stop discipline still do most of the protective work.
01Setting the claim honestly first
A fuel tanker carries a cargo that is valuable, liquid, easily transferred and hard to trace once moved. That combination attracts a range of threats, from a driver siphoning a few hundred litres to an organised diversion of a whole load.
Electronic locks are frequently marketed as preventing tanker hijacking. They do not. A device bolted to a valve or a hatch is a physical obstacle and a reporting mechanism; it has no capacity to intervene against people, and a determined group with time, tools or coercion will get past it.
Being clear about that is not a weakness in the product case, it is what makes the rest of the case credible. The genuine value sits in three narrower claims: unauthorised access becomes harder, an attempt becomes visible, and what happened becomes documented. Each is real and each is worth paying for, and none of them is prevention.
02What deterrence actually means here
Deterrence is not a property of the lock; it is a property of the attacker’s calculation. A visible, obviously connected device changes the expected cost of an attempt, and that change is enough to redirect some attackers and irrelevant to others.
Against opportunistic theft it works well. Someone who noticed an unattended tanker and considered drawing a few hundred litres is deterred by a device that will report the attempt with a location, because the opportunity depended on nobody knowing.
Against a planned attack it does very little. A group that selected the route, brought tools and accounted for the tracking has already priced the lock into the plan. Expecting the same device to address both threat classes is the error that produces disappointed buyers, and it is worth deciding at purchase which one you are actually buying against.
03Where the device genuinely changes the outcome
The decisive variable is time. Under a mechanical seal, a diversion is discovered when the tanker arrives and someone checks the seal, potentially many hours after the fuel left. Under a connected lock, the opening generates an event as it happens.
That difference is what creates the possibility of intervention. A tanker that stops off-route and reports a valve opening at 02:40 is a situation someone can respond to while the vehicle is still there. The same fact learned at 09:00 the next morning is an insurance claim.
It also changes what can be established afterwards. A located, timestamped sequence of events, stop, opening, duration, movement resuming, is a materially stronger position in a dispute than a broken seal and two conflicting accounts, and it is often the part of the value that survives even when the loss itself could not be prevented.
04The threat the lock addresses best
The most common fuel loss on tanker routes is not a dramatic hijacking. It is a small, repeated, internal diversion, a stop that is not on the schedule, a partial transfer, a resumed journey and a delivery that is short by an amount small enough to be argued about.
This is precisely the pattern a connected lock is good at. The loss depends on the stop being unremarkable and the opening being unrecorded, and a device that timestamps and locates every valve event removes both conditions without needing to resist any force at all.
It is also the pattern that accumulates the most money over a year. A single hijacked load is a large, visible, insurable event; a hundred small short deliveries are an unexplained margin problem that nobody attributes to theft because no single instance looks like one.
05Master and slave on a multi-compartment tanker
A tanker with several compartments has several points that can be opened, and putting a fully connected lock on each is expensive and unnecessary when they all travel together.
The master and slave arrangement fits this directly. The Jointech JT701 acts as the connected master, carrying GSM/3G with dual SIM, its own GPS at a quoted 2.5 m CEP, and a 15,000 mAh battery. The JT709ex field locks carry no cellular connection and no GPS of their own, link to the master over Bluetooth or LoRa at up to 1 km in open area, and are quoted at up to three years of standby life.
The dependency is worth stating plainly: every slave is only as reachable as its master. A master that fails or goes out of range silences the whole set rather than one compartment, which is an acceptable exchange for removing a SIM and a charging routine from each lock, but only if it is a decision rather than a surprise.
06What an attacker does about the device
Assume the attacker knows the lock is there. The realistic responses are to cut the securing element, open the housing to disable the electronics, or remove the unit entirely, and the device is designed to report each of those rather than resist them indefinitely.
The JT701 detects rope cut, cover opening and vibration; the JT709ex reports tamper, shackle cut, and use of its mechanical emergency key. Each generates an event before or during the attack rather than afterwards, which is the mechanism by which detection substitutes for resistance.
The one response that defeats the reporting is removing the device where there is no coverage and no witness. This is why local event buffering matters: a unit that retains events and resends them in order when connectivity returns still delivers the record, whereas a device that only transmits live loses exactly the interval an attacker chose for being unobserved.
07Geofencing and scheduled stops
A valve opening is not suspicious in itself, deliveries require it. What makes an opening suspicious is that it happened somewhere it was not supposed to, which is a question about the route rather than about the lock.
Defining the planned stops in advance converts every other opening into an exception. The lock reports the event and its position; the platform decides whether that position was expected. Without the route definition, an operator receives a stream of openings and has to reconstruct from memory whether each was legitimate.
The practical caveat is that positioning degrades exactly where tankers spend time, inside terminals, under gantries, between structures. A 2.5 m CEP figure describes open-sky conditions, so a geofence should be sized with a margin rather than drawn tightly around a depot boundary, or it will generate exceptions for vehicles that are exactly where they should be.
08The response process is the product
Everything above depends on someone acting. An electronic lock generates events during the journey, and if those events reach nobody with the authority and information to respond, the organisation has purchased a more detailed record of losses it still did not prevent.
That means assigning a named recipient and a response expectation before deployment, not after. A tanker route running overnight needs an overnight recipient; a system whose alerts arrive in an inbox read at nine in the morning has converted a real-time capability into a reporting one.
It also means deciding in advance what the response actually is. "Call the driver" is a decision; so is "notify the depot and hold the delivery"; so is "contact local authorities". Working that out during the first incident is how the useful window gets spent on deliberation.
09What still does the heavy lifting
The measures that reduce tanker losses most are not technological. Driver vetting and retention, route planning that avoids known problem stretches, discipline about unscheduled stops, and pairing or convoying on high-risk legs all outperform any device.
The lock supports those measures rather than replacing them. Stop discipline is enforceable because deviations are visible; driver accountability is fairer because openings are attributable; route planning improves because the data shows where incidents cluster. In each case the human process is doing the work and the device is supplying the evidence.
A programme that installs locks and changes nothing else usually sees a smaller improvement than expected, and concludes the device underperformed. The more accurate conclusion is that the device did what it does, it made things visible, and nothing downstream was set up to use the visibility. Budgeting for the process alongside the hardware, rather than after it, is what separates the deployments that hold from the ones quietly abandoned in year two.
10The GCC operating envelope for a tanker lock
A device mounted on a tanker in the Gulf sits in a harder thermal environment than the published envelope suggests at first glance. The JT701 is rated −20 to +70 °C and the JT709ex −20 to +60 °C, against the −40 to +85 °C typical of fixed fuel sensors, and a metal fitting in direct afternoon sun is not at air temperature.
Both carry IP67, which under IEC 60529 means dust-tight with resistance to temporary immersion. That is the right rating for an exposed road vehicle, with the standard caveat that the rating protects a correctly closed enclosure and a charging port cover left unseated is outside it.
Coverage is the third constraint and the one that most affects the security value. Cross-border tanker corridors include stretches with intermittent cellular service, so local event retention with ordered resynchronisation is not a nice-to-have, it is the difference between a record and a gap across the interval an attacker would choose.
11How to specify this without overclaiming
Write the requirement in terms of detection and evidence rather than prevention, because that is what can be delivered and therefore what can be tested. "Any valve opening outside a defined stop is reported with position and time within a stated interval" is a specification a vendor can be held to.
Ask the vendor directly what happens to events during a coverage gap, and treat a vague answer as disqualifying. Ask what the device reports when it is removed, and what the platform does when a unit stops reporting at all, silence is the failure mode most likely to matter.
Then state the limit in your own internal documentation as plainly as in the purchase decision. A security programme that records "electronic locks deter opportunistic access and document openings; they do not prevent forced entry or coercion" is a programme that will not be surprised, and will not have promised something it cannot deliver to its own management.
12How ENTEK.AI positions this capability
ENTEK.AI treats a tanker lock as one asset among the vehicle, the tank and the trip. A valve opening is recorded with its time and position, on a geofenced trip that shows whether the stop was planned, and the lock events and the tank readings can be reviewed side by side. That combination is the useful part, and it is not available from a lock alone.
The platform does not claim to prevent hijacking, and no ENTEK material should say otherwise. It shortens the time between an unauthorised opening and someone knowing about it, and it produces an auditable record of what happened, the deterrence, detection and monitoring layer described throughout this article.
On this topic in particular, an overclaim would be worse than useless: a security buyer who discovers the limit during an incident will not extend the benefit of the doubt to anything else in the system.
| Threat | Does the lock prevent it? | What the lock does contribute |
|---|---|---|
| Opportunistic siphoning at an unattended stop | Often deters it | Located, timestamped opening event |
| Internal partial diversion during a trip | No | Removes the two conditions the loss relied on |
| Planned, equipped theft of a load | No | Evidence trail; possible intervention if response is staffed |
| Hijacking involving force or coercion | No, and no vendor should claim it | Detection and documentation only |
| Device removal in a coverage gap | No | Only if events were buffered and resent in order |
| Dispute over a short delivery | n/a | Strongest contribution, an auditable event record |
Figures and sources
- Jointech JT701 tamper conditions detected: rope cut, cover open, vibration (Source: ENTEK.AI product specification, Jointech JT701, as of 2026-08-30)
- Jointech JT709ex alert types published: tamper, mechanical key used, shackle cut (Source: ENTEK.AI product specification, Jointech JT709ex, as of 2026-08-30)
- Jointech JT701 cellular connectivity: GSM / 3G, dual SIM (Source: ENTEK.AI product specification, Jointech JT701, as of 2026-08-30)
- Jointech JT701 quoted GPS accuracy: 2.5 m CEP (Source: ENTEK.AI product specification, Jointech JT701, as of 2026-08-30)
- Jointech JT701 battery capacity: 15,000 mAh Li-ion (Source: ENTEK.AI product specification, Jointech JT701, as of 2026-08-30)
- Jointech JT709ex link to its master, and range: Bluetooth / LoRa, up to 1 km (open area) (Source: ENTEK.AI product specification, Jointech JT709ex, as of 2026-08-30)
- Jointech JT709ex quoted standby life: up to 3 years (Source: ENTEK.AI product specification, Jointech JT709ex, as of 2026-08-30)
- Jointech JT709ex own positioning and cellular capability: none, uses the master for both (Source: ENTEK.AI product specification, Jointech JT709ex, as of 2026-08-30)
- Jointech JT701 operating temperature range: −20 to +70 °C (Source: ENTEK.AI product specification, Jointech JT701, as of 2026-08-30)
- Jointech JT709ex operating temperature range: −20 to +60 °C (Source: ENTEK.AI product specification, Jointech JT709ex, as of 2026-08-30)
- IP67, first digit: protection against solid foreign objects: dust-tight (no ingress of dust) (Source: IEC 60529, Degrees of protection provided by enclosures (IP Code), as of 2026-08-30)
- ISO 17712 mechanical seal classes, for comparison with an electronic device: I (indicative), S (security), H (high security) (Source: ISO 17712:2013, Freight containers, mechanical seals, as of 2026-08-30)
Questions
Can an electronic lock prevent a fuel tanker hijacking?
No. It cannot act against people and cannot resist force or coercion, and no vendor should claim otherwise. It makes unauthorised access harder, and it turns an opening or tamper into a detected, located, documented event, a deterrence, detection and monitoring layer, not prevention.
So what is it actually worth buying for?
Mainly for speed and evidence. An unauthorised opening becomes known in minutes rather than at delivery, which creates a window for intervention; and the located, timestamped record is a materially stronger position in a dispute than a broken seal and two conflicting accounts.
Do we need a connected lock on every compartment?
No. One connected master and several field locks is the normal arrangement: the JT709ex slaves carry no SIM and no GPS, link to the JT701 master over Bluetooth or LoRa at up to 1 km in open area, and are quoted at up to three years standby. The trade-off is that a master failure silences the whole set.
What is the most common reason a deployment disappoints?
No response process. The device generates events during the journey, but if the alert reaches nobody with the authority and information to act while the vehicle is still there, the organisation has bought a more detailed record of losses it still did not prevent.