ot-security-awareness-training-planlisted

## When to Use - Designing OT security training for a new site or program. - Fixing a training program after a phishing or USB-borne incident. - Adding contractor and vendor training to an existing program. - Aligning training with an audit or certification requirement. ## Prerequisites - Role inventory: operators, control engineers, EWS users, contractors, executives, and their OT touchpoints. - Incident history: which behaviors caused or enabled past incidents. - Production schedule constraints that limit training windows. - Assessment capability: how comprehension will be measured. - Credentials: none. This skill produces design documents. - Authorization: operations manager accepts the time commitment per role. Training that competes with production time is an operations decision. - Upstream skills: `ot-incident-response-plan-review` for incident-derived topics. ### Safety This skill is passive. It produces assessment and governance documents only. ## Workflow 1. Define the role set from OT touchpoints. Requirement: topics match what each role can actually break or protect. Anchor: IEC 62443-2-1 4.3.2.4.3. Decision: roles are operators, control engineers, EWS users, contractors, and executives. Trade-off accepted: finer role granularity improves relevance and multiplies the content maintenance burden. A role with a distinct OT touchpoint gets its own topic set. 2. Topic decision per role. Requirement: every topic is one the role can act on. Anchor: AT-3. Decision: