1. TTPs & IOCs
Analysts track an adversary's tactics, techniques, and procedures (TTPs) plus their infrastructure as indicators of compromise (IOCs).
# track TTPs and infrastructure (IOCs)Typorithm · hard
Step 1 of 8 · intro card
Dark Web & Breach Intel
Threat-intelligence analysts track adversary groups — their tactics and techniques (TTPs), their infrastructure (IOCs), and their aliases across forums — and attribute behavior using MITRE ATT&CK. The output feeds detection rules and proactive defense.
Tracking an adversary starts with behavior and infrastructure. TTPs capture how a group operates; IOCs (domains, IPs, hashes) capture the artifacts they leave behind. Together they form a profile that persists even as surface details change.
Adversaries operate under shifting aliases across forums and channels. Mapping those handles to one another lets analysts attribute disparate activity to a single group and build a coherent picture over time.
MITRE ATT&CK provides a common framework for describing and attributing techniques, so findings are comparable across teams. Crucially, the intelligence loop closes only when those findings feed detection rules and proactive defenses — observation that never improves your detections is wasted effort.
Track TTPs (behavior) and IOCs (infrastructure artifacts).
Map aliases to attribute activity to one group.
Use MITRE ATT&CK to describe and feed detections.
# track TTPs and infrastructure (IOCs)
# map aliases across forums
# attribute behavior via MITRE ATT&CK
# feed findings into detectionsConnect each part of the code to the concept before you type.
Analysts track an adversary's tactics, techniques, and procedures (TTPs) plus their infrastructure as indicators of compromise (IOCs).
# track TTPs and infrastructure (IOCs)Actors use different handles in different places; mapping aliases links activity to a single group.
# map aliases across forumsMITRE ATT&CK gives a shared vocabulary to describe and attribute observed behavior to known techniques.
# attribute behavior via MITRE ATT&CKIntelligence is only useful when it drives action — findings become detection rules and proactive defenses.
# feed findings into detectionsRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.