ISA/IEC 62443 Lead Implementer Training — Lesson 2: Risk, Threats, Vulnerabilities, Security Levels, and Requirements

Learning Objectives

• Interpret the principles, requirements, roles, and dependencies shaping risk, threats, vulnerabilities, security levels, and requirements.
• Apply the workflow and produce IACS risk and security-requirement register that another practitioner can review.
• Analyze “a security level is selected without analysing process consequences” and recommend a proportionate, supported response.

Detailed Topics

• industrial risk assessment
• threat scenarios
• vulnerability analysis
• consequence analysis
• target security levels
• security requirements
• risk treatment
• design assumptions
• Competence, communication, governance, documented information, risk, validation, and follow-up considerations

Instructor Demonstration

The instructor demonstrates the risk, threats, vulnerabilities, security levels, and requirements workflow, identifies the applicable inputs and responsibilities, records checkpoints in IACS risk and security-requirement register, and contrasts the accepted state with a condition where a security level is selected without analysing process consequences.

Hands-On Exercise

Complete a controlled implementation, audit, assessment, or foundation exercise for Risk, Threats, Vulnerabilities, Security Levels, and Requirements. Establish scope and criteria, collect or create evidence, examine “a security level is selected without analysing process consequences,” reach a supported conclusion, and preserve the result in IACS risk and security-requirement register.

1. Confirm objectives, scope, roles, criteria, stakeholders, and expected outputs.
2. Perform the planned activities while recording assumptions, evidence, and decisions.
3. Test a normal case, an exception, and a follow-up or improvement condition.
4. Document conclusions, owners, due dates, escalation, and verification requirements.

Scenario Analysis

• Identify the requirement or principle with the strongest influence on risk, threats, vulnerabilities, security levels, and requirements.
• Compare two defensible responses and explain their governance, risk, and evidence trade-offs.
• Determine how IACS risk and security-requirement register should be approved, retained, reviewed, and updated.

Troubleshooting Guidance

Separate missing evidence from ineffective practice, and distinguish a documentation issue from a control, process, governance, or competence failure. Use IACS risk and security-requirement register to trace the earliest divergence. Treat “a security level is selected without analysing process consequences” as a hypothesis until the response is validated against the applicable requirement and intended outcome.

Validation Checklist

• The scope, criteria, stakeholders, and intended outcome for risk, threats, vulnerabilities, security levels, and requirements are explicit.
• The IACS risk and security-requirement register links statements and decisions to objective, reviewable support.
• Responsibilities, competence, communication, risk, legal duties, and change impact were considered where relevant.
• Findings, corrective actions, monitoring, review triggers, and improvement ownership are clear.

Lesson Outcome

Learners can apply Risk, Threats, Vulnerabilities, Security Levels, and Requirements, explain the reasoning used, and defend the result through IACS risk and security-requirement register.