Intrusion detection alerts

Identifies intrusion detection alerts 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(?:intrusion\s+detection|network\s+intrusion|signature\s+rule|alert\s+threshold|packet\s+inspection|anomaly\s+detection|intrusion\s+prevention|network\s+monitoring)\b

Corroborative evidence keywords

intrusion detection alerts, intrusion, detection, alerts, security, operations, threat, data, student, transcript, grade, GPA, enrollment, FERPA, FAFSA, financial aid, tuition, degree, field, column (+27 more)

Proximity: 300 characters

Should match

• intrusion detection — Primary topic phrase match
• network intrusion — Case-insensitive topic phrase match
• signature rule — Alternative topic phrase match
• alert threshold — 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
• ids intrusion detection — 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.