Safeguard
Security Guides•

How to run a manual operation drill for OT after a cyber incident

Manual operation is a primary OT mitigation. A step by step drill plan: map dependencies, name roles, run it safely, and record what slowed you down.

Safeguard Security Team
3 min read

To run a manual operation drill, pick one process, list the IT and OT systems it depends on, simulate losing them, run the process using the manual procedures, and record what slowed you down. CISA lists practising manual operation among its five primary OT mitigations.

Why it is on the shortlist

The May 2025 joint guidance says the ability to operate manually is vital for restoring operations quickly after an incident, and asks owners to regularly test business continuity and disaster recovery plans, fail safe mechanisms, islanding capabilities, software backups and standby systems. The Volt Typhoon and DarkSide advisories repeat the point: identify IT and OT interdependencies, develop workarounds, and test manual controls.

Before the drill

  1. Choose a scope. One line, one unit or one site area. Start small.
  2. Map dependencies. For that process, list what it needs: identity services, time, historian, recipes, licences, remote support.
  3. Write the manual procedure. If one does not exist, writing it is the first finding.
  4. Name roles. Who decides to isolate, who runs the process, who talks to management.
  5. Set stop conditions. Agree in advance what ends the drill if safety is in doubt.

Running it

  • Start in a planned window with operations leadership present.
  • Simulate the loss, for example by treating the supervisory system as unavailable.
  • Keep the real safety systems and procedures in place throughout. The drill tests manual control, not removal of protections.
  • Use only the written procedure. When someone improvises, note it.
  • Time key steps, such as isolating networks and restarting from backups.

After the drill

Hold a short review the same day:

  • What was missing from the procedure?
  • Which dependency surprised you?
  • Could the crew hold this for hours, not minutes?
  • Were backups of controller logic available and current?
  • What decisions waited for someone not in the room?

Turn answers into tracked actions with owners and dates. Repeat on a schedule, and rotate the process you test.

Link it to isolation

The agencies also stress the ability to isolate ICS networks. Include a step in the drill where you cut the IT to OT conduit and confirm that operations continue on the local network.

Keep the findings visible

Share a one page summary with operations, IT and management after each drill. When leadership sees that a missing printed procedure delayed recovery, funding for fixes tends to follow more easily than it does for abstract risk.

Quick check

Does a drill mean switching off safety systems?

No. Safety systems stay active. The drill tests running the process without supervisory or IT services.

How often should we run one?

CISA says to test regularly without giving a fixed interval. Choose one your operations team can sustain and run it at least after major changes.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.