Release of STIX Validator 3.1.2 and implications for Extension Definitions

[Rich Piazza <rpiazza@mitre.org>]

Hi all,

 

The 3.1.2 release of the STIX validator took place on 11/30.  It has been updated to better handle extension definition JSON schemas when validating content specified using an extension definition.

 

The validator has a command line argument (-s/--schemas) to specific the directory in which the necessary JSON schemas for the extension definitions can be found. The major change is that the name of the schema file in that directory must be the extension-definition id.  Previously, the validator looked for a file named after the STIX object type that was being extended.  This made it impossible to use more than one extension of the same STIX object type in content at the same time.

 

For examples of this change look in the STIX common object repository.  The best one to look at is acs-data-markings.

 

If you have contributed an extension definition to the STIX common object repository, please create a pull request which contains the file name change.

 

In the future, when creating a JSON schema for an extension definition please name the JSON schema file: <extension-definition-id>.json

 

Thanks!

 

                Rich

 

--

Rich Piazza

Lead Cyber Security Engineer

The MITRE Corporation

781-271-3760

––––––––––––––––––––––––––––––––––––

MITRE - Solving Problems for a Safer World™