Fencing, access control, cameras and staffing: what each layer stops, and which combination is proportionate for a container site.
Every site tour includes a walk past the fence line and a mention of cameras, and most visitors nod and move on to the row of machines they came to see. That is understandable, but the security layer deserves a slower look, because it is the part of the site you are trusting to keep your hardware where you left it between visits.
The layers, from the outside in
Physical security on a container or industrial site is not one control, it is several, stacked so that a failure in one layer does not mean the whole site is exposed. Fencing and the perimeter are the first layer, and their job is narrower than people assume: a fence does not stop a determined intruder, it stops casual access and buys time before the next layer engages. What matters is whether the perimeter is continuous, lit, and free of the kind of gaps that develop quietly at the back of a site where nobody walks.
Access control is the second layer, and it answers a different question: not who could get in, but who is allowed to, and whether that permission is checked at the point of entry rather than assumed. A gate that opens on a shared code everyone on site knows is a different control from one that logs each individual entry against a named person. Ask which one you are looking at, because the two look similar from the car park and behave very differently in practice.
Cameras are the third layer, and their value depends entirely on coverage and retention, not on whether they are visible. A camera pointed at the main gate tells you little about what happened at a container three rows back. Staffing is the fourth layer, and it is the one that turns the other three from passive recording into an active response: a camera that nobody is watching, or an alarm that nobody answers, is a layer that looks complete on a site tour and is not.
Access and visitor handling
Ask specifically how the site treats a visitor who is not staff: your own technician, a delivery driver, a broker walking a prospective customer through. Are visitors logged in and out, and is there a record of who they were with while on site? A site where visitors sign in at a desk but then move around unaccompanied is offering a paper trail rather than actual control over where people go once they are inside the fence.
The same question applies in reverse to your own access. If you need to get to your hardware outside a scheduled visit, what does that require, and is the answer written down anywhere rather than left to whoever happens to answer the phone that day?
Recording, retention and what happens after an incident
A camera system is only as useful as the footage that is still there when you need it. Ask how long recordings are kept, and whether that period is long enough to cover the gap between something going wrong and someone noticing. A retention window measured in a small number of days is common on cost-sensitive sites; know that number rather than assume footage will still exist by the time a query is raised.
A second question is what triggers a review of footage in the first place. Is it only pulled after a specific complaint, or does someone routinely check for anomalies such as a container door open outside scheduled hours? The difference is between security that reacts to what you report and security that notices on its own.
Alarms and the response path
An alarm that fires and reaches nobody is not a control, it is a sound. Ask what the alarm is connected to (an on-site guard, a remote monitoring service, a mobile alert to a named individual) and what happens between the alarm firing and someone physically responding. The gap between those two moments, more than the sophistication of the sensor itself, is what determines whether the alarm layer does anything useful.
Insurers who cover hosted hardware, or the site itself, generally want to see this response path documented rather than described verbally: who is alerted, on what timeline, and what their obligation is once alerted. If your own insurance, or the operator's, depends on a specific standard of site security, check it directly against what the site has rather than what the marketing page states in general terms.
What to look for on a visit
Checking this takes no specialist knowledge, only a slower walk around the site than most tours default to. A short list of what to look and ask for:
- Walk the full perimeter, not just the section near the entrance, and look for gaps, poor lighting or points where the fence backs onto unmonitored ground.
- Ask to see the visitor log, and ask whether visitors are escorted or left to move around unaccompanied.
- Ask how long camera footage is retained, and what prompts someone to review it.
- Ask what the alarm is connected to, and how quickly a physical response happens once it fires.
- Ask whether the layers are documented anywhere the site's insurer has seen, or only described informally on request.
A site that answers these questions specifically, with names, timelines and a document rather than a general assurance, is telling you the rules are lived rather than posted. A site that answers in generalities is telling you something too. Our operations page sets out the layers at our own facilities: a fenced perimeter, access control and CCTV, logged access with escorted visitors, and a team on site 24/7.
