DevSecOps Essentials (DSE) — Lesson 3: CI/CD Security, Testing, Supply Chain, Containers, and Release Assurance

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Pipeline Controls and Sast.
• Implement and validate Dast, Software Supply Chain, and Container Security and Release Gates using reviewable evidence.
• Evaluate the condition where analysts reach the wrong conclusion because Container Security and Release Gates evidence is incomplete and Sast context was not preserved and select a proportionate corrective response.

Detailed Topics

• Pipeline Controls applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Sast applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Dast applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Software Supply Chain applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Container Security and Release Gates applied to the course scenario, expected behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces a product team must accelerate delivery while embedding proportionate security controls, preserving developer flow, and producing auditable evidence. The walkthrough connects tools, configuration or analysis logic, system messages, decisions, and evidence captured in the DevSecOps control map, secure-pipeline evidence, dependency report, and improvement backlog. It also tests the exception where analysts reach the wrong conclusion because Container Security and Release Gates evidence is incomplete and Sast context was not preserved.

Hands-On Exercise

Complete a controlled, authorized EC-Council exercise covering CI/CD Security, Testing, Supply Chain, Containers, and Release Assurance and preserve the verified result in the DevSecOps control map, secure-pipeline evidence, dependency report, 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 Pipeline Controls.
• Compare two defensible responses and explain technical, security, operational, legal, and support trade-offs.
• Determine how the DevSecOps control map, secure-pipeline evidence, dependency report, 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 “analysts reach the wrong conclusion because Container Security and Release Gates evidence is incomplete and Sast context was not preserved” 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 DevSecOps control map, secure-pipeline evidence, dependency report, 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 CI/CD Security, Testing, Supply Chain, Containers, and Release Assurance, explain the resulting security or operational behavior, and defend the outcome through the DevSecOps control map, secure-pipeline evidence, dependency report, and improvement backlog.