IntermediateDevSecOps: Secure CI/CD & Supply Chain project · about 12 hours

Secure CI pipeline with SAST, SCA and secret scanning

Add code, dependency and secret scanning to a CI pipeline with quality gates.

The real-world brief

A fintech wants security issues caught on every pull request instead of at the end of a project.

What you will build

  • A pipeline with SAST, SCA and secret scans
  • Gates that fail on high-severity issues
  • A planted vulnerability caught and fixed
  • A short security report

Skills you will practise

SASTSoftware composition analysisSecret scanningSecurity gates

Tools

GitHub ActionsSemgrep or SonarQubeOWASP Dependency-Check or SnykGitleaksPython or Java app

Project tasks

The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.

1Baseline app Steps in portal
2Scans Steps in portal
3Gates Steps in portal
4Fix and report Steps in portal

How companies use DevSecOps: Secure CI/CD & Supply Chain

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.

Questions

Can I add the Secure CI pipeline with SAST, SCA and secret scanning project to my resume?

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.

How long does this project take?

About 12 hours of hands-on work, and it fits best after week 4 of the DevSecOps: Secure CI/CD & Supply Chain course.

Where do I get the step-by-step tasks?

Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.