Skip to content
cyberhux

Why remote sites are the soft underbelly of African energy firms

Mines, substations and depots often sit outside head-office security routines. A practical guide to finding and closing the physical and digital gaps.

10 min readcyberhux research team
In this article

Why remote sites develop different controls

Remote energy and mining locations operate under pressures that head-office policies do not always reflect. Sites may be widely dispersed, dependent on contractors and focused on keeping essential services running. Limited connectivity, long supply chains and shared facilities can make standard controls difficult to apply consistently.

Attackers benefit from those differences. A cabinet installed during an urgent repair, a badge shared during a shift change or a temporary vendor connection can remain long after its original purpose. The issue is rarely a lack of policy alone; it is the gap between the policy and the site's daily reality.

Map physical entry routes beyond the front gate

A site assessment should include reception, vehicle gates, workshops, warehouses, equipment yards, communications rooms and temporary structures. Roof access, delivery routes and adjacent public spaces may also matter. The objective is to understand where an unauthorised person could plausibly go and what they could reach from there.

Pay attention to the controls between areas, not only the perimeter. Someone with legitimate access to a workshop should not automatically be able to enter a network room or operations area. Visitor escorts, contractor supervision and delivery procedures should be observed in practice because written procedures may differ from what busy teams can sustain.

  • Check doors, locks, fencing, lighting and camera coverage in operational conditions.
  • Look for shared badges, propped doors, untracked keys and informal tailgating.
  • Inspect network cabinets, exposed cabling and unattended communications equipment.
  • Review how alarms are handled when connectivity or staffing is limited.

Test the path from physical access to digital impact

An unlocked cabinet is a physical weakness, but its significance depends on what an attacker can do next. Open switch ports, accessible console connections, unmanaged devices and flat networks can turn a brief visit into wider network access. Conversely, strong segmentation and port controls can sharply limit the opportunity.

Authorised testing should follow these paths carefully and stop before any action that could affect safety or operations. The goal is to demonstrate realistic impact, not to interfere with industrial processes. IT, operational technology, facilities and safety teams should agree the test boundaries and emergency contacts in advance.

  • Disable unused network ports and control which devices may join site networks.
  • Separate visitor, corporate, operational and building-management networks.
  • Protect administrative interfaces and remove default or shared device credentials.
  • Monitor new devices and unexpected connections at remote locations.

Control contractor and maintenance access

Specialist vendors often need temporary physical or remote access to maintain equipment. Problems arise when that access is always on, shared between individuals or broader than the job requires. A maintenance account created for one visit can otherwise become a permanent route into the environment.

Tie access to a named person, approved task and defined time window. Require stronger authentication for remote sessions and record administrative activity where practical. At the end of the work, local staff should be able to confirm that credentials were disabled, temporary firewall rules removed and replaced equipment handled securely.

Prepare for limited connectivity and delayed support

Remote sites may not be able to wait for a central response team. Local personnel need a short playbook covering who to call, how to isolate a suspicious device safely and which evidence to preserve. Instructions should distinguish cyber response from actions that could interrupt essential operations.

Test communications during degraded conditions. If the usual network is unavailable, can the site still reach the security team? Are contact details available offline? Can central teams see enough telemetry to understand the event? Short tabletop exercises can reveal these dependencies without disrupting operations.

A practical 90-day improvement plan

Start with a small number of representative sites: a high-risk location, a typical location and one with known operational constraints. Combine interviews, physical observation and non-disruptive technical review. Use the results to identify systemic fixes that can be replicated rather than producing a separate list of isolated repairs for every site.

Prioritise actions that reduce the largest attack paths first: secure network equipment, remove unnecessary remote access, segment critical systems and establish reliable visitor and contractor controls. Then schedule authorised validation to confirm that the changes work under real site conditions.

  • Days 1–30: map sites, access paths, critical dependencies and existing exceptions.
  • Days 31–60: address exposed equipment, shared access and high-risk network routes.
  • Days 61–90: validate controls and rehearse a site-level response scenario.
  • Ongoing: include representative remote sites in every broader assessment programme.