Cyber threat intelligence is one of the most misunderstood functions in security organizations. Many teams that claim a CTI practice are actually running an indicator-of-compromise (IOC) subscription service: consuming threat feeds, importing IP addresses and file hashes into SIEM blocklists, and calling it intelligence. This is to intelligence what weather data is to a weather forecast — raw material that has not been analyzed, contextualized, or made actionable. True intelligence answers questions that shape decisions: Who is likely to attack us? What are their objectives? How do they operate? What evidence would we see if they were already in our network? When is the next campaign likely?
The intelligence cycle provides the operational structure. Requirements definition — what questions need to be answered? — drives collection priorities. Collection gathers raw data from the sources most likely to answer those questions. Processing converts raw data into analyzable form. Analysis synthesizes processed data into assessments with defined confidence levels. Dissemination delivers finished intelligence to the consumers who need it. Feedback from consumers shapes the next iteration of requirements. Organizations that skip requirements definition and jump to collection typically end up with enormous volumes of data and no analytical process to convert it into decisions. The discipline is applied intelligence methodology, not data aggregation.
The strongest signal is not a single event. It is the pattern that keeps appearing across institutions.
Reporting Note
Strategic intelligence answers the highest-level questions about the threat landscape facing a specific organization. Which threat actor groups have historically targeted your industry, geography, and company size? What are their motivations — financial crime, economic espionage, sabotage, hacktivism? What capabilities have they demonstrated — ransomware deployment, data exfiltration, destructive attacks, supply chain compromise? What events trigger increased threat actor activity — major geopolitical developments, sector-wide regulatory changes, your organization's own public announcements like acquisitions or technology changes? Strategic intelligence is the input to security program investment decisions, threat modeling, and board-level risk communication. A financial services CISO who knows that FIN7 and Carbanak are the financially motivated groups historically most active against their sector can make better investment decisions than one operating with generic threat landscape awareness.
Open Source Intelligence (OSINT) is the foundation layer. OSINT sources are extraordinarily rich — most people dramatically underestimate how much actionable threat intelligence is publicly available. Security researchers and companies publish detailed technical reports on threat actor campaigns, including TTPs, tools, infrastructure, and victimology. Vendor threat intelligence reports from Mandiant (now part of Google Cloud), CrowdStrike, Microsoft, Recorded Future, and others are publicly available and represent synthesized analysis of significant campaigns. CISA and the FBI publish Joint Cybersecurity Advisories when they have sufficient attribution confidence and public benefit from disclosure. Academic institutions publish research on threat actor techniques. Court documents in US Department of Justice indictments against threat actors contain remarkably detailed technical information — the indictment of Chinese PLA Unit 61398 (APT1) published by Mandiant and the subsequent DOJ indictments against GRU officers (APT28) contain extensive technical indicators and TTP documentation.
Dark web monitoring provides visibility into threat actor communications that OSINT alone cannot access. Criminal forums, ransomware group websites on .onion domains, paste sites, and encrypted messaging channels where cybercriminals communicate contain information about active campaigns, leaked credentials, zero-day vulnerabilities before public disclosure, and threat actor planning. Commercial dark web monitoring services — including Recorded Future, Flashpoint, Intel 471, and Digital Shadows (now ReliaQuest) — operate collections programs that systematically monitor these sources and surface relevant findings. Effective dark web monitoring is not keyword searching; it requires human analysts who understand the social dynamics of criminal communities, can distinguish credible claims from roleplay, and can contextualize findings against the organization's threat profile. A post advertising access to a network matching your organization's industry and location requires immediate investigation; a generic claim of 'hacking Fortune 500 companies' does not.
MISP (Malware Information Sharing Platform) and STIX/TAXII constitute the technical infrastructure for IOC sharing between organizations. MISP is an open-source threat intelligence platform that allows organizations to create, store, and share threat intelligence in a structured format. STIX (Structured Threat Information eXpression) is the data format; TAXII (Trusted Automated eXchange of Intelligence Information) is the transport protocol. ISACs (Information Sharing and Analysis Centers) operate STIX/TAXII feeds for specific sectors — FS-ISAC for financial services, H-ISAC for health, E-ISAC for energy, A-ISAC for aviation. Sharing IOCs through these channels enables rapid dissemination: an IOC identified in one financial institution's environment reaches peer institutions within minutes. The limitation is well understood: IOCs are perishable. IP addresses used for C2 change within hours or days. Domain names are rotated constantly. File hashes are trivially modified. An IOC-centric intelligence program always fights the last battle.
Attribution is the most difficult and consequential intelligence function. Determining with reasonable confidence which threat actor conducted a specific attack requires correlating evidence across multiple dimensions: TTPs (which tools and techniques match the known behavior of which group?), infrastructure (which hosting providers, AS numbers, and IP ranges are associated with which actors?), tooling (which specific versions of malware or which custom tools are characteristic of which groups?), timing patterns (do operational hours align with any known actor's time zone?), victimology (does this target fit the known targeting profile of any group?), and language artifacts (do compile-path artifacts, error messages, or comments reveal language patterns?). The intelligence community applies formal confidence levels — assessed with high/moderate/low confidence — to attribution judgments. Public attribution statements from vendors frequently overstate confidence; the intelligence underpinning the attribution is often ambiguous.
Nation-state actors deliberately complicate attribution. Russia's GRU has been documented using Chinese APT tools in some operations. North Korea's Lazarus Group operations in cryptocurrency theft have used infrastructure and tools associated with other actor groups. The US and UK attribution of specific GRU officers by name in public indictments required years of intelligence collection across multiple intelligence agencies. Commercial threat intelligence companies operating without government intelligence access must be appropriately humble about attribution certainty. The practical value of attribution for most organizations is not legal or diplomatic — it is operational: if a group attributed to attack you with a high-confidence assessment matches a known threat actor's profile, that actor's known TTPs can guide detection tuning and hunting hypothesis development.
Threat hunting uses intelligence to search for active compromise proactively rather than waiting for automated alerts to fire. A structured hunting program begins with intelligence-informed hypotheses: 'Based on current intelligence about APT29 targeting Western government contractors, we hypothesize they may have used spearphishing with trojanized documents to establish initial access in the last 90 days. We will search our endpoint telemetry for the specific document loading behaviors and PowerShell execution patterns associated with their known tooling.' The hunter then queries endpoint telemetry, network logs, and authentication records looking for evidence consistent with the hypothesis. Most hunts find nothing — which is itself informative, validating that no evidence of that specific technique exists. Occasionally a hunt finds active compromise, enabling response before the attacker achieves their objective.
The MITRE ATT&CK framework provides the shared vocabulary that makes hunting hypotheses precise and reproducible. ATT&CK documents 14 tactics (the adversary's high-level goals — Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Credential Access, Discovery, Lateral Movement, Collection, Command and Control, Exfiltration, Impact) and hundreds of specific techniques with sub-techniques. Each technique includes detection guidance: which data sources to query, what events to look for. ATT&CK Navigator allows teams to visualize which techniques they have detection coverage for and which represent gaps. Intelligence reports that map adversary activity to ATT&CK techniques enable hunters to translate threat actor behavior directly into hunting queries against their telemetry.
Predictive intelligence is the highest-value capability and the hardest to develop. Predictive CTI answers questions before attacks occur: 'Which vulnerabilities that were disclosed in the last two weeks are most likely to be weaponized against organizations in our sector in the next 30 days?' 'Which threat actor groups are likely to target our industry given the current geopolitical situation?' 'What attack campaigns are threat actors discussing on underground forums that haven't launched yet?' The inputs to predictive intelligence include vulnerability disclosure monitoring (particularly for vulnerabilities in widely-used software with proof-of-concept code available), threat actor operational pattern analysis, geopolitical event tracking, dark web collection, and historical analysis of actor behavior patterns. Exploit Prediction Scoring System (EPSS) provides a machine learning model that predicts the probability a CVE will be exploited in the wild within 30 days — correlating with actual exploitation data from threat intelligence feeds.
Intelligence-as-a-Service has become a realistic option for organizations that lack the resources to build internal CTI programs. Vendors including Recorded Future, Mandiant Advantage, CrowdStrike Falcon Intelligence, and Secureworks Taegis provide finished intelligence products, IOC feeds, actor profiles, and analyst access through subscription services. The value proposition is access to collection sources and analytical expertise that would cost tens of millions of dollars to replicate internally. The limitation is that external intelligence is necessarily generic — it cannot account for the specific context of an individual organization's threat profile, technology environment, and business context that makes intelligence truly actionable.
Internal CTI programs require distinct skills that are scarce in the security market. CTI analysts need intelligence tradecraft training — structured analytical techniques, source evaluation methodology, confidence calibration. They need technical depth to understand and evaluate technical reports. They need geopolitical and criminal ecosystem knowledge to contextualize actor behavior. They need writing skills to communicate complex, uncertainty-laden assessments clearly to non-technical audiences. SANS FOR578 (Cyber Threat Intelligence) and the CTI training from the Cyber Threat Alliance provide the structured curriculum that most organizations use to develop internal CTI capability. The field is maturing, with the first dedicated CTI practitioner certifications now available.
The operational reality of making intelligence actionable is where most CTI programs struggle. Producing technically excellent intelligence reports that analysts read and appreciate is not the same as changing behavior and improving defenses. Actionable intelligence must reach the right consumers in a format they can use: detection engineers need ATT&CK-mapped hunting queries, not narrative prose; incident responders need IOCs in SIEM-importable formats, not PDF appendices; executives need risk-quantified assessments, not technical jargon. The measurement question — is our CTI program actually improving our security posture? — requires tracking whether intelligence products led to detection rule changes, hunting programs, or hardening actions, and whether those changes had measurable impact on detection rates or response times. CTI programs that cannot demonstrate this chain of impact from intelligence to outcome are ripe for budget scrutiny.
The future of CTI involves AI augmentation of analyst workflows rather than AI replacement of human judgment. LLMs can process enormous volumes of unstructured threat intelligence reports and extract structured TTP information, enabling analysts to synthesize more intelligence faster. Machine learning models can correlate infrastructure across campaigns — linking IP addresses, domains, SSL certificates, and server configurations associated with known actors to identify new infrastructure before it is used in attacks. Graph analysis of threat actor relationships and infrastructure can surface hidden connections between campaigns attributed to different actor groups. But the judgment required to assess attribution confidence, to evaluate source credibility, and to make the leap from intelligence assessment to operational recommendation requires human expertise that cannot be automated with current technology.
The forces behind this story have been building across several reporting cycles. What looks sudden on the surface is often the result of delayed investment, weak coordination, and incentives that rewarded short-term efficiency.
The next phase will be measured less by announcements and more by capacity: who can fund the response, who can execute it, and who absorbs the cost when older assumptions stop working.
The pressure is moving from headlines into systems.
A single event can be dismissed as noise. Repeated stress across contracts, public agencies, infrastructure, and household decisions becomes a structural story. That is why this analysis tracks both the visible development and the slower institutional response behind it.
Whether institutions respond with durable policy or temporary statements.
How quickly markets, cities, and public systems adjust to the next visible pressure point.
Which signals repeat across multiple regions instead of staying isolated to one event.
Story Type
Analysis
Primary Desk
Cyber Intelligence
Reader Use
Context and follow-up
Update Path
Related briefings
The useful question is not only what changed, but who is prepared to operate as if the change is permanent.
Aman Anil
Founder & Polymath
Aman Anil connects research, climate exposure, public policy, technology, and the financial systems responding to scientific change.
Have context, a correction, or a follow-up?
Send article notes, correction details, or additional source context to the editorial inbox. Include the article title and only the essential information needed for the inquiry.
