iec-62443-certification-readinesslisted

## When to Use - Planning certification for a product, component, system, or service. - Responding to a customer requirement for a 62443 certificate. - Preparing for a pre-assessment with a certification body. - Deciding which parts to certify first. ## Prerequisites - Product, component, or system definition with version and boundaries. - Existing process documentation: development lifecycle, service delivery, incident handling. - Zone and conduit design from `ot-network-segmentation-design` for system-level work. - Component inventory with any existing certificates and their scope. - Credentials: none. This skill produces assessment documents. - Authorization: product management and security management accept the readiness decision and its cost. - Upstream skills: `ot-network-segmentation-design` for 3-3 scope, `conduit-security-design` for system requirement evidence. ### Safety This skill is passive. It produces assessment and governance documents only. ## Workflow 1. Define the certification scope precisely. Requirement: scope names the part, the target, and the version. Anchor: 62443-2-4, 62443-3-3, 62443-4-1, and 62443-4-2 as applicable. Decision: one scope statement per part, each naming the audited entity: the development process for 4-1, the component and its version for 4-2, the system and its zone boundary for 3-3, and the service delivery process for 2-4. Trade-off accepted: a narrow scope costs less and is faster, and it may not satisfy a customer whose r