Endpoint detection telemetry

Name: Endpoint detection telemetry
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Identifies endpoint detection telemetry patterns in security and access control contexts. Detects potential exposure of sensitive security information in international systems.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: structural regex with domain-specific anchors and constrained context replaces phrase-only marker. Added context gating and exclusion rules improve precision and reduce incidental matches.
Detection quality: Mixed
Jurisdictions: global
Regulations: GDPR
Data categories: credentials, security
Scope: wide
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:endpoint\s+detection|carbon\s+black|defender\s+for\s+endpoint|sentinel\s+one|process\s+telemetry|threat\s+detection|endpoint\s+security|behavioral\s+analysis|agent\s+telemetry)\b

Corroborative evidence keywords

endpoint detection telemetry, endpoint, detection, telemetry, security, operations, threat, data

Proximity: 300 characters

Should match

endpoint detection — Primary topic phrase match
carbon black — Case-insensitive topic phrase match
defender for endpoint — Alternative topic phrase match
sentinel one — Additional topic phrase match

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
edr process — Generic word pair from old broad template should not match

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.