DevSecOps Foundation study materials
DevSecOps Foundation study resources

DevSecOps Foundation study plan

DevSecOps Foundation · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Why DevSecOps? & Culture and Management

  • Explain the business and security drivers behind DevSecOps, including the limitations of traditional security models and the benefits of shifting security left.

  • Define the core principles of DevSecOps culture: collaboration, shared responsibility, blameless postmortems, and continuous learning.

  • Compare and contrast DevSecOps with traditional security approaches in terms of roles, processes, and tooling.

  • Identify key stakeholders and describe how to build cross-functional teams that include security from the start.

Your checkpoint

A one-page summary comparing DevSecOps and traditional security across at least five dimensions, with a list of three cultural practices to implement in your organization.

Week 2

Strategic Considerations & General Security Considerations

  • Analyze strategic considerations for adopting DevSecOps, such as selecting pilot projects, defining success metrics, and securing executive sponsorship.

  • Evaluate common security challenges in DevOps environments, including shared responsibility models, attack surface changes, and compliance in dynamic systems.

  • Describe how to integrate security into CI/CD pipelines without sacrificing speed, using automation and guardrails.

  • Outline a threat modeling approach suitable for rapid development cycles.

Your checkpoint

A threat model for a sample CI/CD pipeline, identifying at least five threats and corresponding mitigations, plus a draft adoption roadmap with milestones.

Week 3

IAM: Identity and Access Management & Application Security

  • Explain identity and access management principles in DevSecOps, including least privilege, just-in-time access, and identity federation.

  • Implement secure authentication and authorization for applications and pipelines, using standards like OAuth 2.0 and OpenID Connect.

  • Apply application security practices such as static and dynamic analysis, dependency scanning, and secure coding standards.

  • Integrate security testing into the software development lifecycle (SDLC) and automate vulnerability management.

Your checkpoint

A secure coding checklist and an IAM policy design for a sample application, covering authentication, authorization, and secrets management, with at least three automated security tests described.

Week 4

Operational Security & Logging, Monitoring, and Response

  • Describe operational security practices for infrastructure and workloads, including hardening, patching, and configuration management.

  • Design a logging and monitoring strategy that captures security-relevant events across the pipeline and runtime.

  • Explain incident response in DevSecOps, including detection, containment, eradication, and recovery, with blameless postmortems.

  • Use telemetry and observability to detect anomalies and support forensic analysis.

Your checkpoint

An incident response runbook for a pipeline breach scenario, including detection sources, escalation steps, and a postmortem template, plus a logging architecture diagram.

Week 5

Governance, Risk, Compliance (GRC) and Audit

  • Identify governance, risk, and compliance (GRC) requirements relevant to DevSecOps, such as regulatory standards and industry frameworks.

  • Integrate compliance checks and audit trails into automated pipelines to enable continuous compliance.

  • Perform risk assessments for changes in the software supply chain and prioritize remediation.

  • Explain how to generate audit evidence automatically and maintain traceability from requirements to deployment.

Your checkpoint

A compliance matrix mapping at least three regulatory requirements to automated controls in a CI/CD pipeline, with a sample audit report generated from pipeline data.

Week 6

Why DevSecOps? & Culture and Management & Strategic Considerations

  • Synthesize the cultural and strategic aspects of DevSecOps by designing a change management plan for a security transformation.

  • Develop metrics and KPIs to measure the effectiveness of DevSecOps initiatives, such as mean time to remediate and deployment frequency.

  • Create a communication plan to engage stakeholders and foster a security-first culture.

  • Evaluate case studies of DevSecOps adoption and extract lessons learned.

Your checkpoint

A DevSecOps transformation plan for a hypothetical organization, including a culture change strategy, a metrics dashboard design, and a stakeholder communication plan.

Week 7

General Security Considerations & IAM: Identity and Access Management & Application Security & Operational Security

  • Review and reinforce technical security controls across identity, application, and operations.

  • Design a secure software supply chain, including dependency verification, artifact signing, and provenance.

  • Implement infrastructure as code (IaC) security scanning and policy as code.

  • Conduct a tabletop exercise simulating a security incident in a DevSecOps environment.

Your checkpoint

A secure supply chain reference architecture and a tabletop exercise report with identified gaps and improvement actions.

Week 8

Governance, Risk, Compliance (GRC) and Audit & Logging, Monitoring, and Response & Why DevSecOps? & Culture and Management & Strategic Considerations & General Security Considerations & IAM: Identity and Access Management & Application Security & Operational Security

  • Review all domains comprehensively, focusing on areas of weakness identified in practice exams.

  • Complete a full-length practice exam under timed conditions and analyze results.

  • Revisit key concepts and frameworks, ensuring understanding of GRC, logging, monitoring, and response in DevSecOps.

  • Finalize a personal exam-day strategy, including time management and question-answering techniques.

Your checkpoint

A personalized study guide summarizing key takeaways from each domain, along with a log of practice exam scores and a plan for final review.

Milestones

Week 4: Score at least 70% on a practice quiz covering domains 1-7, and complete the incident response runbook deliverable.

Week 6: Score at least 75% on a practice quiz covering all domains, and receive positive feedback on the transformation plan from a peer or mentor.

Week 8: Score at least 80% on a full-length practice exam and achieve a passing score on at least two different practice exams.