Kubernetes Internal Service URL
Detects Kubernetes Internal Service URL 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
- wide
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Unsupported
Pattern
https?://[a-z0-9][a-z0-9.\-]{1,200}\.svc\.cluster\.local(?::\d+)?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
http://my-service.default.svc.cluster.local— Kubernetes service URL in default namespacehttps://api-gateway.production.svc.cluster.local:8443— Kubernetes service URL with porthttp://redis-master.cache.svc.cluster.local:6379— Kubernetes Redis service URL
Should not match
https://my-service.default.svc.cluster.remote— Wrong domain suffix (.remote instead of .local)https://my-service.default.pod.cluster.local— Wrong subdomain (pod instead of svc)ftp://my-service.default.svc.cluster.local— Wrong scheme (ftp 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.