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.