Build an end-to-end secure delivery chain: SBOMs, signing, admission control, DAST and runtime alerts.
A healthcare company must prove that only scanned, signed software runs in production and that it is tested while running.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
Fintech: Security checks developers do not hate. Security reviews happened at the end and blocked releases for weeks. SAST, dependency, secret and IaC scans run on every pull request with clear fix advice. Most issues are fixed by developers before review, and releases are no longer blocked late.
E-commerce: Leaked cloud keys. A developer pushed AWS keys to a public repository and the account was abused within hours. Secret scanning with push protection, OIDC for pipelines instead of stored keys, and short-lived credentials. No long-lived keys remain in pipelines and new leaks are blocked at push time.
Healthcare: Proving what is in production. Auditors asked which open-source packages ran in production and nobody could answer. SBOMs are generated for every image, images are signed and only signed images are admitted. The team can list every package in production within minutes.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 22 hours of hands-on work, and it fits best after week 12 of the DevSecOps: Secure CI/CD & Supply Chain course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.