A cyber threat intelligence (CTI) programme drifts quietly: feeds keep arriving, indicators pile up in the platform, and requirements written two years ago stop matching the threats the organisation now faces. This health check is a recurring audit of that drift: nine metrics with formulas, data source types and green, amber and red thresholds, plus a cadence, a findings log and a remediation map. It is written for the CTI lead and the security operations manager who consume the output, and for internal audit when it re-performs the figures. It measures feed health, requirement coverage and how much intelligence becomes detection; it is not a board narrative, and the lifecycle, models and sharing standards are explained in the Threat Intelligence Guide rather than here.
What this health check covers
The Threat Intelligence Maturity Model places a programme on a capability scale, and the Threat Intelligence Feed Evaluation Guide covers the one-time trial of a new feed. This page is the recurring check between those two events: it shows whether priority intelligence requirements (PIRs) are still answered, whether feeds still earn their place, whether indicators are retired on time and whether intelligence changes what defenders do. It suits anyone looking for threat intelligence KPIs, CTI programme metrics or a practical answer to how to measure threat intelligence.
Key takeaways
- Requirements are the denominator: PIR coverage comes first because every other metric is only meaningful against what stakeholders asked the programme to answer.
- Feeds are measured in production, not at trial: fidelity, overlap and ageing drift after purchase, so each feed is re-scored every quarter.
- Indicators need an end date: expired indicator share and IOC ageing show whether the platform is pushing stale data into detection tools and creating noise.
- Value means action: intel to detection conversion and actioned intel share count what defenders changed, not how many reports were produced.
- Thresholds are starting points: the values below are NHI Mgmt Group recommendations; record your own targets and the reason for any change in the findings log.
How to use this template
Copy the metrics table and findings log into your tracker. Fix the definitions once (what counts as a PIR, a feed, a confirmed match and an actioned product) in your Threat Intelligence Policy Template so results stay comparable. Collect each figure from the data sources listed, score it, log every amber or red result as a finding with an owner and due date, and keep each run so the trend is visible.
Cadence and sign-off
| Review | Frequency | Owner | Approver | Evidence kept |
|---|---|---|---|---|
| Indicator hygiene (T3, T9) | Monthly | CTI analyst responsible for the platform | CTI lead | Platform export of indicator counts by age and validity |
| Feed scorecard (T2, T8) | Quarterly, and before each renewal | CTI lead | Head of security operations | Scorecard per feed, match and triage records |
| Full metric run (T1 to T9) | Quarterly | CTI lead | CISO or head of security operations | Metric workbook, findings log, review minutes |
| PIR refresh with stakeholders | At least yearly, and after a major business or threat change | CTI lead | CISO | Signed PIR list, stakeholder attendance |
| Independent re-performance | Yearly | Internal audit | Audit committee | Re-performed samples, variance notes |
Metrics
"PIR" means a priority intelligence requirement approved by a named stakeholder. "Feed" means any external source ingested on a schedule: commercial, open source, government or sharing community. A "confirmed match" is an indicator hit triaged as malicious or suspicious rather than benign. NHI Mgmt Group recommended thresholds; adjust to your programme.
| ID | Metric | Formula (numerator / denominator) | Data source type | Green | Amber | Red |
|---|---|---|---|---|---|---|
| T1 | PIR coverage | Active PIRs with at least one mapped source and a finished product in the last quarter / active PIRs | PIR register; collection plan; product library | ≥ 90% | 70% to below 90% | < 70%, or PIRs not reviewed in over 12 months |
| T2 | Feed fidelity rate | Confirmed matches from the feed / all matches from the feed in the period, per feed | SIEM and EDR alert triage outcomes linked to indicator source | ≥ 70% per feed | 40% to below 70% | < 40%, or a feed with no matches for two quarters and no other use |
| T3 | IOC ageing | Active network indicators (IP, domain, URL) older than their type's review age / active network indicators | Threat intelligence platform (TIP) indicator store | < 5% | 5% to 15% | > 15% |
| T4 | Intel to detection conversion | Intelligence products in the period that produced a new or tuned detection, hunt or block / intelligence products marked actionable for detection | Detection repository change history; hunt log; product library tags | ≥ 50% | 25% to below 50% | < 25% |
| T5 | Stakeholder request turnaround | Requests for information answered within the agreed time / requests for information closed in the period | Request ticket queue | ≥ 90% | 75% to below 90% | < 75% |
| T6 | Report consumption | Intelligence products opened or acknowledged by at least one named recipient within 7 days / products distributed | Portal or distribution analytics; acknowledgement records | ≥ 80% | 50% to below 80% | < 50% |
| T7 | Actioned intel share | Products that led to a recorded action (detection, block, patch priority change, credential reset, access change, risk decision) / products distributed | Product library with action field; change and ticket records | ≥ 40% | 20% to below 40% | < 20% |
| T8 | Feed overlap | Indicators from the feed already present from another feed at ingest / indicators from the feed, per feed | TIP deduplication and source attribution data | < 50% for every paid feed | 50% to 80% | > 80% for a paid feed with no unique matches |
| T9 | Expired indicator share | Indicators still exported to detection tools after their valid until date or revocation / indicators exported to detection tools | TIP export logs; SIEM, firewall and EDR blocklists | 0% | Under 2% | 2% or more, or indicators exported with no end date at all |
Notes on the formulas
- T1 counts finished products, not collection: a source mapped to a PIR that has produced nothing for a quarter does not cover it. PIRs with no named stakeholder are retired, not counted.
- T2 depends on triage discipline: it only works when analysts record a disposition for indicator alerts and the alert keeps its source tag. Measure per feed; an average hides the worst source.
- T3 uses review ages by indicator type: set them in policy, for example short for IP addresses on shared hosting and longer for file hashes, which do not go stale in the same way. The Threat Intelligence Feed Evaluation Guide covers freshness and latency.
- T4 and T7 need a field in the product record: add "action taken" and "detection reference" to each product so conversion can be counted without interviews. Tactical products map most directly to detections; strategic products count under T7 through risk decisions. See Strategic vs Operational vs Tactical Threat Intelligence.
- T8 is a renewal input: high overlap is acceptable for a free source; for a paid feed, compare its unique confirmed matches with its cost before renewal.
- T9 uses the indicator's own validity: STIX 2.1 defines valid_until on the Indicator object as the time after which it should no longer be considered valid, and marks revoked objects as no longer valid by their creator. Exports should honour both.
How to collect the data
- Snapshot the PIR register and collection plan: PIR ID, stakeholder, approval date, mapped sources and the last product delivered for T1.
- Export TIP indicator data: counts by type, source, first seen, valid until, revocation status and duplication for T3, T8 and T9.
- Pull triage outcomes: from SIEM and EDR case records, join indicator alerts to their source feed and disposition for T2.
- Read the detection change history: list detections, hunts and blocks created or tuned in the period that reference an intelligence product for T4.
- Export the product library and request queue: distribution, acknowledgement and action fields for T6 and T7; request open and close times against the agreed turnaround for T5.
- Compare exports with enforcement points: check blocklists in firewalls, proxies and EDR against TIP validity for T9; this is where stale data actually does harm.
- Sample and verify: trace five products and five indicators end to end. A metric that cannot be traced to records is reported amber at best.
Reading the results together
| Pattern | Likely meaning | First action |
|---|---|---|
| T6 high, T7 low | Products are read but not usable | Add recommended actions and owners to each product; see Writing Threat Intelligence Reports |
| T2 low, T8 high on the same feed | A paid feed adds noise rather than coverage | Move it to enrichment only or drop it at renewal |
| T3 and T9 both amber or red | Indicator expiry is not enforced end to end | Set type-based expiry in the TIP and make exports respect it |
| T1 falling while products rise | The team is busy on work nobody asked for | Hold a PIR refresh and retire unrequested product lines |
| T4 low with a healthy T2 | Good intelligence is not reaching detection engineering | Add a standing hand-off and track it as a ticket type |
Red flags that need action now
- Blocklists in production still enforcing indicators past their validity or revoked by the source (T9).
- No PIR review in over a year, or PIRs with no named stakeholder (T1).
- A paid feed with no confirmed match in two quarters (T2, T8).
- No detection or hunt traced to intelligence in a quarter (T4).
- Products shared outside the TLP marking they carry; the current FIRST standard is TLP 2.0 with CLEAR, GREEN, AMBER and RED labels.
- Platform API keys or feed credentials shared between analysts with no owner; see Securing the threat intelligence platform (TIP) itself.
Findings log
| Finding ID | Finding | Metric | Severity | Owner | Due date | Status |
|---|---|---|---|---|---|---|
| HC-CTI-01 | [Number] PIRs without a product in the last quarter | T1 | [High / Medium / Low] | [Role] | [Date] | [Open / In progress / Closed / Risk accepted] |
| HC-CTI-02 | Feed [name] fidelity at [%] with [%] overlap | T2, T8 | [Severity] | [Role] | [Date] | [Status] |
| HC-CTI-03 | [Number] expired indicators still enforced in [tool] | T9 | [Severity] | [Role] | [Date] | [Status] |
| HC-CTI-04 | Intel to detection conversion at [%] | T4 | [Severity] | [Role] | [Date] | [Status] |
| HC-CTI-05 | [Finding] | [Metric] | [Severity] | [Role] | [Date] | [Status] |
Group items with a shared root cause into one finding. Risk accepted findings carry an expiry date and the approver's name, and are re-opened at the next quarterly run.
Framework mapping
| Framework | Reference | Metrics |
|---|---|---|
| NIST CSF 2.0 | ID.RA-02 Cyber threat intelligence is received from information sharing forums and sources | T2, T8 |
| NIST CSF 2.0 | ID.RA-03 Internal and external threats identified and recorded | T1 |
| NIST CSF 2.0 | DE.AE-07 Cyber threat intelligence integrated into the analysis of adverse events | T4, T9 |
| NIST CSF 2.0 | ID.IM-01 Improvements identified from evaluations | All |
| NIST SP 800-53 Rev. 5 | PM-16 Threat Awareness Program; SI-5 Security Alerts, Advisories, and Directives | T1, T5, T7 |
| NIST SP 800-53 Rev. 5 | RA-10 Threat Hunting; SI-4 System Monitoring; PM-6 Measures of Performance | T4, all |
| ISO/IEC 27001:2022 | Annex A 5.7 Threat intelligence | T1, T7 |
Remediation map
| Finding type | Metrics | Where the fix is explained |
|---|---|---|
| Stale or missing requirements | T1, T5 | Threat Intelligence Guide (lifecycle and intelligence requirements) |
| Weak or redundant feeds | T2, T8 | Threat Intelligence Feed Evaluation Guide; Open-Source vs Commercial Threat Intelligence |
| Indicator hygiene | T3, T9 | Threat intelligence platform (TIP) rollout playbook |
| Intelligence not reaching detection | T4 | Detection Engineering Guide; Threat Intelligence vs Threat Hunting |
| Products not read or used | T6, T7 | Threat Intelligence Report Template; Writing Threat Intelligence Reports |
Related guides
- Threat Intelligence Maturity Model: place these results on a capability scale.
- Threat Intelligence Executive Briefing: the leadership view of the programme.
- M1019 Threat Intelligence Program: the ATT&CK mitigation for a threat intelligence programme.
- Threat Intelligence for Identity and NHI Guide: intelligence on credential and token abuse.
References
- NIST: SP 800-150, Guide to Cyber Threat Information Sharing
- OASIS: STIX Version 2.1
- FIRST: Traffic Light Protocol (TLP)
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-53 Rev. 5
Related NHI Mgmt Group resources: Threat Intelligence Guide, Threat Intelligence Maturity Model, Threat Intelligence Executive Briefing, Threat Intelligence Feed Evaluation Guide.