Secrets in Git Repos [Security Zines]
It's time to stop hardcoding secrets in Git repos
The year is 2022, and secrets in Git repositories are still causing headaches for security engineers around the world. If you're a long-time GitGuardian follower, you already know how committed we are to fighting secrets-in-code with our tutorials, webinars, videos, and reports. This time, we decided to team up with @sec_r0 to raise awareness around the risks of hardcoding secrets, with the help of a drawing!
If you enjoyed reading this zine, spread the word and share it around!
🛑
A lot of speculation has been made around the initial access techniques used in the Solarwinds attack in its early days. With hindsight, we know that the scenario in which hackers could have used the compromised Solarwinds FTP server credentials is untrue. The purpose of this cartoon is simply to remind readers that hardcoding credentials in Git repositories is a very common misstep and that working with Git history commands is more complex than it seems.
For a thorough technical analysis on how the SUNBURST malicious code was inserted into Solarwinds Orion Platform software, you can refer to this report from CrowdStrike’s intelligence team.
For a thorough technical analysis on how the SUNBURST malicious code was inserted into Solarwinds Orion Platform software, you can refer to this report from CrowdStrike’s intelligence team.
🙌
Security Zines is a project led by Rohit Sehgal, Staff Security Engineer at Gojek. Check out his work at securityzines.com/#comics and give him a follow on Twitter @sec_r0 to see what he comes up with next!
Want to learn more about secrets sprawl?
Here's everything you need to go down the rabbit hole.
Understanding secrets sprawl
Best practices around secrets management and detection
More Git tutorials and cheat sheets!
I hope these resources will help you keep secrets out of your Git repositories in the future. Don't forget to bookmark them and share them with your developer friends and colleagues!