Join our Newsletter — 33% off our NHI Course
Home› Guides› Strategic vs Operational vs Tactical Threat Intelligence: Audiences,…
Guide Threat Intelligence & Threat Actors

Strategic vs Operational vs Tactical Threat Intelligence: Audiences, Outputs and Metrics

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 13 min read
On this page

Most threat intelligence programmes say they serve three levels, then spend nearly all their effort on indicator feeds that only a firewall reads. Strategic, operational and tactical intelligence (with technical intelligence often split out or folded into tactical) differ in who acts on them, what decision they change, where their evidence comes from and how you prove they worked. This guide compares the levels side by side: the audience and output for each, the sources that feed it, the metrics that show value, the ways each level fails, and a worked example of one threat carried through all of them. It is for CTI leads, CISOs and SOC managers designing or rebalancing a programme. For the overall discipline see the Threat Intelligence Guide, and for the writing itself see Writing Threat Intelligence Reports.

Key takeaways

  • The level is set by the decision, not the subject. The same ransomware campaign is strategic when it changes investment, operational when it changes this week's priorities, and tactical when it changes a detection or a hardening setting.
  • Definitions vary, so write yours down. The MWR, CPNI and CERT-UK framework defines operational intelligence as actionable information on specific incoming attacks, while many teams use the word for campaign and actor tracking; agree one meaning before setting metrics.
  • Each level has its own sources and shelf life. Strategic work leans on geopolitical, regulatory and open source analysis; tactical work on incident, malware and campaign reports; technical indicators on feeds that age in hours to weeks.
  • Measure outcomes per level. The same framework suggests accuracy, impact and timeliness for strategic, forecast and mitigation for operational, defensive changes for tactical and prevented attacks for technical; volume metrics measure none of these.
  • The two classic failures mirror each other. IOC-only programmes never reach a decision maker, and executive-only programmes never reach a control; a balanced programme carries each finding down and up the levels.

The levels side by side

The table follows the four-level model in the MWR InfoSecurity paper produced with CPNI and CERT-UK, which remains the most cited UK framing, with the decision each level supports made explicit.

DimensionStrategicOperationalTacticalTechnical
Primary audienceBoard, executives, CISO, risk committeeSecurity managers, heads of incident response, SOC leadsArchitects, administrators, detection engineers, incident analystsMachines: SIEM, EDR, firewall, email and DNS controls
Decision it changesInvestment, risk appetite, strategy, disclosure readinessShort-term priorities, staffing, readiness for a specific threatDetections, hardening, architecture, hunt plansBlock, alert or enrich
Typical outputsAnnual or quarterly threat assessment, sector briefings, risk scenario inputsWarnings, campaign and actor updates, pre-event briefingsTTP analyses mapped to ATT&CK, detection requirements, hardening adviceIndicator sets with expiry, rule files
FormProse on business impact, little technical detailShort alerts with who, what, when and confidenceTechnique packs, procedures, data sourcesStructured data (STIX, CSV, vendor formats)
Time horizonMonths to yearsDays to weeksMonths (behaviour changes slowly)Hours to weeks
Main risk if absentSecurity spend disconnected from threatSurprise by a predictable eventControls that miss how attackers actually operateKnown-bad infrastructure not blocked

Note on terms: the MWR framework uses operational for forewarning of specific attacks, and notes such intelligence is rare for private organisations and often needs government-level access for state threats. Many programmes instead call campaign and actor tracking operational. Either is workable; mixing them makes requirements and metrics incoherent. This guide uses operational for threats active now against organisations like yours, including specific forewarning when it exists.

Strategic intelligence in depth

  • Threat model it serves: which actor types and motivations matter to the business over the next one to three years, and how geopolitics, regulation and technology change shift them.
  • Architecture in words: a small analyst cell holds the priority intelligence requirements (PIRs) agreed with executives, collects broadly, writes assessments, and feeds the enterprise risk register and budget cycle.
  • Sources: government and agency assessments (for example the annual ENISA Threat Landscape, whose 2026 edition covers 1 January to 31 December 2025), regulator publications, sector ISAC reporting, vendor annual reports, press and trusted peers. The MWR paper observes that open source material often supplies most of the content in mixed-source reports and that purchased analysis should be treated as collected material, not finished judgement.
  • Tradecraft: estimative language matters most here. ODNI ICD 203 sets nine analytic tradecraft standards and a fixed likelihood scale (for example likely 55 to 80 per cent, very likely 80 to 95 per cent) and separates likelihood from confidence.
  • Controls it drives: risk scenarios, cyber insurance assumptions, programme priorities and tabletop themes. See the Cyber Risk Quantification Guide and the Board Cyber Risk Reporting Guide.
  • Failure modes: generic trend summaries copied from vendor reports; technical detail the board cannot use; no explicit ask; judgements never revisited.

