Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is an Indicator of Compromise (IoC)?

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.

Illustration for the cybersecurity term Indicator of Compromise (IoC)
Home / Blog / Cybersecurity Terms / What Is an Indicator of Compromise (IoC)?
17 November 2026

What Is an Indicator of Compromise (IoC)?

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.

Common Types of IoC

CategoryExamplesTypical source
File-basedMD5, SHA-1, or SHA-256 hashes; file names; YARA matchesEDR, sandbox, malware analysis
NetworkIP addresses, domains, URLs, JA3/JA4 TLS fingerprints, unusual user agentsFirewall, proxy, DNS, IDS logs
HostRegistry run keys, scheduled tasks, new services, mutex namesEDR telemetry, Sysmon, Windows event logs
EmailSender addresses, subject lines, attachment hashes, header anomaliesSecure email gateway
AccountSign-ins from unexpected countries, new MFA devices, suspicious OAuth grantsIdentity provider logs

Not All Indicators Are Equal

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.

IoC Versus Indicator of Attack (IoA)

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.

How IoCs Are Shared

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.

Using IoCs Without Drowning in Them

Age Them Out

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.

Add Context

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.

Hunt Backwards

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.

Feed Findings Back

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.

FAQ – Frequently Asked Questions

Where Can I Find Reliable IoC Feeds?

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.

Why Do IoCs Cause So Many False Positives?

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.

Can Attackers Evade IoC-Based Detection?

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.

How Do IoCs Help During an Investigation?

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.

Related Terms

You May Be Interested In These

What Is Hospital Device Network Security?

Cybersecurity Terms

17 November 2026

What Is Hospital Device Network Security?

Read More
What Is e-Devlet Gateway Security?

Cybersecurity Terms

17 November 2026

What Is e-Devlet Gateway Security?

Read More
What Is a Zero-Day Vulnerability?

Cybersecurity Terms

17 November 2026

What Is a Zero-Day Vulnerability?

Read More