Indicator of Compromise
Also called IOC.
Forensic breadcrumbs that a system was compromised.
What it is
An Indicator of Compromise is an observable artifact (a file hash, domain, IP, registry key, or filename) associated with malicious activity.
Why it matters
IOCs let teams sweep an environment for known-bad and share threat data, but they are brittle: attackers change them easily, which is why behavior-based detection has to complement them.
In practice
Searching every endpoint for a malware hash and C2 domain pulled from one infected host.
What to look for
- Hashes, IPs, domains, file paths and registry keys tied to a known intrusion.
- Indicators with a source, a date and the context they came from.
- Matches in historical logs, not only live traffic.
Common mistake
Treating indicators as permanent. Infrastructure moves quickly; age them out and pair them with behavior.
Use it in CyberKit
- Indicator Extractor
Pull every IOC out of a log or a report, then score the domains against published string heuristics.
- Report Generator
Write an incident report with a timeline, evidence and chain of custody, findings, indicators, ATT&CK mapping and queries. Export it as PDF, HTML or Markdown.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
MISP Open source
An open source platform for storing, correlating and sharing threat indicators.
-
OpenCTI Open source
Organizes intelligence as linked STIX objects, from actors down to indicators.
-
VirusTotal Commercial
Pivots between files, domains and IPs to find related infrastructure.
-
ATT&CK Navigator Open source
Shows a group's known techniques on the ATT&CK matrix.
ATT&CK techniques
- T1070: Indicator Removal
Tools practitioners use
Read next
- Pyramid of Pain: Ranks indicators by how much they hurt attackers to lose.
- Threat Hunting: Proactively searching for threats that evaded detection.
- MITRE ATT&CK: A public knowledge base of real adversary tactics and techniques.