iec-62443-gap-assessmentlisted

## When to Use - Preparing a gap register for a zone before remediation planning. - Responding to a request for a 62443-3-3 baseline. - Pre-audit preparation against an integrator checklist. - Feeding the zone and conduit audit with documented evidence. ## Prerequisites - Zone list and membership from `purdue-model-zone-conduit-audit`, or an equivalent zone map. - Evidence pack: network diagrams, firewall rule sets, account lists, backup records, monitoring reports. - Interview time with the zone owner and the control engineer. One hour per zone typical. - Credentials: none. - Authorization: site security manager sign-off to collect evidence. - Upstream skills: `purdue-model-zone-conduit-audit` for zone scope. ### Safety This skill is passive by default. Active steps are gated in the Workflow section. - Passive. Document and questionnaire review. Sends no packets. Safe to run during normal operations. ## Workflow 1. Load the zone list and the evidence pack. Confirm every zone has a named owner. 2. Open `references/questionnaire.md`. Complete one question block per SR for each zone. 3. Record three fields per answer in `gap-register.md`: current state, target state, and the evidence artifact that proves the current state. Answers without evidence are gaps. 4. Decision point: an answer of partial with an evidence artifact is still a gap. Downgrade every partial to a gap until the evidence shows the full control in place. 5. Classify severity: High where a gap crosses a