Secret detection
Understand what a match means, what SecureIntent checks, and when to review the result.
On this page
On this pageSupported patterns
SecureIntent checks supported patterns that may represent sensitive information. The website demonstrates three familiar categories:
| Category | Example context | Safe placeholder |
|---|---|---|
| API key | A service credential in code | [API_KEY_1] |
| Access token | A token in a request or log | [GITHUB_TOKEN_1] |
| Card number | Payment information in text | [CARD_NUMBER_1] |
These are illustrative categories, not an exhaustive detection specification. Installed rules and product versions determine actual coverage.
Review a match
A match means that text resembles a supported sensitive pattern. It does not prove that the credential is valid, active, or authorized. Check the highlighted value and the surrounding context.
If the value is sensitive, anonymize it before sharing. Do not dismiss a finding just because the destination is a tool you use frequently.
False positives and missed secrets
Example keys, documentation snippets, and test fixtures can resemble secrets. Unusual credential formats or sensitive prose may not match a rule. No pattern-based detector covers every possible leak.
Test with fictitious values
Use the fixed examples in the local product demo to explore the product workflow. Do not use active credentials, customer records, or private documents in the website demonstration.