Bearer
Detects Bearer patterns.
- Type
- regex
- Engine
- universal
- Confidence
- high
- Confidence justification
- High confidence: structurally constrained pattern with corroborative keyword support reduces false positive rates significantly. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Verified
- Jurisdictions
- global
- Regulations
- Criminal Code Act 1995 (Cth)
- Frameworks
- CIS Controls, ISO 27001, NIST CSF, PCI-DSS, SOC 2
- Data categories
- credentials, security
- Scope
- specific
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\b[Bb]earer\s+[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\b
Corroborative evidence keywords
api key, api_key, apikey, access key, secret key, private key, auth token, authorization, access token, bearer, conn str, connection string, connectionstring, cookie, credential, database, host, JWT, oauth, passphrase (+37 more)
Proximity: 300 characters
Should match
Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxIn0.reCjcZ0-m3Q— Bearer token with JWTbearer eyJhbGciOiJub25lIn0.eyJ0ZXN0IjoiMSJ9.abc— Lowercase bearer with JWTBearer eyJ0eXAiOiJKV1QifQ.eyJpZCI6MSwiYWRtaW4iOnRydWV9.sig— Bearer token with type claim
Should not match
Bearer single-segment-token— Only one segment instead of three dot-separatedToken eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxIn0.sig— Wrong keyword (Token instead of Bearer)Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxIn0— Only two dot-separated segments instead of threetemplate example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Authentication-related terminology in software documentation, security training materials, or system architecture descriptions without actual credentials. Mitigation: Require proximity to credential-specific patterns (API keys, connection strings, tokens) rather than general security terminology.
- Code snippets and configuration examples containing credential-related keywords or placeholder values in developer documentation. Mitigation: Check for common placeholder patterns (example.com, localhost, 0000) and documentation file types to reduce false positives from technical writing.