Operational intelligence in depth

  • Threat model it serves: campaigns, actors and events likely to affect the organisation in the coming days or weeks: a ransomware group targeting your sector's edge devices, hacktivist activity around a public event, a newly exploited vulnerability in a product you run.
  • Architecture in words: analysts monitor a watchlist tied to PIRs, triage reporting daily, and issue short warnings to security leadership and incident response with a recommended action and owner.
  • Sources: ISAC and peer channels, government alerts (for example machine-readable indicators and defensive measures from CISA's Automated Indicator Sharing, offered at no cost over TAXII 2.1), vendor campaign reporting, monitoring of hacktivist and criminal channels where legal and approved, and real-world events that trigger attacks.
  • Controls it drives: temporary heightened monitoring, emergency patching, help desk procedure tightening, incident response readiness. See the ISACs and Information Sharing Communities Guide.
  • Failure modes: alert fatigue from forwarding every vendor bulletin; warnings without an owner or action; no record of whether a forecast came true.

Tactical (and technical) intelligence in depth

  • Threat model it serves: how relevant adversaries actually operate: initial access, credential abuse, persistence, lateral movement and impact, expressed as ATT&CK techniques such as T1078 Valid Accounts, T1133 External Remote Services and T1486 Data Encrypted for Impact.
  • Architecture in words: analysts convert reporting into technique-level requirements; detection engineers turn them into analytics and test cases; architects turn them into hardening; hunters use them as hypotheses. Technical indicators flow separately and automatically into controls with expiry dates.
  • Sources: actor and campaign reports, malware analysis, your own incident reports, red team findings and MITRE ATT&CK. For indicators: paid and free feeds, government sharing programmes and internal investigations.
  • Controls it drives: detection backlog, coverage mapping, hardening baselines and hunts. See the Detection Engineering Guide and the Threat Hunting Guide.
  • Failure modes: technique lists with no procedure detail; indicators without expiry; volume chasing. The MWR paper reports feed overlap as low as 1 per cent and notes attackers change hashes and IP addresses easily, which is why over-investment in indicators is inefficient. See the Pyramid of Pain Guide.

Sources by level

Source typeStrategicOperationalTacticalTechnical
Government and agency assessmentsPrimaryAlerts and advisoriesTechnique detail in advisoriesIndicator annexes, AIS
Sector ISACs and peersSector trendsPrimaryShared incident write-upsShared indicators
Vendor research reportsAnnual trend reportsCampaign reportingPrimaryReport appendices
Internal incidents and huntsAggregated lessonsCurrent activityPrimaryPrimary
Commercial and open feedsRarely usefulContextContextPrimary
Geopolitical and regulatory analysisPrimaryEvent triggersRarely usefulNot used

For choosing between feeds and finished reporting, see Threat Feeds vs Finished Intelligence and Open-Source vs Commercial Threat Intelligence.

Worked scenario: one threat through every level

A financial services firm's CTI team sees repeated reporting that an extortion group gains access by calling IT help desks, impersonating staff to reset multi-factor authentication, then abusing remote access and SaaS consoles.

  1. Technical: phone numbers, domains used for look-alike login pages and infrastructure addresses go to email, DNS and proxy controls with a 30-day expiry. Useful, but short-lived.
  2. Tactical: analysts map the behaviour to T1566.004 Spearphishing Voice, T1621 Multi-Factor Authentication Request Generation and T1078 Valid Accounts, then raise detection requirements (MFA device registration after a help desk reset, first-time console access from new devices) and a hardening request for stronger caller verification.
  3. Operational: a two-paragraph warning to the head of service desk and the incident response lead: the group is active against peers this month, confidence moderate, action is to switch to call-back verification for privileged accounts this week.
  4. Strategic: a one-page note to the executive risk committee: social engineering of support processes is a likely route to a material incident over the next year, the firm's identity verification relies on knowledge-based questions, and the ask is funding for phishing-resistant authentication and verified reset workflows.
  5. Feedback: detections fire once in a test; the service desk logs two blocked attempts; the committee approves funding. Each outcome is recorded against the level's metric.

The identity angle is often the actionable core: reset procedures, MFA enrolment and privileged account controls are where intelligence turns into a change. See the Threat Intelligence for Identity and NHI Guide.

Metrics per level

LevelOutcome metricSupporting measureAvoid as a headline
StrategicDecisions or risk register entries changed by an assessment per yearJudgements later confirmed or revised, with reasonNumber of reports published
OperationalWarnings issued before the event that led to action in timeMedian time from credible report to warning; actions closed by ownersBulletins forwarded
TacticalDetections or hardening changes delivered from intelligence requirementsATT&CK coverage for prioritised techniques; hunts seeded by CTITechniques listed in reports
TechnicalBlocks or alerts on intelligence-sourced indicators that led to confirmed findingsFalse positive rate; share of indicators expired on timeIndicators ingested

These follow the evaluation logic in the MWR paper (accuracy, impact and timeliness for strategic work; forecast and timely mitigation for operational; informing defences for tactical; prevented attacks for technical). For a fuller set see the Threat Intelligence Programme Metrics Guide.

Decision guidance: where to invest

  • Small organisations (no dedicated analyst): buy technical intelligence through existing EDR, email and MDR services; get operational warnings from an ISAC and government alerts; produce a short strategic note once or twice a year with help from peers or a provider. Do not build an indicator pipeline you cannot maintain.
  • Mid-sized organisations (one to three analysts): put most analyst time into tactical work that feeds detection and hardening, automate technical indicators, and run a quarterly strategic briefing tied to the risk register.
  • Large or regulated organisations: staff each level explicitly, with a named consumer for every product. Expect strategic work to need analysts who can write for executives, not only technical specialists.
  • Outsourced or managed intelligence: a provider can supply technical feeds and much of the tactical reporting, but strategic relevance depends on knowing your business, assets and risk appetite. Keep PIR ownership and the strategic note in-house even when collection is bought, and require the provider to map its reporting to your PIRs.
  • Hand-offs between levels: name who moves a finding up or down. Detection engineers should flag when a tactical pattern deserves an operational warning; the CISO's office should push strategic decisions back down as new collection requirements. Without named hand-offs each level becomes a separate silo with its own reporting rhythm.
  • Trade-off: technical intelligence is easiest to buy and measure but has the shortest life; strategic intelligence is hardest to measure but changes the most money. Balance by consumer demand, not by what tools produce.

How to implement or rebalance the levels

  1. Inventory consumers: list every person or system that receives intelligence, what decision they make with it and how often.
  2. Write PIRs per level: three to five strategic questions from executives, a watchlist for operational tracking, technique priorities for tactical work, and acceptance criteria for indicator sources.
  3. Define products: one template per level with length, cadence, TLP default and owner. See the Threat Intelligence Report Template.
  4. Pilot one quarter: run each product with one consumer group, collect feedback after every delivery and record decisions taken.
  5. Automate the technical layer: enforce expiry, warning lists and confidence thresholds so analysts spend time on the other levels.
  6. Review and roll back: drop products no consumer used in two cycles, and re-scope PIRs at least annually and after major business change.

Common failure patterns

  • IOC-only programme: the team's output is a feed into the SIEM, so no person changes a decision and the programme looks like a cost centre. Add tactical requirements and a strategic note derived from the same reporting.
  • No executive translation: board packs list actor names and technique IDs instead of business consequence and an ask. Lead with impact, likelihood using a fixed scale, and the decision needed. See the Threat Intelligence Executive Briefing.
  • Collection-led programme: buying whatever vendors offer without requirements, which the MWR paper identifies as rarely delivering significant value.
  • Blended requirements: a single request that mixes strategic and technical needs ("tell us everything about ransomware") that no product can satisfy. Split it by level.
  • Operational without memory: warnings issued but never scored, so the team cannot show whether forecasts were right or acted on.
  • Tactical without engineering: technique reports that never become detections because no detection engineer owns the requirement.

Framework mapping

FrameworkReferenceLevel most served
NIST CSF 2.0ID.RA-02 (CTI received from sharing forums and sources)All, especially operational and technical
NIST CSF 2.0ID.RA-03 (internal and external threats identified and recorded)Strategic
NIST CSF 2.0DE.AE-07 (CTI integrated into analysis)Tactical and technical
NIST CSF 2.0GV.OV-01 (strategy outcomes reviewed to adjust direction)Strategic
NIST SP 800-53 Rev 5PM-16 Threat Awareness Program; SI-5 Security Alerts, Advisories, and DirectivesStrategic and operational
NIST SP 800-53 Rev 5RA-3 Risk Assessment; RA-10 Threat HuntingStrategic; tactical
ISO/IEC 27001:2022Annex A 5.7 Threat intelligenceAll levels
MITRE ATT&CKM1019 Threat Intelligence ProgramTactical

Practitioner checklist

  • Write down your organisation's definition of each level, including whether technical is separate from tactical.
  • Name a consumer and a decision for every intelligence product.
  • Agree three to five strategic PIRs with executives and review them annually.
  • Use a fixed likelihood scale and separate confidence statements in all assessments.
  • Turn every relevant tactical finding into a tracked detection or hardening requirement.
  • Give every indicator an expiry and a confidence threshold before it reaches a control.
  • Score operational warnings after the fact: was the event real and was action timely?
  • Report one outcome metric per level instead of volume counts.
  • Derive the strategic note and the tactical pack from the same analysis so levels stay consistent.

Standards and references

Related NHI Mgmt Group resources: Threat Intelligence Guide · Writing Threat Intelligence Reports · Threat Intelligence Programme Metrics Guide · Threat Intelligence Maturity Model · Threat Feeds vs Finished Intelligence

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.