Tool stack: GitHub, Git Bash, VSCode, Semgrep,
Prepared by the ShieldOps team
Temitayo Kara
Oluwadarasimi Isreal
Abdul Adedamola
Osumili Felix
Kehinde Justinah Coker
ShieldOps closes the gap between finding vulnerabilities and actually fixing them. Most teams run security scans too late, after deployment, during an occasional pen test, or not at all. Leaving hardcoded secrets, vulnerable dependencies, injection flaws, and broken access controls to reach production undetected. ShieldOps embeds security checks (SAST, DAST, dependency scanning, and secrets detection) directly into the CI/CD pipeline, so every commit is tested automatically, and pairs this with a SOAR (Security Orchestration, Automation, and Response) layer that takes every finding, enriches it with real vulnerability data, prioritizes it, and triggers the right response, without waiting on a human to triage it.
The system is built and validated against a real, intentionally vulnerable application. It demonstrates the full loop of the pipeline, a vulnerable commit is caught, the build is blocked, the finding is automatically enriched with CVE/CVSS data, routed through one of three automated playbooks (exposed secret, critical CVE, or confirmed OWASP Top 10 flaw), and tracked in a deduplicated case queue, all visible on a live dashboard alongside a measurable "mean time to triage" (MTTT) that's demonstrably faster than manual review.
Repo setup
Fork OWASP Juice Shop on GitHub so as to control commits.
Integrate Semgrep (SAST) and scan codebase
Semgrep looks inside your source code for actual bugs and vulnerability patterns, SQL injection, XSS, hardcoded crypto keys, insecure deserialization, command injection. It is pattern-matching against your application logic, line by line.