Skip to main content
OT/ICS Cybersecurity

The OT Incident Plan Nobody Signed: Get a Sponsor and a One-Page Charter First

Whose signature is on your OT incident response plan, and could that person order a shutdown? A plan's authority comes from its sponsor, not its author. The one-page charter in full, the four decisions only a sponsor can make, and how to ask for the signature in twenty minutes.

Cinematic dim control room: a clipboard with a blank page and an empty signature line lies beside a pen on a steel desk, an empty chair facing lit control panels and plant equipment behind it

Whose signature is on your OT incident response plan, and could that person order the control room to shut down for a cyber reason? If you have to open the file to check, or the answer is "my manager, who runs IT", the plan has a problem no amount of good writing will fix.

Plans are written by people who know the systems. They are obeyed because someone with authority signed them. Those are rarely the same person, and the gap between them only shows on the night it matters.

Someone always has to hold that authority. When a cyber incident was found at the water treatment plant in Arkansas City, Kansas, in September 2024, the city switched the plant to manual operations "out of caution" and reported no disruption to service. That is a decision with a cost, made fast. Somebody had to be allowed to make it, and it is far easier when the paper already says who.

This is for the manager, OT lead or engineer who has been told to "write the incident plan" and has not yet been told who will stand behind it. If your plan already carries a sponsor's signature from someone who can bind operations, the charter below is still worth a look for its decisions box. Otherwise, read on before you type the first heading.

The guidance has said this for a while. NIST SP 800-61r3 starts its incident response policy elements with a statement of management commitment, and then the roles with authority to confiscate, disconnect or shut down systems (section 2.3). And plenty of sites are still at the start: in the SANS 2025 survey, as reported by Industrial Cyber, 57% of respondents had an incident response plan written specifically for ICS/OT. Many of the rest are about to write one. This is the moment to get the order right.

The one-page charter, before the plan

Three documents get confused. The policy is standing authority: management's commitment, and who may disconnect or shut down. The charter is a time-boxed work order for the project that writes the plan. The plan is the finished job. You need the charter first, because it is the page the sponsor signs before anyone spends a month drafting.

Item 11 is the one that earns the charter its place. Every question in that box is one a draft plan quietly leaves for "the incident". Listed, dated and owned, they get decided in a meeting room instead of on a phone call at 02:00.

Item 4 deserves one example. "Improve incident readiness" cannot be checked. "Plan approved by 30 June; every shift supervisor briefed by 31 July; every number in the contact register called and confirmed" can be. A sponsor can only say the project is finished if the objectives say what finished looks like.

Is there a box on your current plan where those four decisions are recorded? If yes, check the dates. If no, you have found your first page.

"Our plan is approved. My manager signed it"

"We have an incident response plan. My manager approved it last year. It's on the intranet. I don't need a charter to tell me that."

Run one test on that signature: can the person who signed it bind operations, or only IT? A plan approved by the author's own manager in the IT or security chain is, to the control room, a document from another department. The shift supervisor reads "isolate the cell" and asks who said so. If the honest answer is "someone who doesn't run the plant", the step waits for a phone call.

For a site plan the sponsor is usually the plant or site manager. For an enterprise plan it is an executive who can commit operations: a COO, a VP of operations, sometimes a CISO with that mandate in writing. The standard most OT programmes follow says the same thing in general terms: Part 2-1 of the ISA/IEC 62443 series, 2024 edition, treats commitment from the top of the organisation down as essential to the security programme (clause 4.1.2.2; it is a paid document, so this is a paraphrase).

"I can't walk into the GM's office and ask for authority"

"I'm a controls engineer. I fix PLCs. I'm not going to march into the general manager's office and ask to be given authority over the plant."

Good, because that is not the request. You are not asking for authority for yourself. You are asking the person who already holds it to write it down. That is a much easier meeting, and it fits in twenty minutes if you bring three things:

  • The decisions box, with its four rows. Put the shutdown question first. Most site managers have an opinion on it, and few have ever been asked to sign it.
  • The time you are asking for, in hours. Your own share, a few hours a week from a handful of people, and a few hours of the sponsor's own time across the whole project. Make the numbers yours and say they are estimates.
  • One line on why it cannot be signed lower down, taken from the rules that apply to your site (next section).

Then ask for a decision, not for support. "Will you sponsor this, and can you decide these four by the end of next quarter?" Support costs the manager nothing and gives you nothing. A signature with dates gives you a plan that will hold.

"Corporate owns incident response"

"Incident response belongs to the CISO. Corporate has a plan for the whole company. They're not going to let one site write its own and sign it locally."

Nobody has to pick a side. Split two things that usually get argued as one: accountability for the plan, and authority inside the plan. The sponsor and the plan owner are accountable for the OT plan being right and approved. The enterprise incident response owner, often the CISO's team, signs for how the OT plan sits inside the company plan. Operations keeps the final say over process actions, because nobody at headquarters can see a tank level. That is why the charter has four signatures rather than one.

The rules in several jurisdictions point the same way, at management approval:

  • In the EU, NIS2 Article 20(1) requires management bodies to approve the cybersecurity risk-management measures, oversee them, and answer for them.
  • For North American electric utilities, NERC CIP-003 has the CIP Senior Manager approve the documented cyber security policies, which cover incident response.
  • In Australia, the SOCI Act requires the annual risk management program report to be approved by the board, where there is one (section 30AG).

None of them was written for one site's plan, and none of them says "charter". What they share is the idea that approval sits with management, not with the person who wrote the document.

Where the authority comes from

Back to the opening question. With a charter in place, the answer to "whose signature, and could they order a shutdown?" is a name and a yes, or a dated line in the decisions box that will produce one. Either is better than finding out at the first incident that the plan was one person's well-written opinion.

Write the work order before the job. The plan will be shorter to argue about and much harder to ignore.

Sources: SecurityWeek, Kansas water facility switches to manual operations (24 Sep 2024) | NIST SP 800-61r3 | SANS 2025 survey, as reported by Industrial Cyber | ISA/IEC 62443-2-1, 2024 edition, clause 4.1.2.2 (paid standard) | NIS2 Directive (EU) 2022/2555 | NERC CIP-003-9 | Security of Critical Infrastructure Act 2018

ICS/OT Incident Response Plan: Write One That Works

Most OT incident response plans fail before anyone writes a word: no sponsor, no charter, no agreement on who decides. This workshop course takes you from a blank page to a plan your site approves and your operators can follow.

Each of the eight sections writes one chapter of your plan: the authority and scope, the inputs, severity in the language of the plant, command and decision rights, response steps, recovery and the readiness library.

You get the plan template, more than 40 templates and worksheets, 21 worked examples and a capstone with a full model answer.

50 videos, 7.7 hours. US$147 one-time through HKSM Courses. 30-day money-back guarantee when 50% or less consumed.

Explore the Course


ICS/OT Incident Response Plan course preview

Write the OT incident plan your site will actually use

Go from a blank page to an approved, usable plan for your industrial site, one chapter at a time. ICS/OT Incident Response Plan: Write One That Works includes 50 videos, the plan template, worksheets and a full model answer, delivered through HKSM Courses for US$147 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course