IOC
An observable artefact, such as a file hash, IP, domain or URL, that indicates a system may have been compromised.
IOCs are atomic or computed observables tied to known malicious activity: hashes of malware, C2 IPs and domains, URLs, mutex names, registry keys, email sender addresses, JA4 fingerprints. They are shared through feeds, reports and STIX/TAXII, and matched against telemetry for detection and retrospective sweeps.
They are fast to act on and easy to share, but they decay: attackers rotate infrastructure and recompile malware cheaply, and IPs get reassigned to innocent tenants. Every IOC needs context (source, confidence, first and last seen, associated campaign) and an expiry, or watch-lists fill with stale entries that cause false positives.
The pyramid of pain explains the limit: IOCs sit at the bottom; durable detection targets TTPs.
Learn it properly
Compared
Also used in
- Writing intelligence reportsAnalyst · Threat intelligence for analystsFree
- Forensics and evidence engineeringSecEng · Detection & Response EngineeringPro
- Ransomware responseAnalyst · Incident handling & reportingPro
- Writing incident reports for executivesAnalyst · Incident handling & reportingPro
- Building a safe triage labAnalyst · Malware analysis for respondersPro
- Static triage: hashes, strings, PE headers and YARAAnalyst · Malware analysis for respondersPro
- Dynamic and behavioural analysisAnalyst · Malware analysis for respondersPro
- Extracting and writing up IOCsAnalyst · Malware analysis for respondersPro