When investigating a secret leakage incident, you want to know the facts right away. Two of the more urgent questions are going to be "Is the credential still valid?" and "Has the secret been removed from the git repo?" GitGuardian makes it simple to understand the state of your leaked secrets with our automatic validity and presence checks. In the GitGuardian dashboard, in the incident list view, you can quickly filter incidents by Validity to see which ones are valid, Which are found to be invalid, Are in an unknown state. Or if a check could not be completed. From the list view, you can also see which issues are still present in your git history, indicated by the red eye icon. If there is more than one occurrence of the secret found, then we display the count beside the icon. Of course, you can filter for only the incidents with a presence in your Git history or for ones where the secret has been removed. Clicking on an incident brings you to the incident page; validity and presence info can be found on the right-hand side in the "Explore the incident" section. From here, you can retrigger either a validity check or a presence check by clicking the corresponding circular arrow button. These checks are re-run periodically. How often depends on which plan you are on. Check out our documentation for validity and presence checks to read more about this. In the incident view, hovering over the red or grey eye icons in the Presence column will reveal more info about when the last check was run. Being able to quickly assess the validity and presence of a secret during an incident is just one more way GitGuardian makes it straightforward for teams of any size to effectively manage secret sprawl remediation.