Menu

Post image 1
Post image 2
Post image 3
Post image 4
Post image 5
Post image 6
Post image 7
Post image 8
Post image 9
1 / 9
0

DevSecOps in Practice: Tools That Actually Catch Vulnerabilities - Part 1

DEV Community·Hariharan·about 1 month ago
#aoLJas1M
Reading 0:00
15s threshold

Secret Scanning with Gitleaks I have built a deliberately vulnerable Flask app to use as a target for building a real DevSecOps pipeline. The repo is at https://github.com/pkkht/devsecops-demo . This part covers the first gate in the pipeline — secret scanning. Why secrets in code are such a big deal? AWS access keys, API tokens, database passwords — they end up in source code more often than you would think. A developer hardcodes a key to test something locally, forgets to remove it, and commits it. If the repo is public even for a minute, bots are scanning GitHub continuously and will find it. It is one of the most preventable attack vectors and one of the most common. The fix is to catch it before the commit happens. The demo app already has secrets in it - intentionally added. We will use Gitleaks to catch the exposed secrets. What is Gitleaks Gitleaks is an open source secret scanner.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More