Glossary Terms
What are indicators of compromise (IoCs)?
Indicators of compromise (IoCs, also written IOCs) are technical artifacts or observables, such as unusual outbound traffic, unexpected system file changes, or suspicious logins, that suggest an attack is imminent, underway, or has already happened. Security teams use them to detect an incident, work out its scope, and confirm what to clean up and restore.
Indicators of compromise at a glance
| What they are | Technical evidence that an attack is coming, is happening, or has happened |
| Also called | IoC, IOC (plural IoCs or IOCs) |
| Common types | Network, account and login, and host and file indicators |
| Where teams look for them | Event logs, extended detection and response (XDR) tools, and security information and event management (SIEM) systems |
| Who uses them | Security and IT teams during detection, response, and investigation after recovery |
| What they don’t do | Prevent an attack. They’re evidence, so they need monitoring and a response plan behind them |
| Related terms | Indicators of attack (IoAs), tactics, techniques, and procedures (TTPs), incident response plan |
NIST’s glossary defines an indicator of compromise as “technical artifacts or observables that suggest that an attack is imminent or is currently underway or that a compromise may have already occurred.” CISA’s shorter version is “clues and evidence of a data breach.”
What are examples of indicators of compromise?
Fortinet’s list of the most common indicators of compromise, grouped by type, looks like this.
| Type | Examples |
|---|---|
| Network | Unusual outbound traffic, mismatched port-application traffic, DNS request anomalies, and large numbers of requests for the same file |
| Account and login | Anomalies in privileged account activity, logins from countries where the organization doesn’t do business, many failed logins on one account, and failed logins for accounts that don’t exist |
| Host and file | Suspicious registry or system file changes, and sudden swells in database read volume |
One indicator on its own may have an innocent explanation, so teams compare what they see against a baseline of normal activity, which makes an attacker’s changes easier to spot.
What is the difference between IoCs and IoAs?
Indicators of attack (IoAs) describe attacker behavior rather than the traces it leaves. CISA’s glossary defines them as the behaviors a cybercriminal exhibits “prior to executing a cyberattack” and calls them “a dynamic profile of how an attacker interacts with your technologies and users.” Fortinet draws the line by timing: IoAs focus on activity “while the attack is happening, whereas IOCs focus on examining what happened after an attack has occurred.” NIST’s definition covers both timings, so sources draw the line between IoCs and IoAs in different places.
How are indicators of compromise used?
Security teams search for IoCs in event logs, XDR tools, and SIEM systems. During an attack, the team uses them to remove the threat and limit the damage. After recovery, as Microsoft explains, IoCs help the organization understand what happened so it can reduce the risk of a similar incident.
Why detection time matters for IT
IBM’s data breach explainer, citing its Cost of a Data Breach 2026 report, notes that “it takes an average of 247 days to identify and contain an active breach across all industries.” That figure shows how long a breach can run before it’s found and contained. That gap matters to IT as much as to security. Once an IoC confirms a compromise, the question becomes which restore point predates it, and a long gap before containment means looking back further than the most recent backups.
Best practices for managing indicators of compromise
- Establish a baseline of normal network, account, and file activity so changes stand out.
- Send logs from endpoints, servers, and cloud services to a system your security team can search.
- Write an incident response plan with named roles for detection, containment, and recovery, and test it.
- Keep backup versions long enough to reach a clean restore point, and keep copies separate from production systems, following the 3-2-1 backup rule.
- Preserve evidence from affected systems before wiping or rebuilding them, so the investigation can confirm the full scope.
How CrashPlan handles recovery after a compromise
CrashPlan is a backup and recovery platform for Microsoft 365, Entra ID, Google Workspace, endpoints, and servers, and its role starts once a compromise is confirmed. Backups of new and changed files and emails run automatically, and customizable version retention means that even if an infection isn’t discovered immediately, IT can return to a known-good state. Immutable backup storage prevents tampering with recoverable copies. For Entra ID, IT can compare the current environment with a historical backup to see which objects, policies, and relationships changed and need to be restored.
Indicators of compromise FAQ
What does IoC mean in cybersecurity?
IoC stands for indicator of compromise: a technical clue, such as a suspicious login or an unexpected file change, that suggests an attack is coming, underway, or has happened.
What is a common indicator of compromise?
Unusual outbound network traffic is one of the most common. Others include unusual activity on privileged accounts, logins from unexpected countries, and repeated failed logins.
What are TTPs and IoCs?
TTPs are an attacker’s tactics, techniques, and procedures: how they operate. IoCs are the traces those methods leave behind, such as files, log entries, or network traffic. CISA’s glossary notes that descriptions of common attack methods are often categorized by TTPs.
How can I spot IoCs?
Compare current activity against a known baseline, and review logs from your security tools for the examples above. Many teams use a SIEM or XDR tool to flag them, with an incident response plan that says who acts on each alert.
CrashPlan is the enterprise platform for resilient, secure, and cost-effective backup and recovery. Purpose-built to safeguard critical data across endpoints, servers, and SaaS applications, CrashPlan empowers organizations to maintain business continuity, meet compliance standards, and protect the ideas that drive growth—without disrupting end users. CrashPlan helps enterprises and institutions reduce storage costs with innovative storage strategies, like zero-cost backup to OneDrive, while maintaining control and visibility across their backup environment.
Privacy | Legal | Cookie Notice | Free Trial

