Evaluating The GitGuardian Secrets Detection Platform: A Self-Guided Roadmap
Tags: enterprise, security, tools, secrets
Published: 2024-03-04 14:46:53

Let's face it: acquiring enterprise security software can feel daunting. There are so many competing security priorities in the enterprise, making it hard to know which ones to address and in what order. Once you are ready to evaluate solutions, it can be confusing to know where to start. This includes secrets security, both on the storage and management side and the detection and leak remediation side. 

[![a very confusing map labeled 'security'](https://lh7-us.googleusercontent.com/ZzXBO6epZvB9Kg5J9HBFb7JHnZVtlzGQlHFcjVD8pJ2NIHimiRYG4wlexhIlA5lfIQxA3qtEMxm4DAQw6g6f7UUvLk4QrcotkZoG58vYFtbD-iU3cNlev1PmBDciwhuDCNYECwt9EA1NUGrPBSiL7Q)](https://lh7-us.googleusercontent.com/ZzXBO6epZvB9Kg5J9HBFb7JHnZVtlzGQlHFcjVD8pJ2NIHimiRYG4wlexhIlA5lfIQxA3qtEMxm4DAQw6g6f7UUvLk4QrcotkZoG58vYFtbD-iU3cNlev1PmBDciwhuDCNYECwt9EA1NUGrPBSiL7Q)

For those who might be tackling secrets security now or in the near future, we want to shine a light on the path we have seen many customers take, moving from free, personal use of the [GitGuardian Secrets Detection Platform](https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com) all the way through to successful enterprise adoption. While every organization is different, and your circumstances might be unique to you, we are happy to share what we have learned from our customers over the years. 

Free for individuals
--------------------

At GitGuardian, we want every developer to keep their secrets secret and stop credentials from leaking into their shared code. This is why we make GitGuardian Secrets Detection and [ggshield, our CLI](https://www.gitguardian.com/ggshield?ref=blog.gitguardian.com), absolutely free for individual developers. Many developers use GitGuardian when they are ready to release code into the wild, especially as open source projects, to make sure they are not opening any access to unintended users. 

With just a few commands, any developer working on their personal projects or on open source contributions can add a [handy pre-commit or pre-push git hook](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?ref=blog.gitguardian.com) to their repositories to automatically prevent the over 400 types of secrets from making it into their git history. 

### Free for small teams

If your team has 25 developers or fewer, you also qualify to use our free tier of the [GitGuardian Secrets Detection](https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com) platform. We do not restrict the power of our scanning tools for free customers, providing the same level of enterprise protection for all projects, large and small. What you see is what you get with GitGuardian.


A free trial for your larger team's projects
--------------------------------------------

When adopting or evaluating any enterprise solution, it is a good idea to start small and view the process as a journey, not a rushed [moonshot style mission](https://www.merriam-webster.com/wordplay/moonshot-words-were-watching?ref=blog.gitguardian.com). Yes, you should act with urgency to attain better security, but starting with small, manageable efforts is preferable to the extremes of doing nothing or abandoning other ongoing security efforts to focus on what might be a whale of a task. 

Many teams start evaluating the [GitGuardian Secrets Detection](https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com) platform by focusing on a single project or repository they deeply understand. When you first add a new repo to your defined perimeter, the platform will perform a historical scan. This deep scan will look through every branch and every commit in your project's git history, uncovering any and all hardcoded secrets lurking below the surface. This is especially useful for inherited legacy code and decades-old [big balls of mud](http://www.laputan.org/mud/mud.html?ref=blog.gitguardian.com#Abstract). 

[![GitGuardian Dashboard with Historical Scan section highlighted](https://lh7-us.googleusercontent.com/DSJMsTigIORrCjR2E0sOWOzobl7CkEYocGc4rwNWuVLA-GHvYLBYDgSM_2nqYnOjJaph8q7aC82dxGlyaba4xjhxB8L0SpcdtjRqv7pFDx3FPbSYVgnEXB1IsakmwtHW3lO8PfNDKQ5lQOkYh5s4ew)](https://lh7-us.googleusercontent.com/DSJMsTigIORrCjR2E0sOWOzobl7CkEYocGc4rwNWuVLA-GHvYLBYDgSM_2nqYnOjJaph8q7aC82dxGlyaba4xjhxB8L0SpcdtjRqv7pFDx3FPbSYVgnEXB1IsakmwtHW3lO8PfNDKQ5lQOkYh5s4ew)

Many teams use these historical findings as a baseline, showing if plaintext secrets in the code are a recurring, ongoing issue.

### Testing for new secrets over time

Once a repository has been added to your GitGuardian perimeter, the platform will scan for any newly added secrets. Many teams will set a period of days or weeks to monitor for new issues and to test sample secrets that represent the real credentials that they worry will slip into the wrong hands. This is when teams also test our ability to [scan Slack channels](https://docs.gitguardian.com/platform/monitor-perimeter/messaging-integrations/slack?ref=blog.gitguardian.com) for secrets.

### Alerting that works for you

It is during these times that many teams will also test the alert integrations. While all alerts will, by default, trigger a warning email, most teams want to make sure any alerts also get added to the right channel on platforms like Slack or Discord or get those alerts automatically sent to services like PagerDuty or Splunk. You can also create [custom webhooks](https://docs.gitguardian.com/platform/monitor-perimeter/notifiers-integrations/custom-webhook?ref=blog.gitguardian.com) that fire off the alert anywhere you need, into any custom SEIM or orchestration tooling. 

[![Alerting section of the Integrations menu in the GitGuardian dashboard](https://lh7-us.googleusercontent.com/IxVcdJDfSPZg5mt7cujHXxGelwjzi3v9MtqYRX9mDWY4dhetEAjhHqxQd4NA05tbkCKQTp9L52BJTCQSaG1iWlXteMjxXvN5liSUvL0cmr4K8v4ANxdnDSJzHfK4ZOA9DnM8c2xYao9_oXKZHCvTSQ)](https://docs.gitguardian.com/platform/monitor-perimeter/notifiers-integrations/email-alerting?ref=blog.gitguardian.com)

Remediation is challenging
--------------------------

For anyone evaluating an enterprise scanning platform, the question should not only be, "Can it find issues?" but instead, "Can it help us find and solve our issues?" With GitGuardian, the answer is a resounding "Yes!"

Remediation of secrets is a challenge for a number of reasons. The interconnectedness of modern DevOps means one can not simply rip out or revoke a secret once published without fear of a cascading failure event. We must gather all the needed data about the [secret's validity, presence throughout the codebase](https://blog.gitguardian.com/presence-and-validity-checks-product-update/), if it has been [exposed publicly yet](https://blog.gitguardian.com/unveiling-public-leak-checks-for-hardcoded-secrets-in-the-gitguardian-platform/), and other vital details.

Gathering facts is a start, but you also need to get feedback directly from the team member who added the secret into the code, the developer. Each incident managed through the GitGuardan dashboard has the option to easily [share the details with selected team members and gather feedback](https://blog.gitguardian.com/coordinating-and-prioritizing-remediation-with-gitguardian/) directly through the platform. Even if the developer is external to your company, the share option can accommodate this communication through the use of a temporarily public URL.

[![Feedback form in the GitGuardian dashboard](https://lh7-us.googleusercontent.com/8Bw6mi0EQ6U_39ptXbPNnFQUjjuHivpIUVkCiNC3Q3FKnCX5TDvztxU2oMpYYikom2MehHqsloa0lLxhE4VLJ0ANP-MwvRLA8FU6RhZIIGmkVboQebIN7VYUymYsqbexaCi4GTOopDnsG82TNR3E9g)](https://docs.gitguardian.com/secrets-detection/remediate/remediate-incidents?ref=blog.gitguardian.com#share-the-incident)

### Working with larger enterprises

Even though GitGuardian makes it easy to perform a self-evaluation and even use the product for free in some situations, we know that most enterprises will require a more formal approach. We have worked with a lot of organizations to perform a [Proof of Concept, POC, exercise and we are happy to share what that process looks like](https://blog.gitguardian.com/evaluating-secrets-detection-platforms-is-messy/). 

Finding your own path
---------------------

[Secrets sprawl is a growing problem](https://www.gitguardian.com/state-of-secrets-sprawl-report-2023?ref=blog.gitguardian.com) affecting every company that writes or leverages code. It is something enterprises need to address sooner than later. Advanced [secrets management maturity](https://blog.gitguardian.com/a-maturity-model-for-secrets-management/) is needed by companies handling sensitive, mission-critical data, requiring addressing the problem of secrets storage and proper use with dedicated secrets managers like [Vault by Hashicorp](https://blog.gitguardian.com/talking-about-data-security-an-introduction-to-aws-kms-and-hashicorp-vault/) or [CyberArk](https://blog.gitguardian.com/protect-secrets-with-cyberark-and-gitguardian-integration/), as well as detecting and remediating secret leaks at scale. 

It might be tempting to think, 'I can just write some regular expression' to address the issue. We have heard from many customers that when it comes down to "[build versus buy](https://blog.gitguardian.com/secrets-detection-build-vs-buy/)" for secrets sprawl, the overhead and magnitude of what is needed often becomes overwhelming rather quickly. But you don't have to just take our word for it. Check out the many, many [reviews and testimonials about GitGuardian from our users](https://www.gitguardian.com/customer-stories?ref=blog.gitguardian.com).

No matter where you are on your security journey, GitGuardian is here to help you get a handle on secrets sprawl. While we encourage you to do your own investigation of our platform, we are also ready to help you navigate this subject. [Reach out today and schedule a demo](https://www.gitguardian.com/book-a-demo?ref=blog.gitguardian.com) and start down the path towards peace of mind when it comes to knowing where your secrets are.

[Request a Meeting](https://www.gitguardian.com/book-a-demo)