Customize Your Automated Incident Severity Scoring Rules In GitGuardian
Now with custom severity rules, you can automate how GitGuardian labels the criticality of each incident. Fine-tune the pre-built scoring definitions and add your own custom rules that help your team with your particular requirements. Â
GitGuardian has always made it easyÂ
to triage secret leak incidents, Now with custom severity rules, you can automate how GitGuardian labelsÂ
the criticality of each incident. GitGuardian provides 15 preconfigured severityÂ
scoring rules that workspace managers can activate through Settings and the Secret Detection menu.
These rules define specific conditions where you would most likey want to set theÂ
severity to Critical, High, or just info. But we realize that nobody knows what'sÂ
more important to your organization than your organization, which is why we haveÂ
made these predefined rules customizable. Now you can fine-tune whichÂ
conditions set which severity scores! You can also add custom rules that help your teamÂ
with your particular requirements and situation. Want to automatically scoreÂ
certain types of credentials as higher severity if they are inÂ
a default branch? You can do that. How about giving all incidents withÂ
invalid credentials in a test folder a severity of low? If it makes sense for yourÂ
needs, it's straightforward to configure. You have the power to tailor automaticÂ
severity rules to match how you prefer to work. It is just one more way GitGuardian makes it easyÂ
for customers to manage the remediation process.