What a finding contains
To see the details of a finding, select its row:- Description: What the matching rule detects, such as a type of API key
- File: The path of the file that contains the secret
- Commit, Author, Email, and Commit Message: The commit that added the secret, and who made it
- Start Line, End Line, Start Column, and End Column: Where the secret is in the file
- Link: A link to the file at that commit, on GitHub, GitLab, or Bitbucket
Finding statuses
Every new finding starts as Unresolved. After you review a finding, change its status to one of the following:- Resolved: You’ve dealt with the leak, for example by revoking the secret
- False Positive: The value isn’t a secret
- Ignore: The value is a secret, but you’ve decided it’s safe to leave, such as a test credential
Change a finding’s status
1
Go to Secret Scanning > Findings.
2
Select the finding’s row, then select Update Status.To change several findings at once, select the checkbox on each finding’s row, then select Update Status below the table.
3
Select a Status. Optionally, enter a Comment that explains your decision.
4
Select Update Status.
Notifications about new findings
When a scan finds secrets, Infisical sends an email and an in-app notification to every member with the Admin role in Secret Scanning. The notification links to the findings from that scan. If a scan fails, the same members get a notification with the error instead. If a scan of a new push finds secrets, Infisical also notifies the author of the commit if they’re a member. If the push has commits from more than one author, Infisical notifies only one of them.If you self-host Infisical, scan notifications need an email service configured. Without one, Infisical doesn’t send the email or the in-app notification.