What are indicators of compromise (IOCs)?
Indicators of compromise are artifacts such as file hashes, IP addresses, and domains that show an attack happened or is underway.
Definition
Indicators of compromise
Also called IOC, IoC, Indicator of compromise
Indicators of compromise (IOCs) are technical artifacts, such as file hashes, IP addresses, domain names, and URLs, that suggest an attack is underway or that a system has already been compromised.
How it works
NIST SP 800-150 defines indicators as technical artifacts or observables that suggest an attack is imminent, underway, or that a compromise may already have occurred. Its examples: the IP address of a suspected command-and-control server, a suspicious DNS domain, a URL that references malicious content, a file hash for a malicious executable, or the subject line of a malicious email.
IOCs come from incident investigations, vendor reports, government advisories, and threat intelligence feeds, usually in machine-readable formats such as STIX. Security tools match them against logs and endpoint data: a SIEM searches proxy and DNS logs for listed domains, an EDR checks file hashes, and a YARA rule scans files for byte patterns.
Example
A vendor publishes a report on a ransomware group with the hash of its loader and the domains of its command-and-control servers. An analyst searches the last several weeks of DNS logs for those domains and finds one laptop that resolved one of them. That hit starts an investigation even though no alert fired at the time.
Why it matters for a SOC
IOCs are fast to act on and easy to share, which makes them the common currency of threat intelligence. They are also the easiest thing for an attacker to change. David Bianco's Pyramid of Pain ranks indicator types by how much it costs an adversary when you detect them: hash values, IP addresses, and domain names sit at the bottom, and tactics, techniques, and procedures sit at the top, because detecting behavior forces the attacker to change how they operate, not just swap infrastructure.
A SOC uses IOCs for quick sweeps and retroactive searches after new intelligence lands, and relies on behavioral detections for durable coverage. Retroactive sweeps only work if the relevant logs were kept long enough to search.
Related terms
- TTPsTTPs (tactics, techniques, and procedures) describe how an attacker behaves, from the high-level goal of an action (tactic) to the method used to reach it (technique) to the specific way a particular actor carries it out (procedure).
- Threat intelligenceThreat intelligence is information about threats and threat actors that has been collected, analyzed, and enriched with context so defenders can make decisions, such as what to detect, hunt for, patch, or block.
- YARA rulesYARA rules are pattern-matching descriptions of malware or other files, made of text, hexadecimal, or regular expression strings plus a Boolean condition, that the open-source YARA tool uses to identify and classify matching files.
- Command and control (C2)Command and control (C2) is the communication channel attackers use to send instructions to systems they have compromised and receive results, usually disguised to look like normal network traffic.
Go deeper
FAQ
- What is the difference between an IOC and an IOA?
- An IOC is evidence that something malicious already happened, such as a known-bad hash on disk. An indicator of attack (IOA) describes behavior in progress, such as a document spawning a script that dumps credentials, and doesn't depend on recognizing a specific file or address.
Sources
- NIST SP 800-150: Guide to Cyber Threat Information Sharing · accessed November 16, 2026
- The Pyramid of Pain (David Bianco) · accessed November 16, 2026
