Skip to content

Review potential exposure

Use this workflow to investigate references to systems you own or are authorized to review. Start with a distinctive domain or configuration marker rather than a broad credential pattern.

Enter a hostname such as api.example.com with Use regex off. Search is case-sensitive. Review the received files and repository names; a marker can appear in legitimate documentation and sample configurations.

Search a related environment variable or use a constrained regex such as EXAMPLE[_-](TOKEN|API_KEY). Investigate one marker at a time so you can record which query produced each finding.

Open code details. Check whether the value is a placeholder, test fixture, generated artifact, or a plausible production configuration. Review the path and commit reference. A high relevance score is a prioritization aid, not verification.

Select Save to Results. In workspace Results, retain the reference, matched context, and any available commit metadata. Export the selected evidence when you need to pass it to the responsible team. Record if the search was partial or reached its limit.

Create a Watchdog with a File Content condition for the distinctive marker. Add repository or path restrictions within the same AND Match rule. Monitoring covers incoming processed changes; it does not replace the historical search.

Include the query, repository, path, commit, observed context, and why the finding merits review. Avoid copying suspected secret values into broadly shared tickets. Follow the responsible team’s incident process for any remediation.