Skip to main content

What is threat intelligence?

Threat intelligence is analyzed information about attackers, their methods, and their infrastructure that helps a SOC detect and prioritize threats.

Glossary
Updated 2 min read

Definition

Threat intelligence

Also called Cyber threat intelligence, CTI, Threat intel

Threat intelligence is information about threats and threat actors that has been collected, analyzed, and enriched with context so defenders can make decisions, such as what to detect, hunt for, patch, or block.

How it works

NIST defines cyber threat intelligence as threat information that has been aggregated, transformed, analyzed, interpreted, or enriched to provide the context needed for decision-making. NIST SP 800-150 lists the raw material: indicators such as malicious IPs, domains, and file hashes; tactics, techniques, and procedures that describe how actors behave; security alerts and advisories; threat intelligence reports; and tool configurations. Some uses are operational, like blocking an indicator, and some strategic, like planning major changes to defenses.

Intelligence arrives from vendor feeds, government advisories, information-sharing communities, open-source research, and your own investigations. Much of it is exchanged in STIX, which OASIS describes as a language and serialization format for exchanging CTI, over TAXII, a protocol for sharing it over HTTPS.

Shared intelligence usually carries handling rules. NIST SP 800-150 describes version 1.0 of the Traffic Light Protocol (TLP), whose labels tell recipients how far they may pass information on: TLP:RED is restricted to the participants in a specific exchange, TLP:AMBER to participants' organizations, TLP:GREEN to a wider community, and TLP:WHITE allows public disclosure. Respecting those labels is what keeps sharing communities willing to share.

Example

A vendor publishes research on a campaign exploiting a vulnerability in an ingress proxy. Intelligence work turns that into decisions: are we running the affected version, is the vulnerable feature enabled, do our logs show the exploit pattern, and what detection should watch for it? Cotool's hunt page shows this flow with an example: a CVE in Envoy's external authorization processing is scored for relevance and exposure against the customer's environment, and the output is patch-and-mitigate guidance and new detections rather than a report.

Why it matters for a SOC

Most intelligence a SOC receives is irrelevant to its environment, and the useful part only matters once it changes a detection, a hunt, or a patch priority. The hard step is filtering, not collecting more feeds. A quick relevance check for each item:

  • Does it target our industry, regions, or technology stack?
  • Do we run the affected product or version, and is it exposed?
  • Do our logs cover the behavior it describes, and for how far back?
  • Can it become a durable behavioral detection, or only short-lived indicators?

Items that pass become hunts, detections, or patch tickets with an owner. Some platforms now automate this step: on Cotool, agents crawl blogs, government databases, and disclosures, combine the results with customer feeds over STIX/TAXII, and investigate each item for relevance before it reaches a person.

Go deeper

Sources

  1. Cyber Threat Intelligence - Glossary | CSRC · accessed November 16, 2026
  2. NIST SP 800-150: Guide to Cyber Threat Information Sharing · accessed November 16, 2026
  3. Cyber Threat Intelligence Technical Committee | OASIS · accessed November 16, 2026
  4. AI Threat Hunting and Actionable Threat Intel | Cotool · accessed November 16, 2026

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo