Threat Detection
Goal
Detect known and unknown threats across all network layers, and give the security team the context needed to respond quickly.
How SentriaOne xSIEM supports it
| Capability | Contribution |
|---|---|
| Signature-based detection | Identifies known attacks, for example traffic matching an intrusion detection rule |
| ML and behavioural analytics | Identifies unknown or unusual activity, such as anomalous connections or data transfers |
| MITRE ATT&CK mapping | Places each detection in the context of attacker tactics and techniques |
| Incident Response | Tracks each detection from review to closure, with recommended mitigations |
Detections are grouped into categories such as C2, UEBA, Caution, Exfiltration, and Discovery.
Typical workflow
- Review new and high-risk detections on the Security Overview.
- Work through detections in Detections › Triage, highest risk first.
- Open each detection and verify what happened using its records, risk signals, and participant history. See Detection Details.
- Decide on an action using the MITRE ATT&CK mitigations, and record the outcome in Detection Tracking.
- Use Detections › MITRE Map to see which attack stages are observed over time.
Example scenarios
| Scenario | Where it appears |
|---|---|
| Exploitation attempt against a web server | Signature detection in the Caution category, with HTTP records as evidence |
| Internal host beaconing to an external server | C2 detection with regular connections to the same peer |
| Large or chunked uploads to cloud storage | Exfiltration detection with bytes-sent evidence |
| Internal host scanning many ports | Discovery detection |
Related pages
- How to analyze top affected internal IPs — a step-by-step example
- How to analyze a detection — analyzing a single detection in depth
- Incident Response
- Detection Tuning