Resources

Threat hunting glossary

39 terms you will meet in threat hunting, detection engineering and threat intelligence, defined in plain words. Where Huntbase does something with a term, we say so in one line.

A

Autonomy levels

Guide, Collaborator, Operator

How much an AI system in security operations may do on its own, set by the organisation that runs it. At lower levels it suggests and waits for a person; at higher levels it acts within agreed rules and records what it did. Clear levels let a team start cautiously and grant more as the system earns trust.

In Huntbase: Scout runs at one of three levels, Guide, Collaborator or Operator, from guiding you step by step to carrying out a whole plan within your response rules. Scout

B

Running a detection rule or hunt query over historical data to see what it would have found: how often it fires, on which hosts and users, and whether it catches known incidents.

C

CACAO

Collaborative Automated Course of Action Operations

An OASIS standard for describing security playbooks in a machine-readable, vendor-neutral JSON format, so a course of action can be shared between organisations and run by different tools. Version 2.0 is current.

In Huntbase: Huntbase can export hunt playbooks as CACAO v2. Threat Intelligence

Canary rollout

Staged rollout

Releasing a change to a small subset first, watching for problems, then widening it in stages. In security it applies to detection rules, agent updates and response scripts alike.

CVSS

Common Vulnerability Scoring System

An open standard, maintained by FIRST, for rating the severity of software vulnerabilities on a 0 to 10 scale based on how they can be exploited and what they affect. Version 4.0 was published in 2023.

In Huntbase: Huntbase enriches findings with CVSS, EPSS and KEV in alert triage. AI Alert Triage

D

The practice of designing, testing, deploying and maintaining detection rules as an engineering discipline: rules live in version control, are tested against real data, are tuned on evidence, and are measured once live.

In Huntbase: Huntbase gives Sigma rules backtests, shadow mode and version history. Detection Engineering

How long an attacker is inside an environment before they are found, usually measured from initial access to detection. Long dwell time gives an attacker room to move laterally, take data and set up persistence, and it can outlast log retention, so the evidence of how they got in may be gone by the time anyone looks.

In Huntbase: Huntbase looks back through your history when new intel lands, so a quiet intrusion doesn't wait for an alert. Threat Hunting

E

EDR

Endpoint detection and response

Software on laptops, servers and workloads that records activity, detects threats and lets responders investigate and contain them, for example by isolating a host or killing a process.

Endpoint isolation

Host containment

Cutting a host off from the network, except for the connection to the security tool managing it, so an attacker cannot use it while responders investigate.

EPSS

Exploit Prediction Scoring System

A model, maintained by FIRST, that estimates the probability that a published vulnerability will be exploited in the wild in the next 30 days. Severity scores describe impact; EPSS adds likelihood.

F

H

A testable statement that frames a hunt, such as "an attacker is using stolen credentials to sign in from proxy infrastructure". A good hypothesis can be proven wrong, names the data that would confirm or refute it, and is usually drawn from threat intelligence, ATT&CK techniques or something odd an analyst noticed.

A reusable, documented hunt: the hypothesis, the data it needs, the steps and queries, what a positive or negative result means, and its known blind spots.

An open, MIT-licensed format for threat hunt playbooks, published by Huntbase: Markdown with YAML frontmatter, one heading per step and fenced blocks for queries. It reads without tooling and diffs cleanly in version control.

In Huntbase: The spec, examples and tooling are on GitHub. hunt.md spec

I

IOC

Indicator of compromise

An observable artefact that suggests a system has been compromised: a file hash, IP address, domain, URL, registry key or similar. IOCs are easy to share and match, but attackers can change them cheaply, so they age quickly.

K

KEV

CISA Known Exploited Vulnerabilities catalog

A list, maintained by the US Cybersecurity and Infrastructure Security Agency, of vulnerabilities with reliable evidence of exploitation in the wild. US federal agencies must remediate listed vulnerabilities by set deadlines, and many other organisations use it to prioritise patching.

KQL

Kusto Query Language

A read-only query language from Microsoft, written as a pipeline of operators. It is used in Azure Data Explorer, Microsoft Sentinel, Microsoft Defender advanced hunting and Azure Monitor.

In Huntbase: Huntbase uses KQL as one query language across every connected store. Search & Lake

L

Investigating a running host directly: listing processes and connections, collecting files and memory, or running scripts. It answers questions the logs never recorded.

In Huntbase: Huntbase Endpoint Control asks hosts live questions mid-hunt. Endpoint Control

M

An open-source threat intelligence platform for storing, correlating and sharing indicators and events, widely used by CERTs, ISACs and security teams. It began as the Malware Information Sharing Platform.

A public knowledge base, maintained by MITRE, of adversary tactics and techniques observed in real intrusions. It covers enterprise, mobile and industrial control systems, and gives defenders a shared vocabulary for mapping detections, hunts and coverage gaps.

MTTR

Mean time to respond

The average time from detecting an incident to containing or resolving it. It is usually measured from the first alert, so it says nothing about how long an attacker was inside before that alert; dwell time covers that part. Some teams use MTTR for mean time to recover or remediate, so check the definition before comparing figures.

O

OCSF

Open Cybersecurity Schema Framework

An open schema for security event data, launched in 2022 by a group of security vendors and now a Linux Foundation project. It defines common event classes and field names, so data from different products can be queried the same way.

In Huntbase: Huntbase normalises results to OCSF v1.3, so one rule or query runs on every matching source. Search & Lake

