A failed sensor, an unavailable access-control system or an altered production setting may look like a technical fault. In a connected workplace, however, the cause could be a cyber incident, and the consequences may quickly move beyond lost data.
Digital systems now help organisations control machinery, monitor equipment, manage buildings, communicate during emergencies and protect lone workers. While this connectivity can improve safety and efficiency, it also creates dependencies. If a critical system is compromised, the result could be unreliable information, operational downtime, environmental damage or physical harm.
Cyber security should therefore form part of health, safety and business-continuity planning rather than remain solely an IT responsibility.
When cyber risk becomes safety risk
Traditional cyber security focuses on protecting the confidentiality, integrity and availability of information. Operational technology has different priorities: safety, reliability and availability often come first because system failure or malfunction can create physical danger.
The UK Health and Safety Executive warns that programmable industrial control systems can be vulnerable to cyber threats capable of causing undetected faults, failure and downtime, potentially increasing the risk of a major accident.
A cyber incident could affect:
- Machinery controls and emergency stops
- Fire alarms and evacuation systems
- Access control, lifts and ventilation
- Temperature, pressure and gas monitoring
- Lone-worker alarms and location tools
- Digital maintenance and permit-to-work systems
- Emergency communication channels
These risks are not limited to factories or critical infrastructure. Offices, warehouses, hospitals, construction sites and transport operations also depend on connected technology to maintain safe conditions.
Understand hidden dependencies
Connected systems rarely work alone. A safety application may depend on sensors, wireless networks, cloud platforms, identity services and third-party dashboards. Failure in one component can affect the wider system.
For example, an air-quality sensor may appear operational after a cyber intrusion while sending delayed or altered readings. Employees could continue working because the dashboard shows normal conditions even though the environment has become unsafe.
Organisations therefore need an accurate record of their operational technology, including connected devices, software, external links, suppliers and system dependencies. The National Cyber Security Centre recommends maintaining a definitive view of these components rather than treating an asset inventory as a static list.
Every review should answer four questions:
- What is connected? Identify equipment, sensors, applications and supporting infrastructure.
- Why does it matter? Record the operational or safety function of each asset.
- Who can access it? Include employees, contractors and external suppliers.
- What happens if it fails? Consider unavailable, delayed and inaccurate information.
Common routes to disruption
Cyber risk does not always begin with a highly targeted attack. Everyday weaknesses can provide access to safety-critical environments.
Weak remote access
Engineers and suppliers may need remote access to diagnose systems, but shared credentials and permanently open connections increase exposure. Access should be limited by user, system and time, protected by strong authentication, and logged for review. A properly configured remote access VPN may provide one layer of protection, but it should not replace network separation, identity controls, monitoring or approval procedures.
Outdated equipment
Operational devices often remain in service longer than office computers. Some cannot be patched without interrupting production, while others rely on unsupported software. Where updates cannot be applied promptly, organisations should use compensating controls such as isolation, restricted access and closer monitoring.
Poor network separation
If office and operational systems are closely connected, malware introduced through email or a compromised account may spread towards equipment supporting physical processes. Network segmentation limits movement and helps contain disruption.
Uncontrolled third-party access
Technology suppliers and maintenance partners may hold legitimate access but follow different security standards. Organisations should know who can connect, what permissions they have and how quickly access can be withdrawn.
Compromised credentials can create another route into these systems, so checking whether work related accounts have appeared in known breaches can provide an additional warning sign. An overview of the best free dark web scan tools outlines several ways to carry out an initial exposure check.
Protecting employee privacy
Connected safety tools may collect sensitive information. Wearables can record location, movement, fatigue indicators or health-related data, while cameras and access systems can build a detailed picture of an employee’s working day.
Collecting more data does not automatically make a workplace safer. Excessive or poorly explained monitoring may damage trust and discourage employees from supporting safety initiatives.
The Information Commissioner’s Office states that workplace monitoring must be lawful and fair. Employers should establish a clear purpose, consider whether monitoring is necessary and proportionate, limit access, define retention periods and apply appropriate safeguards.
Before introducing monitoring technology, organisations should ask:
- What safety problem will this system solve?
- Could the objective be achieved with less intrusive data?
- Who will access the information?
- How long will it be retained?
- Could it later be used for another purpose?
- How will employees be informed and consulted?
Building shared responsibility
Cyber-related safety cannot be managed effectively in silos. IT teams understand networks but may not recognise the physical consequences of failure. HSE professionals understand workplace hazards but may not know how a digital compromise could trigger them.
A joined-up review should involve health and safety, IT, engineering, operations, facilities, data protection, procurement and business-continuity teams. For each critical system, they should consider:
- Loss of availability: What happens if the system stops working?
- Loss of integrity: What happens if it provides false information?
- Loss of control: What happens if an unauthorised user changes its behaviour?
Integrity is especially important. A system that fails visibly may trigger a safe shutdown; one that continues operating with false readings can create a less obvious and more dangerous situation.
Practical protective measures
No single product can remove cyber risk. Safer connected workplaces use several layers of protection:
- Maintain an asset inventory: Record devices, software, owners, dependencies and external connections, then update it whenever systems change.
- Separate critical networks: Keep office, guest, building-management and operational systems appropriately segmented, and avoid exposing safety-related technology directly to the internet.
- Strengthen access controls: Use individual accounts, least-privilege permissions and multi-factor authentication where supported.
- Manage vulnerabilities: Apply supported updates according to risk and document temporary safeguards where immediate patching is impractical.
- Monitor unusual activity: Look for unexpected devices, login attempts, communication paths and configuration changes.
- Preserve manual options: Test safe shutdowns, emergency controls, standby systems and alternative communication routes.
- Buy securely: Assess authentication, logging, updates, secure defaults and supplier support before purchasing connected equipment.
Prepare for disruption
A cyber incident plan must address operational and safety consequences, not only computer recovery. It should define who can stop work, isolate equipment, contact emergency services and approve the return of restored systems.
Incident response, business continuity and disaster recovery perform different functions. Incident response contains the threat, continuity arrangements keep essential work running, and recovery plans restore systems safely. The NCSC recommends setting responsibilities, decision-making authority and communication routes in advance and exercising them regularly.
Backups should also be protected against ransomware and tested through restoration exercises. Recovery planning must cover applications, identity services and system configurations not only files
Employees remain central to resilience. They are often the first to notice an unexpected alarm, unusual control behaviour or incorrect reading. Reporting procedures should be simple and blame-free, and staff should know when to stop work rather than attempt to troubleshoot.
Conclusion
Connected technology can make workplaces safer and more efficient, but every connection introduces a dependency that must be understood. Organisations should design systems on the assumption that faults, mistakes and cyberattacks may occur.
By identifying connected assets, limiting unnecessary access, protecting employee data, testing recovery plans and preserving safe manual alternatives, businesses can reduce the chance of digital disruption causing physical harm. Wherever technology failure could affect health or safety, cyber security must be treated as a shared operational responsibility not simply an IT concern.
Frequently Asked Questions
How can a cyberattack create a workplace safety risk?
A cyberattack can interrupt or manipulate connected systems that control machinery, monitor hazardous conditions, manage building access or support emergency communications. In operational environments, this disruption can contribute to unsafe conditions, equipment failure or physical harm.
Which workplace systems are most vulnerable?
Any connected system may be exposed, but organisations should prioritise equipment whose failure could affect people, operations or the environment. This may include industrial controls, safety sensors, building-management systems, access controls, lone-worker devices and emergency communication tools.
Who should manage cyber-related safety risks?
Responsibility should be shared across health and safety, IT, cyber security, engineering, facilities, operations, procurement and business-continuity teams. This joined-up approach combines technical knowledge with an understanding of physical hazards and operational consequences.
How often should organisations test their response plans?
Plans should be reviewed whenever important systems, suppliers, risks or responsibilities change and exercised regularly. Testing should cover incident escalation, alternative communications, manual controls, backup restoration and the safe return of affected systems.
About the author
David Foy: Head of Content at HSE Network
David leads the content delivery team at HSE Network and handles the day-to-day management of advertorial and editorial content campaigns. David has experience in safety content creation across written and podcast-based mediums and has been working with HSE Network for over 5 years.
