CyberKit

STIX

Also called Structured Threat Information Expression.

A standardized JSON language for describing and linking cyber threat information.

What it is

Structured Threat Information Expression, a community standard governed by OASIS, is a machine-readable format for representing threat intelligence as connected objects: indicators, actors, malware, campaigns, relationships, and more. It expresses how those objects relate, not only the objects themselves.

Why it matters

STIX lets organizations and tools exchange rich, structured intelligence instead of unstructured reports, preserving context and relationships so the receiving side can act on it automatically.

In practice

Publishing a threat report as STIX objects so a partner's platform ingests the indicators and their links to the actor automatically.

What to look for

  • Objects such as indicators, malware and relationships.
  • Confidence and valid time fields on indicators.
  • Bundles that link context to each indicator.

Common mistake

Sharing indicators without context. STIX can carry why it matters, so include it.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • MISP Open source

    An open source platform for storing, correlating and sharing threat indicators.

  • OpenCTI Open source

    Organizes intelligence as linked STIX objects, from actors down to indicators.

  • VirusTotal Commercial

    Pivots between files, domains and IPs to find related infrastructure.

  • ATT&CK Navigator Open source

    Shows a group's known techniques on the ATT&CK matrix.

Read next

  • TAXII: The transport protocol for sharing STIX threat intelligence between systems.
  • OpenIOC: An XML schema for describing indicators of compromise in a portable way.
  • Threat Intelligence Sharing: Pooling indicators and analysis across organizations to defend collectively.

Sources