ISSEP — Lesson 2: Engineering Risk, Threat Modeling, Security Planning, and Technical Management

Learning Objectives

• Distinguish the roles, assumptions, and evidence associated with engineering risk analysis, threat modeling, and security planning.
• Apply technical reviews and supplier and acquisition risk while completing a controlled evaluate design alternatives before a major acquisition decision.
• Defend a decision about which design, assurance, and acquisition conditions should govern approval using risk, operational, and governance considerations.

Detailed Topics

• Challenge engineering risk analysis with a realistic misuse, failure, or change condition before accepting the result.
• Document threat modeling with ownership, evidence, review criteria, and a clear next action.
• Trace security planning from business need to technical implementation and retained assurance evidence.
• Evaluate technical reviews against policy, risk appetite, architecture constraints, and measurable acceptance criteria.
• Use supplier and acquisition risk to resolve a course-specific decision and record why rejected options were not selected.

Instructor Demonstration

A guided demonstration traces the scenario from initial evidence to an approved conclusion. Learners observe how evaluate design alternatives before a major acquisition decision, how competing options are ruled out, and how the engineering risk model and security engineering plan records the final rationale.

Hands-On Exercise

Use the course scenario to evaluate design alternatives before a major acquisition decision, then submit a reviewable engineering risk model and security engineering plan.

1. Inventory the facts, assets, stakeholders, constraints, and evidence relevant to engineering risk analysis.
2. Perform the core analysis for threat modeling and security planning, recording assumptions and rejected options.
3. Introduce the adverse condition where the preferred solution meets functional targets while introducing unmanaged supply-chain and integration risk and revise the proposed response.
4. Complete the engineering risk model and security engineering plan with ownership, acceptance criteria, residual concerns, and the next review date.

Scenario Analysis

• Identify which assumption has the greatest effect on which design, assurance, and acquisition conditions should govern approval.
• Compare two viable approaches involving technical reviews and explain their security and operational trade-offs.
• Specify the evidence required before the engineering risk model and security engineering plan can be accepted.

Troubleshooting Guidance

Separate symptoms from causes by tracing the decision back through inputs, trust assumptions, implementation evidence, and stakeholder responsibilities. Do not close the issue until the scenario in which the preferred solution meets functional targets while introducing unmanaged supply-chain and integration risk has been reproduced or ruled out.

Validation Checklist

• The scope and ownership for engineering risk analysis are explicit and agreed.
• The selected treatment for threat modeling is supported by scenario evidence rather than assumption.
• The exception involving the preferred solution meets functional targets while introducing unmanaged supply-chain and integration risk was tested and its impact was recorded.
• The engineering risk model and security engineering plan identifies acceptance criteria, residual risk, responsible owners, and follow-up actions.

Lesson Outcome

Learners can apply Engineering Risk, Threat Modeling, Security Planning, and Technical Management, explain which design, assurance, and acquisition conditions should govern approval, and support the conclusion with a reviewable engineering risk model and security engineering plan.