Azure DocumentDB Auth Key
Detects Azure DocumentDB (now Cosmos DB) authentication key 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 Base64 key pattern with DocumentDB context keywords 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
- Risk rating
- 10
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?i)(?:AccountKey|AuthKey|documentdb[._-]?key)\s*=\s*[A-Za-z0-9+/\s]{43,92}={0,2}Corroborative evidence keywords
DocumentDB, documentdb, Cosmos DB, AccountKey, AuthKey, documents.azure.com, auth key, access key, api key, api_key, apikey, access token, auth token, authorization, bearer, conn str, connection string, connectionstring, cookie, credential (+44 more)
Proximity: 300 characters
Should match
AccountKey=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==— DocumentDB auth key (88 chars Base64)AuthKey=ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ABCDEFGHIJKLMNOPQRSTUV==— Auth key with mixed charactersdocumentdb_key=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000==— DocumentDB key with placeholder value
Should not match
AccountKey=tooshort— Too short to be a valid DocumentDB keyAccountEndpoint=https://mydb.documents.azure.com:443— Endpoint URL, not a keytemplate example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Azure Cosmos DB / DocumentDB documentation with placeholder connection strings. Mitigation: Check for common placeholder patterns and documentation context.
- Other Azure services using similar Base64 key format. Mitigation: Use DocumentDB-specific keywords and endpoint patterns for differentiation.