Cybersecurity & Information Security

STIX and TAXII: How to Share Threat Intelligence

6 min readPublished: August 5, 2026

Professional visual illustration on STIX and TAXII in the field of Threat Hunting and Detection

Quick answer

STIX and TAXII begin with a question or behavior to identify, continue to Telemetry definition and logic, and conclude with testing, tuning, documentation, and controlled deployment. Quality is measured by coverage and investigative capability.

Threat Hunting and Detection Engineering transform adversary behavior knowledge into measurable questions, data sources, and detection rules. The goal is not to generate more alerts, but to improve coverage and decision quality. This article focuses on STIX and TAXII and is intended for analysts and integration specialists. The aim is to provide a working methodology that can be applied in practice, professional interviews, and work environments, without merely relying on dictionary definitions.

The central challenge is that data is almost always incomplete. STIX objects, relationships, and bundles can indicate a direction, but their meaning depends on time, asset, user, and expected activity. Therefore, we will build the test around an investigative question, required evidence, and a clear criterion for completion.

The practical scenario in the article is: mapping a simulated IOC to STIX objects. All examples are lab data or process descriptions. When dealing with Penetration Testing, Web, or Cloud, work only with explicit authorization, defined Scope, and the ability to stop the test.

What STIX Represents

The topic 'What STIX Represents' is a key part of working with STIX and TAXII. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of a tool without understanding its purpose.

In practice, list STIX objects, relationships, bundles, TAXII collections, API root, compare them to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Objects and Relationships

The topic 'Objects and Relationships' is a key part of working with STIX and TAXII. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of a tool without understanding its purpose.

What TAXII Does

The topic 'What TAXII Does' is a key part of working with STIX and TAXII. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of a tool without understanding its purpose.

Quality, Permissions, and Lifecycle

In STIX and TAXII, identity and authorization are two different questions: who is the client, and what are they allowed to perform on the resource. Roles, Claims, Session, Object ownership, and changes throughout the lifecycle are checked, rather than just assuming the user is 'logged in'.

A test matrix includes anonymous user, regular user, object owner, another user, and administrator. For each action, compare the Response and the server-side impact. Changing an ID or Header is merely a testing means; the evidence is that the server approved or denied an action contrary to policy.

Unique Testing Focus Areas

In this topic, it is recommended to build a focused evidence map in advance. The main testing focus areas are: STIX objects, relationships, bundles, TAXII collections, API root, sharing policy. The list is not an automatic Checklist; each item is selected because it can link an entity, action, and time or explain legitimate behavior.

STIX objects: Define the expected value, what would be considered abnormal, and what additional source would corroborate the finding.
relationships: Define the expected value, what would be considered abnormal, and what additional source would corroborate the finding.
bundles: Define the expected value, what would be considered abnormal, and what additional source would corroborate the finding.
TAXII collections: Define the expected value, what would be considered abnormal, and what additional source would corroborate the finding.
API root: Define the expected value, what would be considered abnormal, and what additional source would corroborate the finding.
sharing policy: Define the expected value, what would be considered abnormal, and what additional source would corroborate the finding.

If one of the focus areas is unavailable, document the gap and choose an alternative. For example, if a Process identifier is unstable, you can use time, Host, User, and Parent; if Payload is encrypted, use Metadata, volume, frequency, and TLS/DNS context.

Recommended Workflow

Define a Scope and one working question regarding STIX and TAXII.
List the data sources and required evidence: STIX objects, relationships, bundles, TAXII collections.
Create a short Baseline of normal behavior or expected outcome.
Perform the minimal test in a lab environment and record time, input, and output.
Build a Timeline or comparison table and separate fact from interpretation.
Pivot to an additional source to confirm or refute the initial explanation.
Summarize the decision, limitations, recommended action, and Retest criterion.

Practical Scenario

The chosen scenario is mapping a simulated IOC to STIX objects. The purpose of the exercise is not to prove attack capability, but to practice safe collection, comparison, and documentation. Before starting, define simulated data, a time window, and an expected outcome.

At the end of the exercise, submit a deliverable that another analyst or tester can review: a screenshot or Export of the evidence, a short Timeline, initial hypothesis, corroborating evidence, limitation, and recommendation. If there is insufficient evidence, the correct conclusion is that the scenario was not proven.

Stage	What to do	Deliverable
Preparation	Define Scope, time, and objective. List which fields or evidence from STIX objects, relationships, bundles are expected to appear.	Short test plan
Data Creation	Perform a safe, simulated action related to STIX and TAXII, without real information or impact on a production system.	Controlled event/Request/Flow
Collection	Collect the raw evidence and context from another source. Verify Time zone, identifiers, and integrity.	Two linked pieces of evidence
Analysis	Write what each piece of evidence proves, what it does not prove, and what the possible legitimate explanation is.	Interim conclusion
Conclusion	Choose closure, escalation, Finding, or Tuning; add recommendation and Retest.	Documented deliverable

Practical Checklist

Check and document: Hypothesis.
Check and document: ATT&CK technique.
Check and document: Data sources.
Check and document: Detection logic.
Check and document: Expected benign behavior.
Check and document: Test cases and coverage.
Note Time zone, tool version, and collection time.
Save the raw data before filtering or modification.
Write what the finding proves and what is still unknown.
Define owner and next action with a due date.

Common Mistakes

Starting from a random IOC without a Hypothesis.
Mapping ATT&CK by name only.
Writing a Rule without Test cases.
Ignoring legitimate behavior.
Measuring Rules instead of Coverage.
Not managing versions.

Summary and CTA

STIX and TAXII: How to Share Threat Intelligence is a topic that connects technical knowledge with work discipline. Start with a question, collect only relevant evidence, maintain context and time, and choose an action that can be justified and re-tested.

In HPI's Cybersecurity & AI track, these principles are practiced using systems, logs, and labs. A natural next step is to move on to the linked articles, perform the lab exercise, and save the deliverable as part of a professional portfolio.

FAQ

Does STIX and TAXII alone prove an attack or vulnerability?

No. It provides a signal or finding that requires context, validation, and an additional source. A professional conclusion relies on a sequence of evidence and alignment with expected behavior.

What do you do when some data is missing?

Document the missing data, check for an alternative source, and reduce the level of certainty. Do not complete fields by conjecture or present Unknown as valid.

How long should evidence be kept?

The time depends on policy, regulation, cost, and event type. It is important to define Retention, Legal hold, and the ability to export evidence in a verifiable format in advance.

How do you practice without risking a real system?

Use virtual machines, simulated data, CTF, or a dedicated lab. For authorized tests, define Scope, Stop conditions, and backup before starting work.