ISSEP — Lesson 4: Secure Operations, Change Engineering, Sustainment, Disposal, and Readiness

Learning Objectives

• Identify the dependencies connecting operational security, change impact analysis, and configuration baselines across the lesson workflow.
• Create and validate a change-impact review, disposal plan, and ISSEP readiness record that another practitioner can independently review.
• Determine how to preserve assurance through modification, continued operation, and final decommissioning when the scenario reveals that an urgent modification bypasses engineering review and leaves obsolete data, interfaces, and documentation unmanaged.

Detailed Topics

• Translate operational security into a repeatable workflow that another practitioner can review and operate.
• Test change impact analysis for normal behavior, boundary conditions, and an adverse scenario relevant to the lesson.
• Connect configuration baselines with governance, implementation ownership, verification, and continuous improvement.
• Frame sustainment engineering by identifying its purpose, stakeholders, dependencies, and decision boundary.
• Apply secure disposal to the scenario and capture the analysis, configuration, or artifact that proves the choice.

Instructor Demonstration

The demonstration models professional reasoning rather than a single idealized answer. It shows how to conduct assess a major operational change and plan the eventual retirement of sensitive components, gather evidence, explain trade-offs, and revise the change-impact review, disposal plan, and ISSEP readiness record after the exception is introduced.

Hands-On Exercise

Perform the analysis needed to assess a major operational change and plan the eventual retirement of sensitive components and record the accepted result in the change-impact review, disposal plan, and ISSEP readiness record.

1. Inventory the facts, assets, stakeholders, constraints, and evidence relevant to operational security.
2. Perform the core analysis for change impact analysis and configuration baselines, recording assumptions and rejected options.
3. Introduce the adverse condition where an urgent modification bypasses engineering review and leaves obsolete data, interfaces, and documentation unmanaged and revise the proposed response.
4. Complete the change-impact review, disposal plan, and ISSEP readiness record with ownership, acceptance criteria, residual concerns, and the next review date.

Scenario Analysis

• Identify which assumption has the greatest effect on how to preserve assurance through modification, continued operation, and final decommissioning.
• Compare two viable approaches involving sustainment engineering and explain their security and operational trade-offs.
• Specify the evidence required before the change-impact review, disposal plan, and ISSEP readiness record can be accepted.

Troubleshooting Guidance

Use the artifact trail to locate the earliest unsupported assumption. Validate scope, data, roles, configuration, and review criteria independently; the analysis is incomplete while an urgent modification bypasses engineering review and leaves obsolete data, interfaces, and documentation unmanaged.

Validation Checklist

• The scope and ownership for operational security are explicit and agreed.
• The selected treatment for change impact analysis is supported by scenario evidence rather than assumption.
• The exception involving an urgent modification bypasses engineering review and leaves obsolete data, interfaces, and documentation unmanaged was tested and its impact was recorded.
• The change-impact review, disposal plan, and ISSEP readiness record identifies acceptance criteria, residual risk, responsible owners, and follow-up actions.

Lesson Outcome

Learners can apply Secure Operations, Change Engineering, Sustainment, Disposal, and Readiness, explain how to preserve assurance through modification, continued operation, and final decommissioning, and support the conclusion with a reviewable change-impact review, disposal plan, and ISSEP readiness record.