1. Intro2. Challenges3. Roadmap4. Closing Thoughts
READ:
OT/ICS Fundamentals 08-SEPT-2026 · 12 min read

OT Shift Handover Security: The 15-Minute Gap

Shift handovers are the lowest-oversight transition in industrial operations, where verbal status transfers, shared logins, and unrecorded overrides can quietly erode control. This article explains where those gaps form, why they persist even at mature sites, and how plant leaders can sponsor practical handover controls without stalling production.

OT securityshift handovercontrol room operationsindustrial access controloperational governance
ManagerDevelopingPR.AA Identity Management & AuthSecurity Hardening
AI-Generated Locally
Article Details
CategoryOT/ICS Fundamentals
Published08-SEPT-2026
Read Time12 min read
AuthorNEXUS Engineering
Handover Sequence

What Actually Happens During a Control Room Handover

The typical handover is a sequence of informal steps that rarely appear in a procedure as a single controlled event. The outgoing operator briefs the incoming operator verbally, usually standing at the console, covering open work orders, abnormal equipment, alarms that have been shelved or suppressed, and any manual interventions in progress. The incoming operator confirms what they have heard, often by nodding or repeating key points, and then assumes responsibility. In many sites the console is never logged out. The outgoing operator simply steps away, the incoming operator sits down, and the session that was opened at the start of the previous shift continues under the same operator account. From the system's perspective nothing has changed, which is precisely the problem: the audit trail attributes every subsequent action to a person who may no longer be at the desk.

The second loss of control occurs at the HMI itself. Operator graphics are typically left on the screens that matter most to the process, such as overview displays, the active alarm summary and a specific loop faceplate with a setpoint being adjusted. Under ISA-101 principles these displays are designed for situational awareness, but they also carry the current state of the process without any evidence of who last touched them or why. Where a setpoint change is pending, a faceplate may show a value that the outgoing operator intended to revert and the incoming operator has no record of. Unrecorded manual overrides are the most consequential element. A bypass of a trip, a forced input, or a local hand-operated valve that was agreed verbally may exist only in the head of the person now leaving the room, and it is not reflected in the historian or in the alarm state until someone notices a deviation.

The result is a window of roughly fifteen minutes in which control authority, process knowledge and audit accountability are all ambiguous at once. IEC 62443-3-3 requires human user identification and authentication (SR 1.1) and auditable events (SR 2.8), yet a shared session satisfies neither in substance. The mechanism of failure is not that a hostile actor exploits the gap, though that is possible, but that any change made during the window, whether by error, fatigue or malice, cannot be reliably attributed or reversed with confidence. Texas City in 2005 illustrated how a transition under pressure, with an unreliable level indication and a crew working outside normal expectations, can convert an ordinary startup into a catastrophe. The handover did not cause that incident alone, but it was where the operating picture was least verified.

Failure Modes

Why Handover Controls Fail Under Production Pressure

Handover controls rarely fail because operators ignore them. They fail because the handover window is structurally hostile to verification. The outgoing operator wants to leave, the incoming operator is catching up on a plant state they did not build, and the time budget is set by rotation schedules rather than by the work that needs doing. The Chemical Safety Board's investigation of the 2005 BP Texas City isomerization unit incident is the reference case: the startup and the shift turnover overlapped, fatigue and staffing were contributing factors, and the operators on duty were working from an incomplete picture of tower level and alarm state. The four causes below recur at mature sites that otherwise run disciplined programmes.

critical

Shared and Persistent Console Sessions Across the Turnover

Where operators share a generic login or the outgoing session is left unlocked for the incoming operator to take over, the identity recorded against every setpoint change, acknowledgement and shelve action becomes meaningless. This directly defeats IEC 62443-3-3 SR 1.1 (human user identification and authentication) and weakens SR 2.1 (authorization enforcement), because privilege is attached to the console rather than to the person. Forensic reconstruction after a process deviation then cannot establish who held control at the moment it changed.

critical

Unverified Manual Overrides and Open Engineering State

Manual overrides, forced inputs, bypassed interlocks and temporarily changed setpoints are frequently carried across the shift as verbal items rather than as tracked, time-limited states. The incoming operator accepts the console as displayed, not as configured. Without an as-found comparison between the HMI presentation, the controller's actual values and the authorised change record, a stale override can persist for hours. Any attacker who manipulates a value during this window is indistinguishable from a legitimate but undocumented operator intervention.

high

Alarm Shelving and Suppression Left Active Through the Handover

Shelved and suppressed alarms are often justified for a single shift and then forgotten. ISA-18.2 and IEC 62682 require that shelving be time-limited, authorised and visible, but in practice the shelved list is reviewed in the outgoing briefing only if the outgoing operator remembers it. An incoming operator who does not see a suppressed high-level or high-pressure alarm has no reason to investigate its absence, and the alarm system appears healthy while a protection function is silently degraded.

high

Reliance on Tacit Knowledge and Informal Briefings

The verbal handover, typically conducted standing at the console, transfers context that no procedure captures: which valve is sticky, which instrument reads high after rain, which contractor is still in the field. Its quality depends on the individual and on the time available, and it is not auditable. Where the handover is not captured in a structured log, the incoming crew inherits assumptions rather than verified state, and the organisation has no evidence that the critical items were actually transferred.

Implementation Path

Hardening the Handover Without Stalling Production

▲

Sequence the changes so that each phase removes a failure mode the previous phase exposed. Do not start with metrics: dashboards built on unreliable handover records only measure the gap and do not close it.

Phase 1
Month 1-2

Baseline and Standardized Digital Handover Checklist

