An incident represents a problem that needs to be addressed and resolved.
Thanks to our secrets detection engine, GitGuardian can identify secrets in your source code and display them on the dashboard for you to remediate.
Policy break incidents. (beta)
As an add-on, GitGuardian has also developed security policies that detect the presence of sensitive filenames, file extensions. These policies only run during real time monitoring.
The same secret can be seen multiple times in your VCS. They are referred to as occurrences. GitGuardian automatically groups several occurrences under the same incident in order to facilitate your remediation process.
Thus, an occurrence of a secret incident is uniquely identified by the combination of the following parameters:
- the source (GitHub repository or GitLab project) impacted by the secret occurrence
- the commit in which we detected the secret occurrence
- the commit file containing the secret occurrence
- the line within the commit file where the secret occurred
Alerts are sent only when a new incident is created or reopened because of a regression. A new occurrence attached to an already-existing open secret incident won't raise any alerts.