Skip to content

MISP Extension definitions - #84

Merged
adulau merged 3 commits into
oasis-open:mainfrom
chrisr3d:main
Nov 13, 2026
Merged

adulau merged 3 commits into
oasis-open:mainfrom
chrisr3d:main

Conversation

@chrisr3d

Copy link
Copy Markdown
Contributor

MISP Extension definitions

Summary

Adds the MISP Extensions: a suite of four STIX 2.1 extensions carrying the MISP content that no standard STIX object or property holds. They replace the custom syntax (x-misp-* objects, x_misp_* properties) that the MISP-STIX
converter (misp-stix) used until now. The MISP Project identity (identity--55f6ea65-aa10-4c5a-bf01-4f84950d210f) creates all four.

Extension definition Type Carries
MISP Property Extension 5ece67ea property-extension MISP values left over on any standard STIX object, with rooms for STIX structures that have no place for custom keys
MISP Attribute Extension c1f2c0fa new-sdo (misp-attribute) a MISP attribute that no standard STIX object represents
MISP Object Extension a093107b new-sdo (misp-object) a MISP object that no standard STIX object represents, with its attributes
MISP Galaxy Cluster Extension 573a76d8 new-sdo (misp-galaxy-cluster) a MISP galaxy cluster that no standard STIX object represents
extension-definition-specifications/misp-5ec/
├── STIX-2.1-MISP-Extensions.md                                # spec document
├── extension-definition--5ece67ea-….json                       # MISP Property Extension
├── misp-property-extension.json                                # its extension body, $ref'd
├── misp-attribute/extension-definition--c1f2c0fa-….json
├── misp-object/extension-definition--a093107b-….json
├── misp-galaxy-cluster/extension-definition--573a76d8-….json
└── examples/                                                   # 8 bundles
objects/extension-definition/
└── extension-definition--{5ece67ea,c1f2c0fa,a093107b,573a76d8}-….json

The layout follows incident-ef7: the main extension sits at the root of the spec directory, and each new SDO has its own subdirectory. The schema $ids and the schema property of each extension definition point to this repository,
which becomes the canonical home. misp-stix ships copies and will point them here before it releases them.

The spec document is Markdown, styled after the Markdown edition of the STIX 2.1 specification. The AsciiDoc workflows only pick up */*.adoc, so the document is not on the Pages index and gets no CI validation. It renders in the
GitHub tree.

Evidence

stix2-validator 3.3.2:

cd extension-definition-specifications/misp-5ec
stix2_validator -v --schemas . examples/*.json
cd ../..
stix2_validator --version 2.1 objects/extension-definition/extension-definition--{5ece67ea-2e8b-4ed0-bb69-26d69053ee0b,c1f2c0fa-3786-4f27-bf57-cf050ecfc104,a093107b-933f-4d72-a9a6-6d7318adadda,573a76d8-f8a0-4f53-bc93-f2777576b7b9}.json
  • Before: an example given an invalid property name in the MISP Property Extension body is rejected, so the extension schemas are enforced:
    [X] STIX JSON: Invalid
    [X] url--5ac347ca-…: extensions.extension-definition--5ece67ea-…: 'BadKey' does not match any of the regexes:
    

'^(?!(extension_type|opinion|author_ref|attachment|filename|url|malware_sample|original_names|windows_pebinary_ext|values)$)[a-z][a-z0-9_]{2,249}$'
```
After: the 8 examples, as committed, are all [+] STIX JSON: Valid, and the validator applies each of the four extension schemas. The 4 published extension definitions are `[+] STIX JSON: Valid` with no warnings, and identical to
their copies in the examples.

The examples raise 12 best-practice warnings and no errors. They are converted from misp-stix test events, which explains the warnings:

  • {103}: their SCO ids are not UUIDv5, and their relationship ids are UUIDv5 rather than UUIDv4.
  • {303}: 4 indicators have no name or description.

Merge Danger

Door: one-way

Merging publishes four extension definition ids, their schema URL and the schema $ids. misp-stix will write them into every bundle it exports, so they cannot move afterwards. A change to a definition needs a new modified, and a
breaking schema change needs a new version. Reverting this PR would break those references, not unpublish them.

Blast Radius: additive

The PR adds new files only. It changes no existing object, schema or spec, and adds no mapping.csv row. CI ignores the new files: the AsciiDoc workflows glob */*.adoc, and the daily CVE job only writes what mapping.csv lists. The
MISP Project identity is not added to objects/identity/; misp-stix ships it, and several other creators of published extension definitions are also absent from that directory.

Four STIX 2.1 extensions (MISP Property, Attribute, Object and Galaxy
Cluster) carrying the MISP content no standard STIX object or property
holds. This repository is their canonical home; misp-stix ships copies.
Markdown styled after the STIX 2.1 Markdown specification.
@adulau
adulau merged commit 248eaa3 into oasis-open:main Nov 13, 2026
2 of 3 checks passed
@adulau

adulau commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants