Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are the Types of Threat Intelligence?

Threat intelligence is usually split into strategic, operational, tactical, and technical. The levels differ by audience, shelf life, and the decision each one is meant to support.

Illustration for the cybersecurity term Types of Threat Intelligence
Home / Blog / Cybersecurity Terms / What Are the Types of Threat Intelligence?
17 November 2026

What Are the Types of Threat Intelligence?

What Are the Types of Threat Intelligence?

Threat intelligence is divided into levels because a chief financial officer and a detection engineer need different things from the same underlying knowledge. The usual split is strategic, operational, tactical, and technical, and the practical distinction between them is shelf life: a technical indicator may be worthless in a fortnight, while a strategic judgement about which actors target your industry holds for a year or more.

LevelAudienceAnswersTypical shelf life
StrategicBoard, executives, risk committeeWho threatens us and what should we fund?Months to years
OperationalSecurity leadership, incident responseWhat campaign is running and are we in scope?Weeks to months
TacticalDetection engineers, SOC, Red TeamHow do they operate and what should we detect?Months
TechnicalTooling, automated enforcementWhat exactly do we block or search for?Hours to weeks

Strategic Intelligence

Written in prose, free of jargon, and aimed at investment and risk decisions. It covers which actor groups have an interest in your industry, how threats are shifting, what regulatory and geopolitical change implies for exposure, and what a plausible worst case looks like in financial terms. Sources include national assessments such as the NCSC’s Annual Review, sector reporting, and your own incident history.

Strategic products fail when they are written by technical analysts for technical readers. A board paper that needs the reader to know what a loader is has not been written for its audience. Lead with the judgement and the recommendation; put the technical reasoning in an annexe.

Operational Intelligence

Operational intelligence concerns specific campaigns and imminent activity: an actively exploited vulnerability in a product you run, a ransomware group newly targeting your sector, a hacktivist campaign naming your industry next week. It answers whether you are in scope and what to do in the next few days, which makes timeliness its defining quality. This is the level that sector sharing through an ISAC or CiSP supplies better than generic commercial feeds, because relevance depends on who your peers are.

Tactical Intelligence

Tactical intelligence describes adversary behaviour: the tactics, techniques, and procedures an actor uses, mapped to MITRE ATT&CK. It outlives indicators because changing behaviour costs an attacker more than changing a domain. This is the most under-consumed level and the most valuable to a maturing team: a report stating that a group abuses a specific remote management tool for persistence yields a detection rule that stays useful for a year, where the accompanying hash list expires within days.

It also drives threat hunting hypotheses and gives a Red Team something realistic to emulate rather than generic attack paths.

Technical Intelligence

The machine layer: addresses, domains, hashes, URLs, certificate fingerprints, and the patterns that match them. It is consumed automatically, never read by a person, and decays fastest. Treated properly it is cheap and effective; treated as the whole of intelligence it produces the familiar failure of a team drowning in indicators and unable to say anything useful about the adversary. Technical material needs expiry dates, confidence scores, and honest quality measurement, or it becomes an outage waiting to happen.

Which Level to Build First

Most teams start with technical because it is the easiest to buy, and stall there. A better sequence starts with strategic—a short, honest assessment of who would target you and why—because it determines which operational and tactical collection is worth funding. From there, build tactical coverage of the three or four actor behaviours most relevant to your sector, automate technical ingestion, and add operational sharing through a sector community.

All four levels draw on the same intelligence lifecycle; they differ in who the product is for. If you cannot name the person who reads each of your outputs, you are producing reports rather than intelligence.

At Privia Security, we build intelligence programmes across all four levels through our SOC maturation services, starting from the decisions your stakeholders actually have to make.

FAQ – Frequently Asked Questions

What Is the Difference Between Operational and Tactical Intelligence?

Operational intelligence is about a specific campaign happening now: who is being targeted, with what, and whether you are in scope. Tactical intelligence is about durable behaviour: the techniques a group uses regardless of the current campaign. Operational drives immediate action such as emergency patching, while tactical drives detection engineering that remains valid for months.

Which Type Should a Small Security Team Prioritise?

Tactical, after a short strategic assessment of who plausibly targets you. Behaviour-based detections built from technique reporting keep working as attacker infrastructure changes, so a small team gets more return per hour than from managing indicator feeds. Automate technical ingestion so it costs nothing to maintain, and get operational awareness free through sector sharing.

Is Strategic Intelligence Worth It for a Mid-Sized Organisation?

Yes, in proportion. It need not be a glossy quarterly report: two pages a year naming the actors with a plausible interest in your business, what they would want, and what that implies for spending is enough to direct the rest of the programme. Without it, investment follows vendor marketing and whichever incident made the news most recently.

Do We Need Separate Products for Each Audience?

Yes. A single report written for everyone serves no one, because the board will not read the technical detail and engineers cannot act on the summary. Write a short assessment with a recommendation for executives, a technique write-up with detection logic for engineers, and push indicators straight into tooling where no human reads them at all.

Related Terms

You May Be Interested In These

What Is Terrascan?

Cybersecurity Terms

17 November 2026

What Is Terrascan?

Read More
What Is Server-Side Template Injection?

Cybersecurity Terms

17 November 2026

What Is Server-Side Template Injection?

Read More
What Is a Trusted Platform Module?

Cybersecurity Terms

17 November 2026

What Is a Trusted Platform Module?

Read More