Skip to content
Tutorials Center
My learning

Topics

Lesson 24 of 37 ยท Threat Intelligence and Hunting

Threat Intelligence Fundamentals

Understand cyber threat intelligence: strategic, operational, tactical and technical levels, the intelligence cycle, sources, confidence and how a SOC uses it.

Your SIEM tells you what is happening inside your network. Threat intelligence (TI) tells you what is happening outside it: who is attacking organizations like yours, what tools and tricks they use, and which addresses, domains and files are associated with them. It is not a magic feed that solves detection. It is information that has been collected, processed and analyzed so that someone can make a better decision.

The key word is decision. A list of ten thousand bad IP addresses is data. Knowing that a group targeting your industry sends invoice-themed phishing and then uses a particular remote-access tool, so you should watch for that tool, is intelligence.

Data, information, intelligence

Stage Example Value
Data 203.0.113.50 Raw fact, no meaning
Information "203.0.113.50 hosted a phishing page last week" Some context
Intelligence "Actors targeting our sector are using such pages to steal webmail logins; block the pattern, check for logins from this range, warn staff" Tells you what to do

Four levels

Levels of threat intelligence

Strategic Trends for executives
Operational Campaigns and actor plans
Tactical Techniques and procedures
Technical Indicators: IPs, hashes, domains

Each level has a different audience and shelf life.

1 / 2
  • Strategic: who might attack us and why, and how the landscape is changing. Read by executives and risk managers to decide budgets.
  • Operational: details of specific campaigns and the timing and goals of attackers. Used by incident response and security leads.
  • Tactical: attacker tactics, techniques and procedures (TTPs), how they operate. Used by detection engineers and hunters. The MITRE ATT&CK framework is the common vocabulary.
  • Technical: indicators of compromise (IOCs) such as IP addresses, domains, file hashes and email subjects. Machine-readable, short-lived, used by tools. See IOCs and enrichment.

The intelligence cycle

flowchart LR
    R["1. Requirements: what do we need to know?"] --> C["2. Collection"]
    C --> P["3. Processing"]
    P --> A["4. Analysis"]
    A --> D["5. Dissemination"]
    D --> F["6. Feedback"]
    F --> R

Good intelligence starts with a question and ends with feedback from the people who used it.

  1. Requirements: decide what matters to your organization. A hospital and a game studio need different intelligence.
  2. Collection: gather from sources (below).
  3. Processing: normalize formats, remove duplicates, translate, extract indicators.
  4. Analysis: judge relevance and reliability, link pieces together, state what it means.
  5. Dissemination: deliver the right level to the right audience in a usable form.
  6. Feedback: did it help? Was it too noisy or late? Adjust the requirements.

Sources

  • Internal: your own logs, past incidents, phishing reports and sandbox results. Often the most relevant intelligence you have.
  • Open source (OSINT): vendor blogs, security researchers, vulnerability databases, public malware-analysis reports, government advisories.
  • Information-sharing communities: industry ISACs (sector-specific sharing groups) and trusted peer groups.
  • Commercial feeds: paid reports and indicator feeds with analyst support.
  • Government alerts: national cyber agencies publish advisories on active threats.

Respect sharing rules. Many intelligence products carry a handling label such as the Traffic Light Protocol (TLP: RED, AMBER, GREEN, CLEAR) that says who may see them. Never pass on something beyond its label.

Reliability and confidence

Not every source deserves equal trust. Analysts rate two things separately:

  • Source reliability: has this source been right before?
  • Information credibility: is the claim confirmed by other evidence?

A reliable source can pass on a weak rumor, and an unknown source can report something you can verify in your logs. Express judgments with calibrated words such as "low, moderate or high confidence" and say what would change your mind.

Try it: score and filter an intelligence feed

This stand-in takes a small invented feed and keeps only entries that are fresh, credible and relevant. Real platforms apply similar logic; the numbers here are for teaching.

Python Score a toy indicator feed

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Analysis means connecting pieces. This example groups indicators by shared properties to suggest they belong to one campaign. It is a simple heuristic, not proof.

Python Group indicators by shared traits

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Using intelligence in the SOC

  • Detection: turn TTPs into rules and IOCs into watchlists in the SIEM (hunting with log queries shows how queries use them).
  • Triage: enrich alerts so analysts see "this IP is associated with a known campaign".
  • Incident response: understand likely next steps of an attacker you are fighting.
  • Hunting: start from a new report and look for its techniques (threat hunting).
  • Management: brief leaders about relevant risks.

Common mistakes

  • Loading every feed into the SIEM without filtering, which floods analysts with false positives.
  • Treating old indicators as current; addresses are reassigned and domains get cleaned up.
  • Ignoring internal intelligence from your own incidents.
  • Collecting reports no one reads: tie every product to an audience and a decision.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which best describes threat intelligence rather than raw data?

    Intelligence is analyzed and contextualized so that it supports a decision.
  2. 2. Which type of intelligence has the shortest useful life?

    Infrastructure changes quickly, so indicators go stale within days or weeks.
  3. 3. What is the first step of the intelligence cycle?

    Requirements make sure collection serves actual decisions.
  4. 4. A source that has been accurate before reports something you cannot verify. What is the sound approach?

    Reliability of the source and credibility of a specific claim are different judgments.

Summary

  • Intelligence is analyzed information that supports decisions, not a pile of indicators.
  • Four levels (strategic, operational, tactical, technical) serve different audiences and age at different speeds.
  • The cycle runs from requirements through collection, processing, analysis and dissemination to feedback.
  • Rate reliability and credibility, filter feeds for freshness and relevance, and respect handling labels.

Next: IOCs and Enrichment