Support ticket transcripts

Identifies support ticket conversation transcripts in security and access control contexts. Enforcement requires timestamped requester/agent message turns; ticket, help-desk, and service-desk references without conversational structure remain discovery inventory.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: category-aware structural regex with anchor and context constraints replaces phrase-only detection.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: NDB Scheme (Cth), SOCI Act 2018 (Cth), TIA Act 1979 (Cth), GDPR
Frameworks: CIS Controls, DISP, ISO 27001, NIST CSF, PCI-DSS, SOC 2
Data categories: credentials, security
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:support\s+ticket|ticket\s+transcript|help\s+desk|service\s+desk|case\s+number|ticket\s+ID|customer\s+complaint|resolution\s+notes|incident\s+ticket|support\s+request|ticket\s+history)\b

Corroborative evidence keywords

support ticket transcripts, support, ticket, transcripts, operations, resilience, student, transcript, grade, [object Object], enrollment, FERPA, FAFSA, financial aid, tuition, degree

Proximity: 300 characters

Should match

support ticket — Primary topic phrase match
ticket transcript — Case-insensitive topic phrase match
help desk — Alternative topic phrase match
service desk — Additional topic phrase match
Ticket ID=HD-771 09:14 Customer: VPN fails after MFA 09:16 Agent: Reset the device registration 09:22 Customer: Access restored — Ticket ID with three timestamped alternating requester/agent messages - the transcript shape that satisfies Evidence_ticket_transcript_turn for enforcement

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.

References

https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism
https://www.homeaffairs.gov.au/about-us/our-portfolios/emergency-management
https://www.disasterassist.gov.au/
https://www.oaic.gov.au/privacy/australian-privacy-principles-guidelines/chapter-11-app-11-security-of-personal-information