Threat intelligence
Enrichment
Adding context to an alert or observable, such as asset owner, geolocation, reputation or WHOIS data, so analysts can judge it quickly.
Raw events carry little meaning: an IP, a hostname, a username. Enrichment joins them with internal context (asset inventory, owner, criticality, HR status, recent changes) and external context (reputation feeds, passive DNS, RDAP/WHOIS, certificate transparency, sandbox verdicts, geolocation and ASN).
Done in the pipeline, it makes detections smarter and triage faster; done in SOAR, it gathers evidence before a human looks. Cost and OPSEC matter: cache lookups, respect API quotas, and avoid submitting sensitive samples or querying attacker-controlled infrastructure in ways that tip them off.
Learn it properly
Compared
Also used in
- Linux logging basicsSecEng · Linux & OS security basicsFree
- KQL and SPL for investigationsAnalyst · Query & detection craftFree
- Regex and parsing for analystsAnalyst · Query & detection craftFree
- EPSS and exploit likelihoodAnalyst · Vulnerability triage & CVE prioritisationFree
- Building a patch-priority queueAnalyst · Vulnerability triage & CVE prioritisationFree
- Security logging architectureSecEng · Detection & Response EngineeringPro
- Detection as codeSecEng · Detection & Response EngineeringPro
- Incident response engineeringSecEng · Detection & Response EngineeringPro