Secrets detection

A collection of 24 posts

GitGuardian vs. Custom-Built Secrets Detection Tools

GitGuardian vs. Custom-Built Secrets Detection Tools

DIY or open-source secrets detection can seem cost-effective and customizable initially... until you start hitting the first obstacles like scalability, developer experience (DX), or deep application security expertise. Read on to find out how GitGuardian can help you rise above these!

GitGuardian Secrets Detectors 2022 Wrap-Up

GitGuardian Secrets Detectors 2022 Wrap-Up

The GitGuardian team is still striving to provide the broadest secrets detection engine, helping you find and fix all sorts of hardcoded secrets! Learn more about the specific and generic detectors our team has released in 2022 in this post.

The State of Secrets Sprawl 2022

The State of Secrets Sprawl 2022

In its 2022 report, GitGuardian extends its previous edition focused on public GitHub by depicting a realistic view of the state of secrets sprawl in corporate codebases.

State of Secrets Sprawl on GitHub - 2021

State of Secrets Sprawl on GitHub - 2021

GitGuardian has been scanning every single public commit made on GitHub for secrets since 2017, now we are releasing our findings in the most comprehensive study on secrets sprawl ever conducted.

Secret sprawl and the attack surface - Secrets in source code (episode 1/3)

Secret sprawl and the attack surface - Secrets in source code (episode 1/3)

The first in a series of articles that will take a deep dive into secrets within source code: In this article, we will look at the concept of secret sprawl, the unwanted distribution of secrets through multiple systems, and how we can prevent it.

arrow-down