Certificate
Defensive view: earn the certificate by passing the exam and shipping a portfolio of defensive engineering.
Certificate outline
EXAMPLE
# Security certificate - outline (defender path) ## Part 1 - exam (90 min) Topics: - Threat modelling (STRIDE / LINDDUN basics) - Identity + access (OIDC, MFA, conditional access) - Cloud baselines (AWS / Azure / GCP) - AppSec defences (OWASP Top 10) - Detection engineering + MITRE ATT&CK - IR lifecycle + evidence preservation - CVD + bug bounty ethics Passing mark: 70 percent. ## Part 2 - portfolio (take-home, ~15 hours) Ship four artefacts: 1. A 5-page threat model of a small app you built or operate 2. A DetectionLab + 5 Sigma rules + screenshots of them firing during Atomic Red Team tests 3. An IR runbook for one scenario (BEC, cloud cred theft, ransomware) with named tools + owners 4. A short report on a real (in-scope) bug bounty finding OR a CVD submission you made For each artefact include: - A short README explaining what + why - Reproducible setup (Terraform / Ansible / shell) - Lessons learned + tradeoffs section Submit a Git repo and a public LinkedIn post summarising the work. ## Grading - Threat model depth (20 percent) - Detections + coverage matrix (30 percent) - Runbook quality (20 percent) - Bounty/CVD professionalism (15 percent) - Reproducibility (15 percent) ## Tips - Build a private write-up repo from day one; you will need it - Pair each offensive lab with a defensive question - Be ethical first; reputation outlasts any role ## After the certificate - Apply to SOC analyst / IR / cloud security roles - Continue learning in public (talks, write-ups) - Mentor someone starting out
Why it matters
A security certificate is real when it includes a portfolio. Threat model + detections + runbook + ethical bounty work shows you can defend. The cert is a filter; the portfolio is what gets you the offer.
Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.
Discussion
Loading…