Add Your Own Custom Secrets Detectors To GitGuardian
GitGuardian already looks for over 390 different types of specific secrets - from Adobe and AWS keys to Zoom and Zendesk Tokens. That's on top of looking for over a dozen generic patterns like Bearer tokens and JSON web tokens.
Did you know that you can add
your own custom detectors to make GitGuardian Secret Detection even more powerful? GitGuardian already looks for over 390
different types of specific secrets from Adobe and AWS keys to
Zoom and Zendesk Tokens. That's on top of looking for over a dozen generic
patterns like bearer tokens and JSON web tokens. For some enterprise, though, especially those
writing their own APIs and orchestrating custom services, total coverage means adding additional
detectors that GitGuardian should scan for. Good news! Anyone on a Business plan
can now request to extend GitGuardian's secrets detection engine to support
detectors specific to their organization. To submit your own detector, open your GitGuardian Workspace and click on Settings
in the lower left-hand sidebar Next, navigate to the Secrets
detection menu and click on Table of Detectors from the navigational
tab or just scroll down to that section. Click on the Add a Custom Detector button
on the right-hand side and provide all the requested information, including any RegEx you
have written. The more detail here, the better. Once submitted, the engineering team
will acknowledge the request and get to work. They will soon get in touch
with you to validate the detector. Adding your own custom detectors is just one more way GitGUardian Secret Detection can
help ensure your secrets stay secret.