Robots Atlas>ROBOTS ATLAS
Security & Privacy

IOC

ActivePublished: 17 November 2026Updated: 17 November 2026Published
Key innovation
Standardizing observable technical artifacts (such as file hashes, IP addresses or domains) as shareable "evidence" of an attack, enabling machine-driven detection and blocking of threats across many organizations.
Category
Security & Privacy
Abstraction level
Pojęcie
Operation level
Security operations
Use cases
Detecting and blocking known threats in SIEM/EDRThreat intelligence sharing between organizationsThreat hunting and retrospective log searchesPopulating reports (e.g. FBI FLASH) with STIX/CSV/JSON indicators

How it works

During incident or malware analysis, analysts extract observable artifacts (file hashes, C2 IP addresses/domains, URLs, registry keys, network artifacts) and describe them as IOCs. The indicators are encoded in structured formats (e.g. STIX) or simple lists (CSV/JSON) and disseminated through threat-intelligence sharing channels, including FBI FLASH reports. On the defender side, IOCs are loaded into SIEM, EDR, firewall and proxy systems, which compare current traffic and events against the indicator list, raising alerts or automatically blocking matches. Because IOCs are reactive (they describe known artifacts), attackers can evade them by changing infrastructure, so they are complemented by behavioural approaches (IOAs, TTPs).

Problem solved

Organizations need a common, portable way to describe what a given attack "looks like" so they can detect and block it without exposing sensitive victim details. IOCs provide such a shareable, machine-readable representation of a threat, allowing defence to scale across many entities and systems.