Your Maintenance Contractor Manages OT. Who Owns Cybersecurity?
Ask who is accountable for the cybersecurity of a control system that a maintenance contractor operates and a vendor supports, and you usually get three answers that do not add up to one. The asset owner assumes the contractor handles it because the contractor touches the equipment. The contractor assumes the asset owner handles it because the asset owner owns the plant. The OEM assumes someone raised a support ticket if anything mattered.
Nobody is being evasive. The gap is structural: maintenance contracts are written around availability and response time, and cybersecurity was not a line item when most of them were signed. The result is a control system that three organizations touch and none governs. This article is about closing that gap, which is a contracting exercise before it is a technical one.
Three parties, three different interests
|
Party |
What they are actually optimizing for |
|
Asset owner |
Production and safety. Carries the regulatory exposure and the consequence of an incident, but often has the least day-to-day visibility of the system. |
|
Maintenance contractor |
Uptime and response time, because that is what the contract measures and pays for. Security work that slows a callout is a cost to them, not a benefit. |
|
OEM or integrator |
Supportability. Standard configurations and remote access make support cheaper and faster, which is why both tend to be permissive by default. |
None of these incentives is wrong. They are simply not aligned to security outcomes, and no amount of goodwill fixes a contract that rewards something else.
|
The question that settles it Who is accountable if an unauthorized change is made to this controller, and who would know? If the answer involves more than one organization pointing at another, you have found the gap. Ask it per system rather than in general, because the answer is often different for a packaged skid, a plant-wide DCS and a remote pump station, and the organizations involved differ too. |
What to split, and how
Accountability cannot be delegated, but activity can. The workable split assigns each activity an owner and keeps accountability with the asset owner throughout.
|
Activity |
Usually performed by |
Accountable |
|
Asset inventory for the system |
Contractor or integrator |
Asset owner. You cannot outsource knowing what you have. |
|
Patching and firmware |
Contractor or OEM |
Asset owner approves; contractor executes to an agreed window. |
|
Backup of logic and configuration |
Contractor |
Asset owner holds a copy. A backup only the contractor has is not your backup. |
|
Remote access |
OEM or contractor uses it |
Asset owner grants, logs and revokes it. |
|
Change control |
Contractor raises |
Asset owner approves, including the security review. |
|
Incident detection and reporting |
Whoever notices |
Asset owner. The contractor must be contractually obliged to report. |
Two rows deserve emphasis. A backup held only by the contractor is a dependency, not a control, and we find it constantly: the only copy of the PLC logic sits on an engineer's laptop at a firm you have a commercial relationship with rather than a custodial one. And the obligation to report an incident has to be written down, because a contractor who discovers a problem they may have caused has an obvious reason not to volunteer it.
Contract language that actually works
- A named security contact on both sides. Not a shared inbox. A person who can be reached during an incident.
- An obligation to report suspected security events, with a deadline. Hours, not "promptly". Align it to any regulatory clock you are subject to.
- Named individual accounts, no shared credentials. If you cannot attribute an action to a person, you cannot investigate it.
- A right to audit the contractor's access and practices. Rarely exercised, and its existence changes behavior.
- Handover of configuration and logic on request and at contract end. The moment a contract ends is the moment this becomes difficult and the moment you most need it.
- Security requirements in the scope of work, not an annex. An annex nobody reads is not a requirement.
For equipment being purchased rather than maintained, the same logic applies earlier, at specification. Our guide to what to ask vendors about SBOM and supply chain covers the procurement side.
Where IEC 62443 helps
The IEC 62443 series is explicitly built around different roles: asset owner, service provider and product supplier each have their own requirements. That structure is useful here because it gives you a shared vocabulary that is not your vocabulary or the contractor's, and a neutral reference for what each party is expected to do. Operators who frame the conversation as "here is what the standard expects of a service provider" get further than those who frame it as a new demand.
Start with a RACI you can actually produce
One page, one system, four columns: activity, who performs it, who approves it, who is accountable. Fill it in with the contractor in the room rather than sending it to them. The disagreements that surface during that hour are the actual findings, and they are cheaper to resolve across a table than during an incident. Repeat per system class rather than once for the whole plant, because the answers genuinely differ. Our OT asset inventory and device management guide covers establishing what systems you are splitting responsibility for.
Why Choose Arista Cyber
We run these sessions with asset owners and their contractors together, which is uncomfortable for an hour and considerably cheaper than discovering the gap during an incident. Our consultants hold functional safety credentials alongside OT security certification, so where a maintenance activity touches a protective function we can assess both consequences. See our OT cybersecurity services and our case studies.
Next Steps
Pick your most contractor-dependent system and answer the question in the box above. If more than one organization points at another, run the RACI exercise before you touch the contract, because you cannot write the clause until you know what you are assigning.
Common Questions
Can we transfer cybersecurity responsibility to our maintenance contractor?
You can transfer the activity. You cannot transfer accountability, because the regulatory exposure and the operational consequence stay with the asset owner. Contracts should assign who performs each task while keeping accountability explicit.
Our contractor holds the only backup of our PLC logic. Is that a problem?
Yes. A backup you cannot access on demand is a commercial dependency rather than a control. Require handover of configuration and logic on request and at contract end, and hold your own copy.
What is the single most important contract clause to add?
An obligation to report suspected security events within a defined number of hours, to a named contact. Without it, a contractor who discovers a problem they may have caused has every reason not to raise it.
How does IEC 62443 help with contractor responsibility?
The series separates requirements for asset owners, service providers and product suppliers. That gives all three parties a neutral shared reference for what each is expected to do, which moves the conversation off opinion.
Should we do one RACI for the whole plant?
No. Do one per system class. A packaged skid, a plant-wide control system and a remote site involve different organizations and different answers, and a single plant-level RACI hides exactly the gaps you are looking for.
|
Not sure who is accountable for your contractor-managed systems? Arista Cyber facilitates responsibility mapping between asset owners, maintenance contractors and OEMs, then translates the outcome into contract language you can actually enforce. |
Facing tougher cyber security challenges?
Talk to Arista Cyber about your OT security posture.
Request a consultation