SLA breach analysis reports

Name: SLA breach analysis reports
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Identifies sla breach analysis reports 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: category-aware structural regex with anchor and context constraints replaces phrase-only detection. 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(?:SLA\s+breach|service\s+level\s+agreement|SLA\s+violation|uptime\s+target|performance\s+metric|penalty\s+clause|service\s+credit|response\s+time|resolution\s+time|availability\s+target|breach\s+analysis|SLA\s+report)\b

Corroborative evidence keywords

sla breach analysis reports, sla, breach, analysis, reports, operations, resilience

Proximity: 300 characters

Should match

SLA breach — Primary topic phrase match
service level agreement — Case-insensitive topic phrase match
SLA violation — Alternative topic phrase match
uptime target — 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
backup outage — 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.