Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An indicator of compromise (IoC) is a piece of forensic evidence—a file hash, IP address, domain, or registry key—that suggests a system or network has been breached.

What Is an Indicator of Compromise (IoC)?
An indicator of compromise (IoC) is an observable artefact that, with reasonable confidence, points to malicious activity on a system or network. Typical examples are the SHA-256 hash of a ransomware binary, the IP address of a command-and-control server, or a phishing domain registered last week.
IoCs are the shared vocabulary of detection. Threat intelligence reports publish them, SIEM and EDR platforms match against them, and incident responders use them to work out how far an intrusion has spread.
| Category | Examples | Typical source |
|---|---|---|
| File-based | MD5, SHA-1, or SHA-256 hashes; file names; YARA matches | EDR, sandbox, malware analysis |
| Network | IP addresses, domains, URLs, JA3/JA4 TLS fingerprints, unusual user agents | Firewall, proxy, DNS, IDS logs |
| Host | Registry run keys, scheduled tasks, new services, mutex names | EDR telemetry, Sysmon, Windows event logs |
| Sender addresses, subject lines, attachment hashes, header anomalies | Secure email gateway | |
| Account | Sign-ins from unexpected countries, new MFA devices, suspicious OAuth grants | Identity provider logs |
David Bianco’s Pyramid of Pain, published in 2013, ranks indicators by how much effort it costs an attacker when defenders block them. At the bottom sit hash values: change one byte of a file and the hash is useless. IP addresses and domains are a little higher but still cheap to replace. Further up come network and host artefacts, then tools, and at the top, tactics, techniques, and procedures (TTPs).
The lesson is not that hashes are worthless—they are precise and generate almost no false positives—but that a detection strategy built only on atomic indicators will always be one step behind. Mature SOC teams combine IoC matching with behaviour-based detection mapped to MITRE ATT&CK.
An IoC tells you something bad has already happened. An indicator of attack describes behaviour that signals an attack in progress, regardless of the specific file or infrastructure used—for example, Microsoft Word spawning PowerShell, which then makes an outbound connection. IoAs catch new variants and living-off-the-land techniques that leave few static artefacts behind. In practice, you need both.
Indicators are only useful if they reach defenders quickly and in a format machines can read. The main standards and tools are:
When FireEye disclosed the SolarWinds supply chain compromise in December 2020, it published indicators and detection rules on GitHub within days, which allowed thousands of organisations to hunt for SUNBURST activity in their own networks.
IP addresses get reassigned and domains get sinkholed. An indicator that was malicious six months ago may now belong to a legitimate cloud customer. Assign expiry dates and confidence scores, and retire stale data.
A bare IP address is far less useful than one tagged with the threat actor, campaign, first-seen date, and the ATT&CK technique it supports. Context decides whether an alert is a priority or noise.
New intelligence should trigger a retrospective search. If a domain is published today as malicious, check whether anyone resolved it in the past 90 days. This is where long log retention in your SIEM pays off.
During incident response, every confirmed artefact becomes a new IoC. Sharing them with sector peers through trusted communities strengthens everyone’s defences and often brings useful intelligence back in return.
At Privia Security, we help SOC teams turn threat intelligence into working detections through our SIEM solutions.
Start with free, high-quality sources: NCSC and CISA advisories, vendor threat research blogs, abuse.ch projects such as URLhaus and ThreatFox, and sector sharing communities running MISP. Commercial threat intelligence platforms add curation, context, and higher confidence scoring. Whatever you choose, measure each feed by how many true positives it produces in your environment, and drop sources that only add noise.
Many indicators point to shared infrastructure. A malicious site may sit behind a content delivery network used by thousands of legitimate services, and cloud IP addresses change owner frequently. Low-confidence feeds and indicators without expiry dates make the problem worse. Filtering against allowlists of known-good infrastructure, scoring confidence, and retiring old data reduce false positives considerably.
Yes, and easily at the lower levels. Recompiling malware changes its hash, and new domains cost very little. Sophisticated groups use unique infrastructure per victim precisely to defeat indicator sharing. That is why IoCs should be one layer among several, alongside behavioural analytics, threat hunting, and detections built around attacker techniques rather than specific artefacts.
Once responders identify one artefact, such as a malicious file hash or a command-and-control domain, they can sweep every endpoint and log source for the same indicator. This quickly reveals how many systems are affected, when the activity began, and whether data left the network. Each new finding produces further indicators, gradually building a complete picture of the intrusion.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.