Tamper-evident seals and GPS tracking are detective controls for IT shipments: a numbered seal proves whether a container was opened, and a tracker shows where the shipment went and where it stopped. Neither prevents access, and organizations that buy them expecting prevention are disappointed. Their value depends on recording seal numbers, owning alerts, and reconciling both at delivery.
That is not a weakness. For equipment in transit, detection is usually the achievable goal — a truck can be stopped anywhere and a determined party will get into a container. What matters is that nobody can do so without leaving evidence, and that the evidence is checked.
Why Must Every Seal Number Be Recorded?
A seal's entire function is that its unique number, recorded at origin, either matches at destination or does not. Applied without recording the number, a seal proves nothing — anyone can cut one and fit another.
The number goes on the manifest at the point of application, along with who applied it and when. It is verified and recorded again at every custody transfer and at final delivery. A documented chain of custody is what turns a seal from a piece of plastic into an audit control.
Verification means reading the number and comparing it, not glancing at the seal. Substitution is the common attack and it defeats anyone who checks only that a seal is present.
Seals come in grades. Indicative seals — plastic pull-ties and tape — show casual interference and are defeated easily. Security seals, typically metal cable or bolt seals meeting ISO 17712, resist removal without obvious damage and are what freight and customs regimes such as CTPAT recognize. Barrier seals require a tool to remove and impose genuine delay.
Tape seals for cases and cartons should leave a void pattern when lifted. Cheap tape peels cleanly at temperature extremes, which produces false confidence rather than evidence.
What Can GPS Tracking Tell You About a Shipment?
Where the shipment is and whether it deviated, not what happened to its contents. GPS devices report location on an interval. That is genuinely useful and it is narrower than it sounds.
Real-time visibility supports exception management — a vehicle stopped where it should not be, a route deviation, a delivery running late enough to matter. The value is in the alerting rather than in the map, because nobody watches a map continuously.
Geofencing turns location into events. An alert when a shipment leaves a defined corridor, or fails to arrive within a window, is actionable in a way that a position log is not.
Environmental sensors on the same device often matter more than position for IT equipment. Shock, tilt, temperature, and humidity relate directly to whether hardware arrives functional, and they connect the packaging specification to evidence about whether it performed.
The limits are practical. Cellular-reporting devices lose coverage in tunnels, rural gaps, and steel containers. Battery life bounds the reporting interval over long transits. And tracking a vehicle is not tracking a carton — if the concern is an individual item, the device goes with the item.
Which Controls Does Each IT Shipment Need?
It depends on what is moving: data-bearing media justifies far more than standard hardware. Applying maximum controls to every shipment is expensive and trains people to treat the process as ceremony.
Standard IT equipment with no data on it needs seals on the trailer, a documented manifest, and reconciliation at delivery. Tracking at vehicle level is reasonable and sensor data is generally worth having for damage claims.
Equipment containing data-bearing media is a different risk. Media should ideally be removed and moved separately under dedicated drive transport controls, and where it cannot be removed, the shipment warrants barrier seals, item-level tracking, and in higher-sensitivity cases a continuously attended vehicle.
The highest-sensitivity movements — regulated data, cleared environments, irreplaceable systems — justify controls that cost real money: two-person integrity, escort vehicles, and a route plan agreed in advance, in line with the higher tiers of the TAPA security standards. These are decisions made on the value at risk, not on the value of the hardware.
Apply and Verify at Defined Points
Seals and trackers are only as good as the procedure around them, and the procedure is short enough to write on one page.
Seals go on at the point the container is closed and the contents have been verified, not earlier and not at the carrier's convenience. A seal applied to a container nobody checked certifies that an unknown quantity was not disturbed.
Two people should be present at application on high-value shipments — one to apply, one to witness and record. Single-person application means the record and the act have the same author, which is the condition that makes a record hard to rely on.
Trackers are activated and confirmed reporting before departure, not after. A device that turns out to be dead on arrival provides nothing, and the check takes seconds at the dock.
Where a shipment is opened legitimately in transit — customs inspection, a required transfer — the original seal number, the reason, the authority, and the replacement seal number all go into the record at the time. An unexplained seal change discovered at delivery is indistinguishable from tampering, and the cost of resolving it falls on whoever has to reconstruct events weeks later. This is one of the routine complications on international movements, where inspection is expected rather than exceptional.
The Control Is the Reconciliation
Seals and trackers generate data. The control is what happens to it, and this is where programs most often fail.
Someone has to compare the seal number at delivery against the number at origin, and that person needs the authority to refuse the shipment. A receiving process where the only option is to accept and note a discrepancy is not a control.
Discrepancies need a defined response before one occurs: who is notified, whether the shipment is quarantined rather than unpacked, who investigates, and what triggers treating it as a potential data breach. Deciding this during the incident produces the wrong answer, usually the convenient one.
Tracking alerts need an owner with a response path. Alerts routed to an unmonitored mailbox are a cost with no benefit, and they accumulate until someone disables them.
Retain the records. Seal logs, tracking histories, and sensor data are the evidence base for insurance claims and for demonstrating custody to an auditor. Retention should match the obligations on the data the equipment carried rather than a shipping department's default, and it should be long enough that a question raised years later can still be answered.