
Group related alerts into a case
and record the evidence for each verdict
Threat Correlator combines findings from Vulnerability Scanner and Behavioral Analyzer with SIEM and EDR alerts and STIX/TAXII threat intelligence. It groups related signals by host, account and time window. Each verdict records evidence, ATT&CK technique IDs, confidence and contradictory evidence. Actions such as isolation require approval.
Deployment consultationWe’ll confirm the scope and deployment environment during the consultation. Deployment guide
See the reasoning behind each verdict
in order
Evidence, reasoning, verdict, and recommended actions appear in order on one screen.
Each step links directly to the original logs so analysts can check the reasoning against the source records.
- Each piece of evidence links to its original log
- Map findings to ATT&CK technique IDs and OWASP LLM Top 10 categories
- Show evidence that contradicts the verdict as well
- EvidenceSandbox: Shadow copy deletion and mass encryption
- EvidenceScanner: Unpatched RCE vulnerability on the same host
- EvidenceT1490 + T1486 combination → Ransomware execution stage
- VerdictCRITICAL · Confidence 0.97
- RecommendationsHost isolation (awaiting analyst approval)
Alerts from the same attack
are grouped into one incident
Threat Correlator builds an incident timeline from alerts linked by host, account, and timing. Analysts can review the incident as a whole instead of opening hundreds of alerts individually. Broad correlation rules can group unrelated alerts, so tune the time window and rules to your environment.
- Show propagation paths in a graph of assets and accounts
- Automatically list affected hosts and accounts
- Assignees and action history sync with ServiceNow and Jira tickets.
T1566.00109:12
T120409:14
T149009:14
T102109:15
Rerun the assessment under the same conditions
and compare the results
The assessment record preserves the input, model version, and policy version. During an audit or follow-up review, rerun the assessment under the same conditions and compare the risk rating and rationale. Use the record hash to verify integrity.
- Use the record hash to verify the original log’s integrity
- Model and policy version history
- Audit logs are digitally signed and stored.
Original run 2026-11-07 09:159f3a…c21e
Re-run 2026-11-07 10:029f3a…c21e
Audit log signed✓
Key features
Cross-source correlation
Correlate scan findings and behavioral detections by host
Evidence chain
Evidence, reasoning, verdict, and recommended actions in one record
Attack technique mapping
MITRE ATT&CK technique ID, OWASP LLM Top 10
Policy-based response
Execute only approved actions through a SOAR platform such as Cortex XSOAR or through an EDR API
Reproducibility check
Rerun under the same conditions to compare verdicts
SIEM integration
Send verdicts back to your existing SIEM, such as Splunk or Sentinel
How it works
Receive
Engine results, SIEM and EDR alerts (API or Syslog), and STIX/TAXII feeds
Connection
Link signals by host, account, and time window
Reasoning
Map ATT&CK techniques and record the chain of evidence
Verdict
Calculate risk and confidence
Response
High-risk actions require approval before execution. Other actions follow the agreed policy.
Integration tools and methods
Integrations use APIs and syslog. We’ll confirm what each tool supports based on its version and your operating environment.
Deployment options
| Method | Description | Recommended |
|---|---|---|
| On-premises and isolated networks | The platform runs in your data center. Offline packages deliver detection rule and model updates so the platform can operate without an external connection. | Finance, public sector, and defense |
| Dedicated cloud | A dedicated environment serves one customer in a South Korean cloud region. | Enterprises and healthcare |
| Managed | In this MDR option, Genox handles security monitoring. We’ll confirm the scope and response procedures during the consultation. | Small and medium-sized businesses and mid-market companies |
| MSSP partners | The security service provider operates separate tenants for each customer. | Security service providers |
Frequently asked questions
How can I verify an AI verdict?
Compare the verdict rationale with the original evidence and use the record hash to check whether the original has changed. Review false positives and missed detections to improve the rules.
Do I need to replace my current SIEM?
You can keep your existing SIEM and detection rules. Threat Correlator receives alerts over an API or Syslog and sends its verdicts back to your SIEM and ticketing system.

Talk to us about Threat Correlator
Tell us about your operating environment, and we’ll explain what the demo and proof of concept can cover.