Azure Service Bus Connection String
Detects Azure Service Bus Connection String patterns. This pattern is based on a Microsoft Purview built-in sensitive information type. Users already running Purview may prefer to enable the built-in SIT directly, or use this version as a starting point for customisation.
- 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
- GDPR
- Data categories
- credentials, security
- Scope
- specific
- Risk rating
- 10
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
Endpoint=sb://[^;]+;SharedAccessKeyName=[^;]+;SharedAccessKey=[A-Za-z0-9+/=]+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
Endpoint=sb://mynamespace.servicebus.windows.net;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=AAAAAAAAAAAA+BBBBBBBBBBBB=— Azure Service Bus connection stringEndpoint=sb://test.servicebus.windows.net;SharedAccessKeyName=SendKey;SharedAccessKey=abcdef123456+ghijkl789012=— Service Bus with custom policyEndpoint=sb://prod.servicebus.windows.net;SharedAccessKeyName=ListenKey;SharedAccessKey=XYZXYZXYZXYZ+123456789012=— Prod Service Bus string
Should not match
Endpoint=sb://test.servicebus.windows.net;SharedAccessKeyName=RootKey— Missing SharedAccessKey parameterServer=sb://test.servicebus.windows.net;SharedAccessKeyName=Key;SharedAccessKey=abc— Wrong initial keyword (Server instead of Endpoint)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.