Elasticsearch URI with Credentials
Detects Elasticsearch URI with Credentials 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
- Partial
- 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
https?://[^:]+:[^@]+@[^\s'"]*elastic[^\s'"]*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
https://admin:secret@elasticsearch.example.com:9200— Elasticsearch URI with credentialshttp://user:p4ssw0rd@elastic-prod.internal:9200— Elasticsearch with basic authhttps://elastic:changeme@localhost:9243/elastic-index— Local Elasticsearch with path
Should not match
https://elastic.example.com/search— Missing credentials (no user:pass@ section)elastic://user:pass@localhost:9200— Wrong scheme (elastic:// instead of http/https)template 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.