DevSecOps Labs (AZ-2008)
Overview
Completed four AZ-2008 DevOps Foundations labs and translated them into cybersecurity value: secure planning, controlled change, repeatable delivery, and tested resiliency. This project showcases how I approach security as part of the delivery lifecycle (DevSecOps), not just reactive response.
Lab Breakdown (Skills + Products Used)
Lab 01 — Agile Planning & Management
Cybersecurity skills gained
- Translating security work into measurable deliverables (hardening tasks, remediation items, validation steps)
- Risk-based prioritization and delivery tracking
- Audit-friendly documentation habits
Products used
- GitHub (Projects/Issues)
Lab 02 — Implement Flow of Work (PR-driven delivery + guardrails)
Cybersecurity skills gained
- Pull request hygiene and review discipline
- Practical change control: who changed what, when, and why
- Safer merges through repeatable collaboration patterns
Products used
- GitHub (Branches, Pull Requests, Reviews)
Lab 03 — CI/CD + Infrastructure as Code
Cybersecurity skills gained
- CI/CD workflow logic (repeatable builds/releases)
- Infrastructure-as-code consistency to reduce configuration drift
- Foundations for pipeline security controls (secrets hygiene, gated approvals, deployment discipline)
Products used
- GitHub Actions
- Azure
- Bicep
- GitHub Copilot
Lab 04 — Resiliency & Failure Testing
Cybersecurity skills gained
- Failover and availability mindset (availability is part of security)
- Controlled fault injection to validate recovery assumptions
- Operational readiness: reducing blast radius and improving recovery confidence
Products used
- Azure Traffic Manager
- Azure Chaos Studio
- Azure
Why This Matters for Cybersecurity
- Controlled change reduces accidental exposure and speeds up investigations.
- Repeatable deployments reduce misconfigurations and drift.
- Resiliency testing supports incident readiness and availability outcomes.