Skip to main content

// roadmap/devsecops

DevSecOps Roadmap

Build security into every step of how you ship, in 6 stages: security basics, secure code, CI/CD, containers, cloud and security operations. Each topic links to our guides and posts to read and to simulators, labs and checklists to practice with. Your progress stays in this browser.

  • 6 stages
  • 30 topics
  • 36-48 weeks
  • 6 projects
  • 87 links to our material

New to DevOps? Start with the Junior DevOps Roadmap.

roadmap --status

Supported byBecome a sponsor
BitriseAtomsizedDigitalOceanDevDojoSMTPfastQuizAPI

// stage 01 of 06, 6-8 weeks

Security Fundamentals

Build your security foundation with core concepts and threat modeling.

progress0/5
  1. Security Principles

    essential~15 h

    Learn CIA triad, defense in depth, least privilege, and zero trust concepts.

  2. OWASP Top 10

    essential~20 h

    Understand the most critical web application security risks.

  3. Threat Modeling

    important~15 h

    Learn STRIDE, DREAD, and attack tree methodologies.

  4. Linux Security Basics

    essential~20 h

    File permissions, user management, SSH hardening, and firewall basics.

  5. Cryptography Essentials

    important~15 h

    Symmetric and asymmetric encryption, hashing, TLS/SSL, and PKI basics.

// stage project

Security Assessment Report

beginner

Perform a basic security assessment on a sample application using OWASP guidelines.

// after this stage you can

  • Identify common security vulnerabilities
  • Apply security principles to system design
  • Conduct basic threat modeling sessions
  • Understand encryption and authentication mechanisms

// tips

  • Practice on intentionally vulnerable apps like DVWA or Juice Shop
  • Join security communities like OWASP local chapters
  • Read security breach post-mortems to learn from real incidents

// stage 02 of 06, 6-8 weeks

Secure Development

Shift security left by integrating security into the development process.

progress0/5
  1. Secure Coding Practices

    essential~25 h

    Input validation, output encoding, parameterized queries, and error handling.

  2. SAST Tools

    essential~20 h

    Static Application Security Testing with SonarQube, Semgrep, or CodeQL.

  3. Dependency Scanning

    essential~10 h

    Find vulnerable dependencies with Dependabot, Snyk, or OWASP Dependency-Check.

  4. Pre-commit Hooks

    important~8 h

    Implement security checks before code is committed using git hooks.

  5. Code Review for Security

    important~15 h

    Learn to identify security issues during code reviews.

// stage project

Secure Code Pipeline

intermediate

Set up a CI pipeline with SAST, dependency scanning, and pre-commit security hooks.

// after this stage you can

  • Write secure code following best practices
  • Configure and interpret SAST tool results
  • Manage vulnerable dependencies effectively
  • Conduct security-focused code reviews

// tips

  • Start with one SAST tool and learn it deeply before adding more
  • Focus on reducing false positives to maintain developer trust
  • Create security champions in each development team

// stage 03 of 06, 6-8 weeks

CI/CD Security

Secure your build and deployment pipelines from threats.

progress0/5
  1. Pipeline Hardening

    essential~20 h

    Secure CI/CD configurations, runner isolation, and artifact signing.

  2. Secrets Management

    essential~25 h

    HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault for secure secrets.

  3. DAST Integration

    important~20 h

    Dynamic Application Security Testing with OWASP ZAP or Burp Suite.

  4. Supply Chain Security

    important~15 h

    SBOM generation, artifact verification, and Sigstore/cosign.

  5. Security Gates

    essential~10 h

    Implement quality gates that block deployments on security failures.

// stage project

Secure CI/CD Pipeline

intermediate

Build a complete pipeline with secrets management, DAST, and security gates.

// after this stage you can

  • Design and implement secure CI/CD pipelines
  • Manage secrets without hardcoding them
  • Integrate dynamic security testing into deployments
  • Generate and verify software bills of materials

// tips

  • Treat pipeline configurations as code: version control and review them
  • Never store secrets in environment variables visible in logs
  • Use ephemeral build environments when possible

// stage 04 of 06, 6-8 weeks

Container Security

Secure containerized applications from build to runtime.

progress0/5
  1. Image Security

    essential~20 h

    Build minimal images, scan with Trivy/Grype, and use trusted base images.

  2. Container Runtime Security

    essential~20 h

    Seccomp, AppArmor, read-only filesystems, and non-root users.

  3. Kubernetes Security

    essential~30 h

    RBAC, Network Policies, Pod Security Standards, and admission controllers.

  4. Runtime Threat Detection

    important~15 h

    Falco, Sysdig, or Aqua for detecting anomalous container behavior.

  5. Service Mesh Security

    nice to have~20 h

    mTLS, authorization policies, and traffic encryption with Istio or Linkerd.

// stage project

Secure Kubernetes Deployment

advanced

Deploy an application to Kubernetes with all security best practices implemented.

// after this stage you can

  • Build and scan secure container images
  • Implement container runtime hardening
  • Configure Kubernetes security controls
  • Monitor containers for security threats

// tips

  • Start with Pod Security Standards before implementing custom policies
  • Use distroless or scratch base images for production
  • Implement network policies even in development environments

// stage 05 of 06, 6-8 weeks

Cloud Security

Secure cloud infrastructure and implement cloud-native security controls.

progress0/5
  1. IAM Best Practices

    essential~25 h

    Least privilege, role-based access, and identity federation.

  2. Infrastructure as Code Security

    essential~15 h

    Scan Terraform/CloudFormation with Checkov, tfsec, or KICS.

  3. Cloud Security Posture

    important~20 h

    CSPM tools like Prowler, ScoutSuite, or cloud-native solutions.

  4. Data Protection

    essential~15 h

    Encryption at rest and in transit, key management, and data classification.

  5. Network Security

    important~20 h

    VPCs, security groups, WAF, and DDoS protection.

// stage project

Secure Cloud Architecture

advanced

Design and implement a secure multi-tier cloud architecture following the Well-Architected Framework.

// after this stage you can

  • Design IAM policies following least privilege
  • Scan infrastructure code for security issues
  • Implement cloud security monitoring and compliance
  • Secure data in cloud environments

// tips

  • Get certified in your primary cloud provider (AWS/Azure/GCP)
  • Use infrastructure as code for all cloud resources
  • Enable CloudTrail/Activity Logs from day one

// stage 06 of 06, 6-8 weeks

Security Operations

Monitor, detect, and respond to security incidents effectively.

progress0/5
  1. Security Monitoring

    essential~25 h

    SIEM concepts, log aggregation, and security dashboards.

  2. Incident Response

    essential~20 h

    IR playbooks, containment strategies, and post-incident reviews.

  3. Vulnerability Management

    essential~15 h

    Vulnerability scanning, prioritization, and remediation workflows.

  4. Compliance Automation

    important~20 h

    Automate compliance checks for SOC2, PCI-DSS, HIPAA, or ISO 27001.

  5. Security Metrics

    important~10 h

    Track MTTD, MTTR, vulnerability counts, and security debt.

// stage project

Security Operations Center

advanced

Set up monitoring, alerting, and incident response procedures for a production environment.

// after this stage you can

  • Set up centralized security monitoring
  • Create and execute incident response plans
  • Manage vulnerabilities across the organization
  • Track and report on security metrics

// tips

  • Start small. You cannot monitor everything from day one.
  • Practice incident response with tabletop exercises
  • Build relationships with development teams, not walls

// next

Keep going

Found a wrong link or a missing topic? Open an issue on GitHub.