An open-source tool, created at Facebook and now a Linux Foundation project, that exposes an operating system as a set of relational tables you can query with SQL: processes, network connections, users, files, installed software and more. It runs on Windows, macOS and Linux.

In Huntbase: Huntbase Endpoint Control is built on open-source osquery. Endpoint Control

R

Searching historical telemetry for a threat that was only described after the activity happened: new indicators, a newly disclosed vulnerability or a fresh advisory. It answers the question every new advisory raises, whether it already happened here. Advisories on mass exploitation often recommend it, because a patch closes the hole but doesn't remove an attacker who is already in.

In Huntbase: When new intel lands, Scout checks it back through the history in the tools you already run and on your endpoints. Threat Hunting

S

Huntbase's name for hunting across the security data you already have and keeping telemetry in a lake. One query runs in place across connected SIEMs, EDR, cloud and identity tools and your own Apache Iceberg lake (available on request), or the Huntbase Lake for telemetry you choose to send, with results normalised to OCSF.

In Huntbase: Every tool you run, one hunt. Your lake or ours. Search & Lake

Security data lake

Apache Iceberg

Security data kept in low-cost object storage in open formats, queried by separate engines. Apache Iceberg is an open table format that adds schemas, partitions, snapshots and transactions to files in a lake, so several engines can read the same tables safely.

In Huntbase: Huntbase can store telemetry for you, and querying your own Iceberg lake is available on request. Search & Lake

Running a new detection rule against live data and recording what it would have fired on, without alerting anyone. Teams use it to measure noise and accuracy before turning a rule on.

SIEM

Security information and event management

A system that collects logs and events from across an environment, stores them, and lets analysts search, correlate and alert on them. It is often the system of record for security investigations and compliance.

In Huntbase: Huntbase Search & Lake hunts across your existing SIEMs in place, or your own lake. Search & Lake

An open, YAML-based format for describing log detections independently of any one SIEM. A Sigma rule names a log source and the field conditions to match, and tools convert or compile it to a specific query language. The community rule set is maintained by the SigmaHQ project.

In Huntbase: Huntbase compiles Sigma natively and lets you backtest a rule on your own history before it goes live. Sigma rule testing

SOAR

Security orchestration, automation and response

Tools that run security workflows, often called playbooks, across other products: enriching alerts, opening tickets, asking for approval and taking response actions through each tool's API.

SPL

Search Processing Language

Splunk's query language. Searches are written as a pipeline of commands that filter, transform and aggregate indexed events.

STIX

Structured Threat Information Expression

An OASIS standard, currently version 2.1, for representing cyber threat intelligence as JSON objects: indicators, malware, threat actors, campaigns, attack patterns and the relationships between them. STIX patterns describe what to look for in observed data.

In Huntbase: Huntbase translates STIX 2.1 patterns for each connected source. Threat Intelligence

T

TAXII

Trusted Automated Exchange of Intelligence Information

An OASIS standard protocol for exchanging threat intelligence over HTTPS, usually carrying STIX. Servers expose collections that clients can poll for new objects or publish to.

The proactive search for attackers who are already inside an environment but have not triggered an alert. Hunters start from a hypothesis, search telemetry and hosts for evidence for or against it, and turn what they learn into better detections.

In Huntbase: Huntbase is built around the hunt: hypothesis, steps, checkpoints and a verdict you record. Threat Hunting

TLP

Traffic Light Protocol

A set of labels, maintained by FIRST, that tells recipients how far they may share information. TLP 2.0 defines TLP:RED, TLP:AMBER+STRICT, TLP:AMBER, TLP:GREEN and TLP:CLEAR.

TTP

Tactics, techniques and procedures

How an adversary operates. Tactics are the goal (for example persistence), techniques are the method (a scheduled task), and procedures are the specific implementation a group uses. Hunting for TTPs is more durable than hunting for IOCs, because behaviour is harder to change than infrastructure.

Two-person approval

Four-eyes principle

A control that requires a second, independent person to approve a sensitive action before it runs. The person who proposed the action cannot approve it themselves.

In Huntbase: In Huntbase, any action outside your response rules waits for two people by default, and the person who proposed it can't approve it. Endpoint Control

X

XDR

Extended detection and response

Detection and response that correlates telemetry beyond the endpoint, such as identity, email, network and cloud, usually within one vendor's ecosystem or through its integrations.

Y

An open-source tool and rule language for identifying and classifying files, most often malware, by matching text or byte patterns and conditions. YARA rules are used to scan files on disk, in memory and in malware repositories.

Questions

Terms people mix up.

  • What is the difference between an IOC and a TTP?

    An IOC is an artefact such as a hash, IP address or domain that suggests compromise. A TTP describes how an attacker operates. IOCs are easy to match but cheap for attackers to change; TTPs are harder to change, so hunts built on behaviour last longer.
  • What is the difference between Sigma and YARA?

    Sigma describes detections over log events and is converted to a SIEM's query language. YARA matches patterns in files and memory, most often to identify malware.
  • How is threat hunting different from detection?

    Detection rules wait for known patterns to appear. Threat hunting goes looking for activity that no rule has caught yet, starting from a hypothesis. A good hunt usually ends by turning what it found into a new detection.

Put the terms to work.

Sign up and run your first hunt with Scout on sample data, then connect your own sources.

  1. Sign up.

  2. Run a guided hunt on the sample workspace. No connector needed.

  3. Connect your own sources when you're ready.