Establish what actually happens at the console today by observing and recording several real handovers per crew, including the verbal exchange, screen state, and any manual actions in progress. Replace the paper or free-text log with a structured digital checklist that captures active alarms and their acknowledgement state, shelved or suppressed alarms with their ISA-18.2 justification and expiry, out-of-service or bypassed interlocks, manual or local-mode overrides, pending work orders and MOC references, and open HMI faceplates or operator-initiated sequences. The checklist must be bounded to the minimum fields that operators will complete under time pressure, with mandatory fields for anything that changes the process state. Scope the first version to one unit or control room so the content can be validated against actual operating practice before it is rolled out site-wide.

Shadow and time at least three handovers per crewMap current log fields against ISA-18.2 alarm states and MOC recordsDefine mandatory versus optional checklist fieldsPilot checklist on one unit with supervisor sign-offAgree a retention period for handover records with the site records owner
Phase 2
Month 3-5

Verified State Confirmation and Individual Console Credentials

Introduce a two-party verification step in which the outgoing operator presents the process state and the incoming operator independently confirms key setpoints, alarm limits, and interlock status against the live DCS or SCADA view, not against the previous log entry. Prioritise safety-relevant and high-consequence parameters first. This is where the handover checklist stops being documentation and becomes a control. In parallel, remove shared operator logins at the console by enforcing individual authentication, mapped to IEC 62443-3-3 SR 1.1 (human user identification and authentication) and SR 2.1 (authorization enforcement), with role-based permissions that reflect the operator's qualification. Where legacy HMI platforms cannot support per-user accounts, document the compensating controls, such as session logging at the engineering workstation and physical access restriction, and record the residual risk formally under the site risk assessment process.

Define a verified-state list of setpointsalarm limitsand interlocks per unitImplement independent incoming-operator confirmation against live valuesConfigure individual accounts and role mapping for each consoleDocument compensating controls for legacy HMIs that cannot enforce individual loginLog authentication and override events as auditable records per IEC 62443-3-3 SR 2.8
Phase 3
Month 6-9

Handover Quality Metrics Reviewed by Plant Management

Move ownership of handover performance to plant management by defining a small set of leading indicators that can be audited, not just reported. Useful measures include the proportion of handovers with a completed checklist, the rate of verified-state exceptions raised at handover, the count of alarms shelved or overrides active at handover without a current justification, and the time from handover start to confirmed incoming acknowledgement. Review these monthly alongside production and safety metrics, and treat unexplained gaps as operational deviations requiring root cause analysis rather than individual performance issues. Feed the findings back into the checklist and training content, and include handover scenarios in tabletop exercises and operator refresher training so that the process remains effective after the initial rollout pressure has passed.

Define four to six auditable handover KPIs with owners and review cadenceAdd handover quality to the monthly plant performance reviewSet a deviation threshold that triggers root cause analysisInclude handover failure scenarios in tabletop exercisesUpdate checklist and training content from audit findings
Closing Thoughts

Who Owns the Gap Between Shifts?

The handover sits in an awkward organisational space. Operations treats it as a production-continuity task that must not cost throughput or delay the start of the next shift. HSE treats it as a procedural control under the PSM operating-procedure and management-of-change obligations in 29 CFR 1910.119(f) and (l), where the question is whether the procedure and its change pathway cover the transition itself. Cybersecurity treats it as a gap in access control and state management, with no one assigned to close it. IEC 62443-2-1 expects an asset owner to run a defined security programme with clear roles, personnel training and documented procedures, yet most sites can name no single owner for the console state at 06:45, the moment when the outgoing operator has left, the incoming operator is partially briefed, and an HMI session may still be logged in under someone else's credentials. The result is that each function can point to a control that exists on paper while the transition itself remains unowned. Before the next audit or incident, leadership has to decide whether the handover is an operational routine with security side-effects, or a security control that operations must execute and evidence. That choice determines who funds the checklist, who signs off the verified-state confirmation for setpoints, alarm limits and shelved alarms, who reviews the handover quality metrics, and who answers when an unrecorded manual override is found to have shaped a trip, a permissive bypass or an alarm shelving decision. The Chemical Safety Board's investigation of the 2005 Texas City isomerization unit explosion is instructive here: operator fatigue, extended hours and the shift-change period were among the contributing conditions examined, and the lesson for leadership is that a transition that is treated as routine tends to be governed by whatever is most convenient at the time it occurs.

01

If an unrecorded manual override set during a handover contributed to a process upset, is the accountable owner the outgoing operator, the incoming operator, the shift supervisor, or the manager who set the staffing pattern and the handover time budget?

02

Does your site's management-of-change process explicitly cover changes made during shift transitions, including temporary overrides, alarm shelving and bypasses, or does it only capture changes made during planned work and maintenance windows?

03

Where in your organisation is the handover written as a control with a named owner, defined evidence and a verification step, and where is it only described as a practice that people are expected to follow when time allows?

04

If a handover failure were the root cause in an incident review, would your leadership team accept a systemic finding covering staffing, timing, access design and procedure, or would the finding be reframed as an individual performance issue that closes the investigation at the operator level?

A control that no one owns will be executed by whoever is most rushed at the moment it matters.
← Back to CyberCuriosity Let's Talk
Comments & Suggestions
Thoughts on this article? Corrections, questions, or additions — all welcome.
★ ★ ★ ★ ★ Optional — tap to rate
GDPR: Your data is processed solely to respond to your enquiry and is never shared with third parties. By submitting you consent to NEXUS Cybersecurity storing your details for this purpose only.
Sent privately — never published publicly