Operations → Security Operations
IOC
An observable artifact or pattern that may indicate malicious activity or a security compromise.
Motivation
IOC helps security teams reduce operational risk by making detection, investigation, and response more systematic.
Mental model
An IOC is evidence, not proof. Its value depends on context, freshness, confidence, and whether it can be connected to broader behavior.
Where it fits
IOC belongs to the Operations track, inside Security Operations. It complements preventive controls by helping teams observe and act on what happens in running environments.
Practical considerations
- Define ownership, escalation paths, and expected response times.
- Prefer high-quality, contextual signals over large volumes of unactionable alerts.
- Test procedures and automation before relying on them during an incident.
- Review outcomes and tune detections, tooling, and playbooks continuously.
Common mistakes
- Treating tooling as a substitute for clear processes and accountable owners.
- Collecting telemetry without retention, access, and investigation plans.
- Measuring alert volume instead of detection quality and response effectiveness.
Related concepts
Use the metadata panel or return to the graph to explore prerequisites and neighboring security operations concepts.