Alerting Rules & Incident Lifecycle
Configuring precision detection rules, automated deduplication windows, severity routing, and the SOC alert lifecycle.
ThreatPurge provides a rule-based alerting engine with customizable severity thresholds, automated deduplication, auditable lifecycle tracking, and multi-channel incident dispatch.
The Alerting Rules Engine#
The Alerting Rules engine allows security teams to define precise conditions under which external findings trigger formal security alerts. Each rule links a Watchlist Category (e.g., Brand Names, Domain Names, Tech Stack) to a target detection module, enforcing a minimum severity threshold.
| Rule Property | Configuration Options | Operational Impact |
|---|---|---|
| Module & Category | ASM, Brand Abuse, Dark Web, Social Media, TPRM | Directs the rule to evaluate findings originating from specific detection engines. |
| Severity Threshold | Critical, High, Medium, Low | Findings below the selected threshold are archived as findings but do not create alert noise. |
| Schedule & Cadence | Interval (every 6h, 12h, 24h) or Cron (e.g., 0 2 * * *) | Controls how frequently the rule executes background sweeps against monitored watchlists. |
| Keyword Exclusions | Comma-separated list (e.g., official, partner, test) | Automatically ignores authorized domains or known benign terms to prevent false positives. |
Severity Levels & Rule Thresholds#
ThreatPurge assigns severity deterministically based on asset criticality, vulnerability exploitability, and weaponization context:
| Severity | Condition Criteria | Recommended SOC Response |
|---|---|---|
| Critical | Active weaponized exploit on internet-facing asset, executive credential leaked in stealer log, or active phishing site. | Immediate incident response, automated PagerDuty/Slack page, and urgent takedown. |
| High | High-severity CVE with available public exploit, exposed management port (RDP/SSH), or typosquat with configured mail exchanger. | Investigate within 4 hours, initiate firewall containment or registrar report. |
| Medium | Expiring SSL/TLS certificate, non-weaponized CVE with high CVSS, or unverified social media impersonator. | Triage during daily SOC shift; assign to IT or certificate team for remediation. |
| Low | Subdomain DNS configuration change, minor technology update, or general brand forum mention. | Review during weekly hygiene and posture audits. |
SOC Alert Lifecycle & Timestamps#
Every alert follows an auditable, four-state lifecycle designed to measure SOC operational performance (MTTD, MTTR, MTTC):
OPEN
Alert is newly created upon finding detection. The detected_at timestamp is permanently recorded.
IN_PROGRESS
An analyst assigns the alert or begins investigation. The responded_at timestamp is automatically captured.
RESOLVED
Vulnerability is remediated, domain taken down, or threat neutralized. The resolved_at timestamp is captured and financial Impact Avoided is calculated.
FALSE_POSITIVE
Alert is confirmed benign or authorized. An audit closure reason is required to maintain compliance fidelity.
Intelligent Deduplication#
Continuous 24/7 background scans could easily generate repetitive alert noise if the same exposure is detected on subsequent sweeps. ThreatPurge enforces a 24-hour sliding deduplication window per unique finding identity. Existing open alerts receive an updated timestamp rather than creating duplicate tickets.
Multi-Channel Alert Routing#
Alerts can be dispatched automatically to external systems configured in the Integration Centre. High-priority alerts can trigger PagerDuty on-call escalation, open tickets in Jira or ServiceNow, and publish rich alert notification cards into Slack or Microsoft Teams.
Related Documentation
Was this page helpful?
Your feedback helps us improve ThreatPurge technical documentation.