Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› What is the difference between indicators of compromise…
Cyber Security

What is the difference between indicators of compromise and tactics, techniques, and procedures?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 19, 2026 Domain: Cyber Security

Indicators of compromise are concrete artifacts observed in a known attack, such as IP addresses, hashes, domains, or suspicious emails. Tactics, techniques, and procedures describe the method and behavior behind the attack. IOCs are useful for confirmation, while TTPs help defenders understand recurring adversary patterns and build more resilient controls.

How IOCs and TTPs differ in practice

IOCs are the evidence trail you can match in logs, files, network traffic, or email. TTPs are the adversary's playbook, the repeatable behaviour that explains how the intrusion works and what it is trying to achieve. The practical difference is that IOCs help you confirm a known event, while TTPs help you recognise and disrupt the method behind it.

That distinction matters because IOC-based detection is often brittle. Indicators can be removed, replaced, or reused by unrelated actors, while TTPs persist longer and are more useful for detection engineering, threat hunting, and control design.

IOCs are usually specific and time-sensitive, for example hashes, domains, IPs, file paths, mutexes, or sender addresses. They are strongest when you already have a lead and want to verify exposure or search for signs of the same campaign. TTPs are broader and more durable, covering things like phishing delivery, credential theft, persistence, lateral movement, living-off-the-land activity, or exfiltration patterns. A single campaign may produce many IOCs but usually maps to a smaller set of TTPs.

Why TTPs outlast indicators of compromise

TTPs are more valuable for understanding the attacker's method because they describe behaviour, not just artifacts. A good TTP view lets defenders ask whether the same technique could be used again with different infrastructure or different malware, which is why Pyramid of Pain Guide remains a useful model for thinking about what kind of detection causes the most friction for an adversary.

This is also where a broader intelligence program matters. Threat Intelligence Guide is useful when teams need to separate tactical indicators from recurring adversary patterns and decide how to turn raw sightings into collection requirements, hunting hypotheses, and operational action.

In contrast, IOCs degrade quickly. An IP address may be blocked today and burned tomorrow, a hash may change with one rebuild, and a domain may be rotated after disclosure. TTPs remain useful because the method, such as credential harvesting followed by remote access and lateral movement, can persist even after the infrastructure changes.

How defenders should use both signals together

The strongest workflow is not IOC versus TTP, but IOC plus TTP. Start with indicators when you need fast confirmation, then use techniques and procedures to expand the search into related telemetry, adjacent hosts, and likely follow-on activity. If the IOC is only an artifact of a known campaign, it may point you to a wider set of compromised systems, but the TTP tells you where else to look.

That is why incident response teams often treat IOCs as search terms and TTPs as investigation logic. A hash can confirm a malicious file; the technique tells you whether the actor also used scheduled tasks, PowerShell, token theft, or outbound beaconing. The latter produces stronger detection content, better hunting queries, and more durable control improvements.

For teams building detections, the key question is whether the signal is meant to detect the same sample again or the same behaviour again. If it is the former, IOC logic may be enough. If it is the latter, you need TTP-led detection that survives infrastructure churn.

Risk and Threat Considerations

Overreliance on IOCs creates a narrow defence that adversaries can evade by changing infrastructure, recompiling tools, or abusing legitimate services. TTPs expose the reusable parts of an attack chain, which is what matters when the same method is repackaged with new tooling or new delivery paths.

Failure mechanism: Teams anchor detection on artifacts that are easy to burn, while missing the behavioural pattern that actually defines the intrusion. That leaves gaps in hunting, weak recurrence detection, and a false sense of containment after only the visible indicators are blocked.

Impact: The organisation may stop one sample but fail to recognise the next campaign using the same technique, allowing repeated compromise, slower eradication, and weaker control hardening.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKTactic/Technique Matrix — Adversary Tactics and TechniquesIOC vs TTP is fundamentally about adversary behavior and attack chaining.
Recommendation — Map observed activity to ATT&CK and hunt for the surrounding technique chain, not just the artifact.
NIST CSF 2.0DE.CM-01 — Monitoring for Anomalies and EventsIOCs and TTPs both feed continuous monitoring and threat detection decisions.
ID.RA-01 — Asset Vulnerabilities, Threats and Risks are Identified and RecordedTTPs inform threat and risk identification beyond single indicators.
PR.DS-07 — Integrity Checking MechanismsIOCs often rely on file, hash, and artifact integrity checks during verification.
Recommendation — Use anomaly and event monitoring to detect both known indicators and recurring behaviors. Record the technique patterns that could recur so risk decisions reflect attacker method, not just artifacts. Verify suspicious files and artifacts with integrity checks before treating them as trusted.
CIS Controls v8CIS-8 — Audit Log ManagementIOC and TTP hunting both depend on usable logs and telemetry.
Recommendation — Centralize and retain logs so IOC searches and TTP-based hunts can be performed reliably.

Practitioner Guidance

What to prioritise: Use IOCs to confirm exposure and TTPs to drive control changes. If a hunt only asks "have we seen this hash or domain," it is probably too narrow for durable defence.

What to verify: Check whether your detections are tied to mutable artifacts or to behavioural patterns that survive tool changes. Good coverage usually includes both, but behavioural logic should carry the higher long-term value.

Decision rule: If the threat is under active investigation, start with IOC searches for speed. If the question is how to prevent recurrence, shift quickly to TTP mapping and detection engineering.

Practitioner takeaway: IOCs help you find the known event; TTPs help you defend against the same adversary method when the evidence has changed.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org