Keep your code safe during the development path using OS tools
summary
Demonstration shows a SAST workflow that scans source, bytecode and binaries and flags secrets in Git history, handling C, C#, Java, Kotlin, Python, Ruby, Go, JavaScript and JSON. CLI and VS Code extension run local analyses; CI integration via GitHub Actions uses a fail-on-find flag to break pipelines. The demo links results to a web manager, runs engines that include dependency and leak checks, and reports 10 findings: 1 critical, 2 high, 3 medium, 4 low.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:17Secure code in development
- 3:43SAST versus DAST
- 7:16Trivy and its features
- 10:25Installing Trivy
- 11:29Trivy CLI scanning
- 14:41Vulnerabilities Trivy detects
- 16:25Trivy in IDEs and CI/CD
- 22:00Trivy in VS Code demo
- 23:44Trivy installation methods
- 24:28Trivy in GitHub Actions
- 28:25Break pipelines on critical issues
- 31:13Trivy GitHub Actions demo
- 33:38Fixing vulnerabilities
- 34:00Q&A
related talks
39m5 Open Source Security Tools All Developers Should Know About
44mUsing Static Analysis Tools to Become A Superhero Programmer
44mAn intro to improving the security of your code with free analysis tools
36mCode Analysis: Empowering developers to write performant, reliable, and safe C++
42mSecure or Insecure Code, That Is the Question
23mStopping vulnerabilities at the source
22mCode Security in the AI Era | SAST, SCA & Secrets Detection
54mKeeping your code secure