EC-Council • ECDE
Validates the ability to integrate security practices into DevOps pipelines and continuous delivery workflows, covering DevSecOps culture, threat modeling, secure code review, automated security testing, container security, and security monitoring throughout the software development lifecycle.
Questions
609
Duration
240 minutes
Passing Score
70%
Difficulty
AssociateLast Updated
Feb 2026
The EC-Council Certified DevSecOps Engineer (E|CDE), exam code 312-97, is a comprehensive certification that validates a professional's ability to embed security practices across the entire DevOps pipeline. The program covers all eight stages of the DevOps lifecycle — from planning and coding through building, testing, releasing, deploying, operating, and monitoring — ensuring that security is treated as a shared, continuous responsibility rather than an afterthought. Candidates learn to apply threat modeling, secure coding guidelines, static and dynamic application security testing (SAST/DAST), infrastructure as code (IaC) security, container security, and runtime monitoring using industry tools such as SonarQube, Snyk, Checkmarx, Jenkins, Terraform, and Docker Bench.
The certification is notably hands-on, featuring over 80 guided lab exercises delivered in virtual environments spanning Amazon Web Services (AWS), Microsoft Azure, and on-premises platforms. This dual focus on theoretical DevSecOps principles and practical tool-based implementation distinguishes E|CDE from more conceptual security credentials, making it one of the most lab-intensive DevSecOps certifications available. The program has been updated to incorporate AI-powered security tooling and cloud-native security patterns relevant to modern CI/CD workflows.
The E|CDE is designed for mid-career technology professionals who work at the intersection of software development, operations, and security. Primary target roles include DevOps engineers looking to formalize their security knowledge, application security specialists transitioning into DevSecOps, software engineers and QA testers responsible for secure delivery pipelines, and cybersecurity engineers or analysts who need to integrate security tooling into CI/CD workflows. Professionals holding EC-Council's Certified Application Security Engineer (CASE) credential or similar AppSec certifications will find E|CDE a natural progression.
EC-Council recommends candidates have at least two years of experience in information security, along with familiarity with SDLC concepts, automation tools, and scripting languages such as Python or PowerShell. The certification suits professionals targeting specialized roles such as DevSecOps Engineer, Cloud DevSecOps Engineer, AWS/Azure DevSecOps Engineer, or CI/CD Security Engineer.
EC-Council requires applicants who wish to sit for the exam without attending official training to have a minimum of two years of work experience in the information security domain and to submit an eligibility application with a non-refundable fee of USD $100. Candidates who complete an authorized EC-Council training course have the application fee included and gain direct exam eligibility upon course completion.
While there are no mandatory prerequisite certifications, candidates are strongly advised to arrive with a working understanding of application security concepts, the Software Development Lifecycle (SDLC), and CI/CD pipeline fundamentals. Familiarity with at least one cloud platform (AWS or Azure), containerization concepts (Docker, Kubernetes), and basic scripting will allow candidates to make full use of the lab-heavy curriculum and perform well on exam questions focused on practical tool configuration and pipeline integration.
The E|CDE exam (code 312-97) consists of 100 multiple-choice questions and must be completed within 240 minutes (4 hours). The exam is closed-book and is delivered exclusively through the ECC Exam Centre portal; it is not available at third-party proctoring sites. A passing score of 70% (70 out of 100 correct) is required. The exam fee is USD $550, and the voucher is valid for one year from the date of receipt.
There are no published unscored or survey questions. Upon passing, certified professionals are enrolled in EC-Council's Continuing Education Scheme and must pay an annual maintenance fee of USD $80 to keep the credential active.
Holding the E|CDE credential positions professionals for high-demand roles in the DevSecOps specialty, which sits at the convergence of software engineering, cloud operations, and cybersecurity — a skills combination that remains scarce in the market. Certified professionals typically pursue titles such as DevSecOps Engineer, Cloud DevSecOps Engineer (AWS or Azure-focused), Infrastructure DevSecOps Engineer, or DevSecOps CI/CD Specialist. According to EC-Council's published data, the average annual salary for a DevSecOps engineer in the United States is approximately USD $139,479, with entry-level positions starting around USD $118,733 and experienced practitioners earning upward of USD $172,500.
Compared to broader security credentials such as CompTIA Security+ or even CEH, E|CDE is deliberately narrow and applied, making it a strong differentiator for professionals who want to demonstrate pipeline-specific security engineering skills to employers adopting DevSecOps practices. The certification's hands-on lab focus on both AWS and Azure cloud environments also complements cloud platform certifications and makes the credential appealing to organizations undergoing cloud-native transformation. Annual continuing education requirements ensure the credential stays current as the tooling landscape evolves.
5 sample questions with correct answers and explanations. Start a practice session to test yourself across all 609 questions.
1. A cloud-native startup builds microservices on AWS and needs to implement continuous integration with automated security scanning. The team uses AWS CodeBuild for builds and wants to integrate security scanning directly into the build process. Which buildspec.yaml configuration phase should include SAST and SCA scanning to fail builds with high-severity vulnerabilities? (Select one!)
Explanation
The post_build phase is appropriate for comprehensive security scanning after all artifacts are created, allowing analysis of compiled code and dependencies while still failing the build if critical issues are found. The pre_build phase can check dependencies but misses compiled code vulnerabilities. The build phase interrupts compilation before completion. The install phase only sets up tools and running scans there would check incomplete code, missing vulnerabilities that emerge during compilation.
2. A startup is migrating their application secrets from hardcoded configuration files to HashiCorp Vault. The security architect requires that database credentials must be dynamically generated with a maximum lifetime of 1 hour, while API keys for third-party services should be stored as static secrets with versioning enabled. Which Vault configuration should be implemented? (Select one!)
Explanation
The Database secrets engine is specifically designed to generate dynamic credentials on demand for database systems, allowing automatic credential rotation and time-limited leases (1 hour in this case). KV v2 (Key-Value version 2) supports versioning and is ideal for storing static secrets like API keys with version history. KV v1 does not support versioning, making it unsuitable for the API key requirement. Transit secrets engine provides encryption-as-a-service for data encryption/decryption, not credential management. PKI secrets engine manages digital certificates and certificate authorities, not database credentials or API keys.
3. A SaaS company implements shift-left security by integrating SonarLint into developer IDEs. Developers report false positives for SQL injection warnings when using parameterized queries correctly. What action should the DevSecOps team take to address this while maintaining security coverage? (Select one!)
Explanation
SonarLint connected mode synchronizes with SonarQube server, allowing centralized quality profile management where false positives can be marked and synchronized across all developer IDEs. This maintains security rule coverage while reducing noise. Disabling all SQL injection rules eliminates important security checks and creates vulnerabilities. Using @SuppressWarnings annotations scatters security decisions across the codebase without centralized review or audit trails. Replacing tools does not address the root cause of tuning security rules to the specific codebase patterns and introduces new tooling overhead.
4. A microservices architecture deploys to Google Kubernetes Engine with container images built by Cloud Build and stored in Artifact Registry. The security team requires that only verified container images signed by trusted authorities can be deployed to production clusters. Which GCP security mechanism enforces this requirement? (Select one!)
Explanation
Binary Authorization enforces deploy-time security policy requiring cryptographic attestations before images can run on GKE. Attestors verify that images passed security checks in Cloud Build, and policies define which attestations are required for production clusters. This implements trusted image deployment through cryptographic verification. Artifact Registry vulnerability scanning identifies vulnerabilities but does not verify image signing or trusted sources. KMS encryption protects images at rest but does not validate image authenticity or signing. Grafeas stores metadata but requires custom webhook implementation and does not provide built-in attestation verification like Binary Authorization.
5. A financial services company implements shift-left security practices in their SDLC. The development team wants to catch security vulnerabilities before code is committed to the repository. Which combination of tools provides the earliest possible security feedback? (Select two!)
Multiple correct answersExplanation
SonarLint provides real-time security feedback directly in the IDE during code writing, and pre-commit hooks with Gitleaks catch secrets before code enters version control. These represent the earliest possible intervention points in the SDLC. OWASP ZAP performs dynamic testing on running applications much later in the pipeline. Trivy scans during build stage after code is already committed. AWS Inspector operates in production, the furthest point from shift-left principles.
One-time access to this exam