Plan an operational technology (OT) cybersecurity project
A work breakdown structure for securing industrial control systems, built around safety, uptime, and OT security standards.
The prompt
Help me plan an OT (operational technology) cybersecurity project.
Facility type: [e.g. manufacturing plant, utility, water treatment, oil and gas, building automation]
Systems in scope: [PLCs, SCADA, DCS, HMIs, historians, remote access, IT/OT network links]
Project goal: [e.g. asset inventory and segmentation, secure remote access, compliance with a standard, incident response readiness]
Standards or regulations: [e.g. IEC 62443, NIST SP 800-82, NERC CIP, local critical-infrastructure rules]
Constraints: [maintenance windows, legacy systems that can't be patched, vendor support contracts, staff]
Timeline and team: [DURATION, roles available]
Create:
1. A work breakdown structure (numbered to three levels) covering initiation, asset discovery and inventory, risk assessment, zone-and-conduit or segmentation design, remote-access and identity controls, monitoring and detection, patch and vulnerability management for legacy systems, backup and recovery, incident response with operations, training, testing and commissioning, and handover.
2. For each work package: deliverable, owner role, dependencies, and whether it needs a plant shutdown or maintenance window.
3. OT-specific risks and mitigations: safety impact, unplanned downtime, active scanning disrupting fragile devices, vendor warranty conditions, IT/OT team friction.
4. A milestone timeline aligned to my maintenance windows.
5. Success measures (e.g. percent of assets inventoried, segmented zones, remote sessions under control).
Always prioritize safety and process availability: flag any task that should be tested offline first and approved by operations and the control system vendor. Mark requirements you're unsure apply to my sector as [CONFIRM].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- DURATION, roles available
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Build a punch list and closeout plan to finish the jobAn organized punch list by area and trade plus a closeout checklist for documents, inspections, and final payment.
- Run a community health needs assessmentA step-by-step plan to assess a population's health needs, set priorities, and turn findings into a program and evaluation plan.
- Write a procurement category strategyA sourcing plan for a spend category: market, needs, options, and roadmap.