Grab a cup of tea, because threat intelligence sounds grander than it is, and once you see the plain version it becomes easy to judge. Intelligence, in any field, means information that helps someone make a decision. A list of one million bad IP addresses is data. Intelligence is knowing which of those matter for your company this week, and what to do about them.
Three levels, three audiences
People usually split threat intelligence into three levels, and the split helps you work out who a report is for.
- Strategic: the big picture for executives. Which groups target Indian banks or manufacturing? Is ransomware against hospitals rising? It shapes budgets and risk decisions. It is written in plain language, often as a short briefing.
- Operational: about specific campaigns and how attackers work: the tools, the initial access methods, the timing. Incident responders and SOC leads use it to plan hunts and detection.
- Tactical and technical: concrete indicators such as file hashes, domains, IP addresses and detection rules. Machines consume these directly, loading them into a SIEM or firewall.
Most beginners meet only the last level, via feeds, and wrongly conclude that threat intelligence means blocklists.
Judging a feed
Sources range from free community lists and government advisories (CERT-In publishes advisories in India) to commercial vendors, information-sharing groups within an industry, and your own incident data. Before trusting any feed, ask four questions.
Is it relevant? A feed about attacks on American retailers has limited use for a Chennai software company. Is it timely? Attackers rotate infrastructure fast; an IP address used for a campaign this week may belong to an innocent hosting customer next month, so indicators need expiry dates. Is it accurate? Check how the provider decides what to list, and watch your own false positive rate. And is it actionable? A report that says “a sophisticated actor is active” gives you nothing to do.
A practical habit: when you add a feed, run it in alert-only mode for a few weeks and see how many matches are real before you let it block traffic. Blocking a major content delivery network because a list was sloppy is a very quick way to become unpopular.
How intelligence travels: STIX and TAXII
To share indicators between tools, standards help. STIX is a structured language for describing threat information (indicators, malware, actors, campaigns and the relationships among them). TAXII is the protocol for exchanging STIX content between servers and clients. Platforms that store and share intelligence, often called threat intelligence platforms, speak these. You do not need to memorise the formats; know that they exist so tools can swap information without a human retyping it.
Sharing safely: the Traffic Light Protocol
Intelligence is often sensitive. It may reveal that you were attacked, or protect a source. The Traffic Light Protocol (TLP), maintained by FIRST, labels how widely information may be passed on. In the current version, the labels are:
- TLP:RED, for named recipients only, with no further sharing.
- TLP:AMBER, limited to the recipient’s organisation and those who need to know to act (a stricter variant, AMBER+STRICT, limits it to the organisation only).
- TLP:GREEN, shareable within the wider community but not published publicly.
- TLP:CLEAR, with no restriction on disclosure.
Respecting these labels is what keeps sharing groups alive. People stop sharing quickly when a TLP:AMBER note shows up on social media.
Making it useful inside your own organisation
Start with questions, not feeds. What would we most hate to lose? Who would want it? That defines your intelligence requirements. Then pick a few sources to match, feed technical indicators to detection tools with expiry dates, and turn operational reports into hunts: if a report says a group uses a certain remote administration technique, check whether your logs would reveal it, and if not, fix that gap. This ties neatly to frameworks like MITRE ATT&CK, which gives a shared vocabulary for attacker behaviour.
Finally, close the loop. Tell consumers what you found and what you changed; write down which sources produced real detections and drop the ones that never do. A threat intelligence function that only collects is a hobby. One that regularly changes a firewall rule, a detection or a decision is doing the job.
Leave a Reply