The secrets issues table provides a consolidated view of all secrets issues. Each row represents an issue created when a scanner finding matches a unified policy, linking the exposed secret to a specific detection rule, file, repository, and the policy that triggered the issue.
Visible columns (default)
Property | Description |
|---|---|
Severity | The severity level assigned to the secrets issue: Critical, High, Medium, Low, Informational, or Unknown. Severity is determined by the detection rule and may be overridden by a matched unified policy |
Name | The descriptive name of the secrets issue (such as AWS access key detected in code). The Name column serves as the primary identifier for the issue |
File Path | The path to the source code file containing the exposed secret, including the affected line range (such as |
Branch | The repository branch where the secret was detected (such as main) |
Created | The timestamp when the issue was first detected |
Secret Type | The classification of the detected secret (such as AWS Access Key, GitHub Token, Stripe API Key, Slack Bot Token) |
Prioritization Labels | Contextual labels that indicate risk-amplifying factors such as repository visibility, validation status, or application criticality |
Filter and sort the table
Use the filter bar at the top of the Secrets table to narrow results by any filterable column. Common filtering strategies include:
By severity: Filter to Critical and High severity to focus on the most impactful secrets exposures.
By secret type: Filter to a specific secret type (such as AWS Access Key) to scope remediation to a single credential category.
By branch: Filter to the main or production branch to focus on secrets that affect production-bound code.
By resolution status: Filter to New to identify untriaged secrets issues, or to In Progress to monitor active remediation.
By secret validation: Filter to Valid or Privileged to identify confirmed active credentials that require immediate revocation.
Secrets validation
You can filter secrets based on their validation status. Options include:
Valid: The secret has been verified as active and functional
Invalid: The secret has been verified as no longer active or functional
Privileged: The secret is valid and provides access to sensitive resources or functions
No Validation: Validation was not attempted because the secret type or source does not support verification
Unavailable: Validation could not be performed because the secret source was inaccessible or the required permissions were missing