SLA breach analysis reports

Detects SLA breach analysis reports: SLA breach or service-credit wording with measured metrics against targets and populated contract, incident and credit fields. Topic wording alone is discovery-only.

Type
regex
Engine
boost_regex
Confidence
medium
Confidence justification
Medium confidence: the topic phrase alone is discovery-only; enforcement needs populated structure (a numeric service metric (availability/uptime/target/response/resolution time with a unit) or a populated contract field (incident/ticket/contract number, customer, supplier, service, reporting period, credit amount)), and 85 needs two distinct structures plus independent contractual-consequence (penalty, rebate, KPI, remediation, downtime) evidence, so policies, blank forms and training text stay below 75.
Detection quality
Topic false positive
Jurisdictions
global
Regulations
Competition and Consumer Act 2010 (Cth)
Frameworks
ISO 27001, SOC 2
Data categories
security
Scope
wide
Risk rating
8
Platform compatibility
Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:SLA\s+(?:breach|violation|miss|failure)(?:es)?(?:\s+(?:analysis|report))?|service\s+level\s+(?:breach|failure|shortfall)|breach(?:ed)?\s+(?:the\s+)?SLA|service\s+credits?\s+(?:calculation|claim|report))\b

Corroborative evidence keywords

root cause, penalty, rebate, abatement, KPI, contractual, remediation plan, downtime, customer impact, P1

Proximity: 300 characters

Should match

Should not match

Known false positives

References