EC-Council Certified DevSecOps Engineer v1 — Lesson 1: DevSecOps Culture, Governance, Threat Modeling, Backlog, and Ownership

Learning Objectives

• Explain the roles, services, data, settings, dependencies, and decision criteria governing shared responsibility and security champions.
• Implement and validate threat modeling, security backlog, and risk acceptance using controlled evidence and clear acceptance criteria.
• Evaluate the condition where the planned shared responsibility result cannot be trusted because security champions scope, authorization, or prerequisite evidence is incomplete and select a proportionate corrective response.

Detailed Topics

• shared responsibility applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.
• security champions applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.
• threat modeling applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.
• security backlog applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.
• risk acceptance applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.

Instructor Demonstration

The instructor traces a product engineering team embedding security into an existing delivery pipeline without blocking releases or weakening auditability. The walkthrough connects tools, configurations or analysis logic, system messages, decisions, and evidence captured in the ECDE v1 threat model, pipeline-control map, security-test evidence, and improvement backlog. It also tests the exception where the planned shared responsibility result cannot be trusted because security champions scope, authorization, or prerequisite evidence is incomplete.

Hands-On Exercise

Complete a controlled, authorized EC-Council exercise covering DevSecOps Culture, Governance, Threat Modeling, Backlog, and Ownership and preserve the verified result in the ECDE v1 threat model, pipeline-control map, security-test evidence, and improvement backlog.

1. Confirm scope, authorization, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, outputs, events, decisions, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception without targeting real third-party systems.
4. Document corrections, evidence, ownership, retest criteria, rollback or recovery, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences shared responsibility.
• Compare two defensible responses and explain technical, security, operational, legal, and support trade-offs.
• Determine how the ECDE v1 threat model, pipeline-control map, security-test evidence, and improvement backlog should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check authorization, prerequisites, identity, configuration order, data quality, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “the planned shared responsibility result cannot be trusted because security champions scope, authorization, or prerequisite evidence is incomplete” as a hypothesis until logs, settings, captured outputs, and retest outcomes confirm the cause.

Validation Checklist

• Required components, identities, permissions, settings, safety controls, and dependencies are present.
• The ECDE v1 threat model, pipeline-control map, security-test evidence, and improvement backlog connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback or recovery, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply DevSecOps Culture, Governance, Threat Modeling, Backlog, and Ownership, explain the resulting security, governance, business, or operational behavior, and defend the outcome through the ECDE v1 threat model, pipeline-control map, security-test evidence, and improvement backlog.