Secrets Scans
Learn how JFrog Advanced Security detects exposed secrets in code and artifacts.
JFrog Advanced Security helps prevent the accidental exposure of secrets such as API keys, passwords, and tokens through its comprehensive secrets detection and token validation capabilities. By scanning both source code and binary artifacts, JFrog Advanced Security prevents unauthorized users from accessing sensitive data, making it a powerful secrets prevention solution.
You can fine-tune secret scan results by ignoring specific findings that your organization knows and accepts. You can apply ignore rules at these levels:
- Entire scanner types
- Individual secret findings
This enables targeted noise reduction and clearer reporting. For more information, see Ignore Advanced Security Violations.
You can identify and address exposed secrets across the development pipeline, with real-time feedback, in the following tools:
- Your IDE
- JFrog CLI
- Frogbot
- The JFrog Platform
For more information, see Enable Advanced Scans.
Supported Secret Types
- Access Tokens and Keys: Detects structured access tokens in both text and binary files, such as API keys, OAuth tokens, and private tokens.
- Token Validation enhances secret detection by verifying the validity of detected tokens and distinguishing between active and inactive tokens by authenticating against the token provider.
- Certificate and Private Key Detection: Identifies issues in X.509 PEM and DER certificates, including:
- Certificates containing private keys
- Expired certificates
- Self-signed certificates
- High Entropy Textual Secrets: Detects high-entropy secrets in source code and configuration files, such as passwords and secret keys with high randomness.
- URL Secrets Detection: Detects embedded credentials in URLs, for example
https://username:[email protected].
Built-in detection doesn't cover every unique secret or pattern. For more information, see Create Custom Secrets Scanner.
Token Validation
Enable Token Validation to verify the validity of detected tokens, distinguishing between active and inactive tokens by authenticating against the token provider.
Note
Token Validation currently supports public SaaS endpoints only, for example
github.comandgitlab.com. Token Validation doesn't validate self-hosted or custom-domain instances, for examplegithub.mycompany.comandgitlab.mycompany.com.
- You can use Token Validation through both the JFrog Platform and the JFrog Xray REST API.
- To enable in the JFrog Platform:
- Navigate to Administration > Xray Settings > General > Advanced Security.
- Select the Enable dynamic token validation checkbox.
- To enable via the REST API, use the Enable Token Validation for Secrets API.
Ignore Secret Findings
When you review a secret and decide it's acceptable or a false positive, you can exclude it from future results by creating an ignore rule for that finding.
The rule applies to that finding, and you can scope it to a specific file, artifact, build, or Release Bundle.
For more information, see Ignore Advanced Security Violations.
Validation Results
After you enable Token Validation, results appear under Findings in violation details. The Token Validation column indicates:
- Active: Token is valid and poses a security risk if compromised.
- Inactive: Token is no longer in use.
- Unsupported: JFrog does not support this token provider.
- Unavailable: JFrog couldn't determine whether the token is active. This can happen when the provider connection is interrupted, blocked by a proxy, or returns an inconclusive response. If you use a TLS-inspecting proxy, make sure the provider URL is allowed, then verify that the connection is stable.
Some providers attach metadata to secrets. For example, AWS includes a Token ID with the Token Secret. The Metadata column displays this metadata.
Access Token Examples
Access token detection finds structured access tokens in text or binary files.
The following table lists example tokens.
| Platform | Example Token |
|---|---|
| GitHub | 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 |
| GitLab | glpat-cV-J-ZMnAy4Ge6GWqGeX |
| npm | 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 |
| Slack | xoxp-6654659592213-6680360740176-6657496465043-78439636fa8af05cb14c83a0527a17f5 |
Supported Providers for Token Validation
The following table lists supported providers and whether they support Token Validation.
| Provider | Token Validation |
|---|---|
| Adobe | Yes |
| Age File Encryption | No |
| Aiven | No |
| Alibaba | Yes |
| Anthropic | No |
| Artifactory | No |
| Asana | No |
| Atlassian | No |
| Authress | No |
| AWS | Yes |
| Azure | Yes |
| Beamer | No |
| Bitbucket | No |
| Bitrise | No |
| Block Protocol | No |
| Brevo | No |
| Buildkite | No |
| CFX Re | No |
| Chief Tools | No |
| CircleCI | No |
| Clojars | No |
| Cloudflare | No |
| CockroachDB | No |
| Contentful | Yes |
| Coveo | No |
| Crates.io | No |
| Databricks | No |
| Databento | No |
| DataStax | No |
| Datadog | No |
| Defined Networking | No |
| DevCycle | No |
| DigitalOcean | Yes |
| Discord | No |
| Docker | No |
| Doppler | Yes |
| Dropbox | Yes |
| Duffel | Yes |
| Dynatrace | No |
| EasyPost | No |
| eBay | No |
| Elastic | No |
| No | |
| Fastly | Yes |
| Figma | No |
| Firebase | No |
| Finicity | No |
| Flutterwave | Yes |
| Frame.io | No |
| GitHub | Yes |
| GitLab | Yes |
| GoCardless | No |
| Yes | |
| Grafana Cloud | No |
| Groq | No |
| Hashicorp Vault | No |
| Heroku | Yes |
| Highnote | No |
| Hubspot | No |
| Hugging Face | No |
| IBM Cloud | No |
| Intercom | No |
| Ionic | No |
| Iterative | No |
| Jenkins | No |
| LaunchDarkly | No |
| Linear | Yes |
| No | |
| Lob | No |
| LocalStack | No |
| Mailchimp | Yes |
| Mailchimp Mandrill | No |
| Mailersend | No |
| Mailgun | Yes |
| Mapbox | Yes |
| MaxMind | No |
| Mergify | No |
| Messagebird | No |
| Midtrans | No |
| MongoDB | No |
| Neon | No |
| New Relic | No |
| Notion | No |
| npm | Yes |
| NuGet | No |
| Octopus Deploy | No |
| Oculus | No |
| Okta | No |
| OpenAI | No |
| OpenRouter | No |
| PagerDuty | No |
| Pangea | No |
| PayPal | Yes |
| Planetscale | No |
| Plivo | No |
| Postman | Yes |
| Postmark | Yes |
| Prefect | No |
| Pulumi | Yes |
| PyPI | No |
| Readme | No |
| Redirect Pizza | No |
| Replicate | No |
| Rootly | No |
| Rubygems | Yes |
| RunPod | No |
| Samsara | No |
| Sauce | No |
| Searchgaurd | No |
| Sendgrid | Yes |
| Sendinblue | Yes |
| Sentry | No |
| Shippo | Yes |
| Shodan | Yes |
| Shopify | No |
| Slack | Yes |
| Snyk | Yes |
| Sonar | No |
| Sourcegraph | No |
| Square | No |
| SSLmate | No |
| StackHawk | Yes |
| Stripe | Yes |
| Supabase | No |
| Tableau | No |
| Tailscale | No |
| Telegram | Yes |
| Telnyx | No |
| Terraform | Yes |
| Travis CI | No |
| Trello | No |
| Twilio | Yes |
| Typeform | Yes |
| Ubidots | Yes |
| Unkey | No |
| WakaTime | No |
| XAI | No |
| Zuplo | No |
Endpoints to Allow
On a self-hosted JFrog Platform, Token Validation sends HTTPS requests from the secrets scanner to these public endpoints. You must allow these endpoints on the scanner egress path so validation can complete. A JFrog SaaS Platform makes these calls from the JFrog network. In these endpoint patterns, <REGION> is the AWS region, <ACCOUNT> is the Azure storage account name, and <DC> is the Mailchimp datacenter prefix.
| Provider | Endpoint |
|---|---|
| Adobe | https://ims-na1.adobelogin.com |
| Airtable | https://api.airtable.com |
| Alibaba | https://ecs.aliyuncs.com |
| AWS | https://sts.amazonaws.com and https://sts.<REGION>.amazonaws.com |
| Azure | https://login.microsoftonline.com and https://<ACCOUNT>.blob.core.windows.net |
| Contentful | https://api.contentful.com |
| DigitalOcean | https://api.digitalocean.com and https://cloud.digitalocean.com |
| Doppler | https://api.doppler.com |
| Dropbox | https://api.dropboxapi.com |
| Duffel | https://api.duffel.com |
| Fastly | https://api.fastly.com |
| Flutterwave | https://api.flutterwave.com |
| GitHub | https://api.github.com |
| GitLab | https://gitlab.com |
https://www.googleapis.com | |
| Heroku | https://api.heroku.com |
| Ionic | https://api.ionicjs.com |
| Linear | https://api.linear.app |
| Mailchimp | https://<DC>.api.mailchimp.com, for example us1, us2, and the other datacenter prefixes |
| Mailgun | https://api.mailgun.net |
| Mapbox | https://api.mapbox.com |
| npm | https://registry.npmjs.org |
| PayPal | https://api.sandbox.paypal.com and https://api-m.sandbox.paypal.com |
| Postman | https://api.getpostman.com |
| Postmark | https://api.postmarkapp.com |
| Pulumi | https://api.pulumi.com |
| Rubygems | https://rubygems.org |
| Sendgrid | https://api.sendgrid.com |
| Sendinblue | https://api.sendinblue.com and https://api.brevo.com |
| Shippo | https://api.goshippo.com |
| Shodan | https://api.shodan.io |
| Slack | https://slack.com |
| Snyk | https://api.snyk.io and https://snyk.io |
| StackHawk | https://api.stackhawk.com |
| Stripe | https://api.stripe.com |
| Telegram | https://api.telegram.org |
| Terraform | https://app.terraform.io |
| Twilio | https://api.twilio.com and https://verify.twilio.com |
| Typeform | https://api.typeform.com |
| Ubidots | https://industrial.api.ubidots.com |
| WakaTime | https://wakatime.com |
Access Tokens and Keys False Positives Reduction
Some access keys won't trigger alerts:
- Public example keys, for example
ANPAI65L554VRJ33ECQS6 - Keys in documentation directories, for example
/usr/local/share/ - Keys matching common test patterns:
.*xxxx.*,.*test.*,.*sample.*,.*example.*.*token.*,.*123456.*,.*abcdef.*,.*foobar.*
Certificate and Private Key Detection
Detects issues in X.509 PEM text and DER binary certificates, including:
- Certificates containing private keys
- Expired certificates
- Self-signed certificates
High Entropy Textual Secrets
Detects and identifies high-entropy secrets in textual files, for example source code and configuration files, when:
- The key is indicative of a secret, for example
passwordorsecret. - The value has high randomness, for example
d#@B2xN,Y}rather than123123123.
The following example shows a high-entropy secret.
my_password: "CorrectHorseBatteryStaple123!"High Entropy Textual Secrets False Positives Reduction
Heuristics minimize false positives. Secrets won't raise alerts if:
- The key is exactly
key, for examplekey = d#@B2xN,Y}. - The value matches test patterns, for example
.*xxxx.*and.*123456.*. - The value contains repeated or sequential characters, for example
123456. - The secret is in documentation directories.
- The secret is in third-party files, for example a third-party npm package.
URL Secrets Detection
Detects secrets embedded in URLs, for example https://myuser:[email protected].
URL Secrets Detection False Positives Reduction
Some URLs won't trigger alerts:
- URLs matching test patterns, for example
.*example.*,.*foo.*, and.*bar.* - Authentication placeholders, for example
.*user:pass.*,.*username.*, and.*anonymous.* - URLs referencing image files, for example
.jpg
Related Topics
Updated 27 days ago
