Skip to content
StrikeCyberStrikeCyber
Field Manual · Concept

Indicators of Compromise (IOCs)

Reviewed 14 November 2026Concept 2 min read

Quick answer

Indicators of compromise (IOCs) are pieces of evidence that a system may have been breached, such as a malicious IP address, domain, file hash or unusual account activity. Security teams match them against logs to find attackers. They are useful for known threats but easy for attackers to change, so they work best alongside detection of attacker behaviour.

On this page

When a new attack campaign is reported, the first question every security team asks is "were we hit?". Indicators of compromise are how that question gets answered.

01

How It Works

IOCs are shared by vendors, governments and researchers after an attack is analysed. Teams load them into their SIEM, EDR, firewall or threat intelligence platform, search historical logs for matches, and alert on future sightings.

TypeExampleHow long it stays useful
File hashThe SHA-256 of a malicious fileShort: one changed byte creates a new hash
IP addressA command and control serverShort: attackers rotate infrastructure
Domain or URLA phishing or malware download domainShort to medium
Email artefactsSender address, subject line, attachment nameShort
Host artefactsRegistry keys, scheduled tasks, services, file pathsMedium
Account activityLogins from unusual countries, new mailbox rulesMedium
Tools and behaviourUse of specific attack tools or techniquesLong: hardest for attackers to change
02

Why It Matters

IOCs give a fast, concrete answer after a public incident, and they are essential during incident response for scoping which systems were touched. Their weakness is that attackers change them easily, and targeted attacks often use infrastructure never seen before. Organisations that rely only on IOC feeds detect yesterday's attacks.

03

How to Test for It

  1. Check that IOC feeds actually reach your SIEM, EDR and firewalls, and that matches raise alerts.
  2. Confirm logs are retained long enough to search back when a new advisory is published.
  3. Run a retro-hunt exercise: take a recent public advisory and search your environment for its IOCs end to end, timing each step.
  4. Test behaviour-based detection with realistic techniques, since attackers in a targeted intrusion will not reuse public IOCs.
04

How to Reduce the Risk

Automate IOC ingestion from reputable sources, keep searchable logs for at least 90 days, and build a routine for retro-hunting when major advisories land. Invest equally in behaviour-based detection: the techniques attackers use are far harder for them to change than their infrastructure. Our threat intelligence and IOC feeds service supports both.

05

Regulatory and Framework Context

For Australian organisations, ASD's ACSC distributes IOCs through its partnership program and alerts, and the SOCI Act's cyber incident reporting obligations make rapid scoping of an incident, which depends on IOCs, a regulatory requirement for critical infrastructure.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

What is the difference between an IOC and an IOA?

An indicator of compromise (IOC) is evidence of something that has already happened, such as a known malicious file. An indicator of attack (IOA) describes attacker behaviour, such as credential dumping or a burst of logins across many hosts, and can catch new attacks that use unknown files and infrastructure.

Where do IOCs come from?

Vendor and government advisories, threat intelligence feeds, incident reports and information sharing groups. In Australia, ASD's ACSC shares IOCs with partners and publishes them in alerts.

What is the Pyramid of Pain?

A model showing that some indicators cost attackers more to change than others. File hashes and IP addresses are trivial to change; tools and tactics, techniques and procedures are hard to change, so detecting those hurts attackers most.

What should we do if we find an IOC in our logs?

Treat it as a possible incident: preserve evidence, scope which systems and accounts are involved, contain them, and engage incident response support if needed. Do not simply block the indicator and move on.

Change log

  1. 14 November 2026First published.
1300 654 898