STIX 1.1 Release Planning

Release Status

This STIX 1.1 release candidate is now published on the STIX website: http://stix.mitre.org/language/version1.1/

Please review, test, and evaluate to ensure that it doesn't have any bugs or introduce any regressions. At this point, bugs will be addressed and fixed but new features will be deferred to the next major or minor release.

Release Timeline

• Initial Draft: January 16 – This will incorporate all major changes except versioning and revocation and a vast majority of minor changes. It should let you get an early look at the overall picture of most of what is included in the new version.
• Draft 2: February 3 – This will incorporate all major and minor changes. It should let you see the overall picture of the new version, but there will almost certainly be bug fixes or other minor changes between this draft and the release candidate as we finalize the schemas and do testing.
• Release Candidate: February 11 – This will be equivalent to the final release unless any issues in it are identified. Its primary purpose is to allow everyone to do some final testing to ensure that what is published as the final release is as bug-free as possible.
• Final Release: February 20 – This is the final, official release. If any issues are found in the release candidate they will be fixed, otherwise this will just be a re-release of the release candidate.

Community Proposals

We welcome and encourage any feedback with regards to these proposals. You can either reply to the corresponding thread on the STIX-discussion email list or by commenting on one of the open issues linked to a given proposal (you will need a GitHub account for the latter). Feedback you don’t wish to make public can be sent to STIX@mitre.org, although we encourage public feedback whenever possible.

New proposals will be added to this page and announced on the STIX-discussion email list.

Round 1

Proposal	Status
Proposal: Change Multiplicity on Indicator Type from 0..1 to 0..many	CLOSED
Proposal: Change Multiplicity on Package_Intent to 0..many	CLOSED
Proposal: Correct Typo in Motivation Vocabulary	CLOSED
Proposal: Create Course Of Action Type Vocabulary	CLOSED

Round 2

Proposal	Status
Proposal: Add ability to indicate profile or profiles on a STIX_Package	CLOSED
Proposal: Add External_ID field or fields to the Incident Component	CLOSED
Proposal: Add Related_Observable to SightingType	CLOSED
Proposal: Add Sophistication field to Threat Actor	CLOSED
Proposal: Add Technical_Targeting field to TTP Victim_Targeting	CLOSED
Proposal: Expand Indicator Type Vocabulary	CLOSED
Proposal: Fix relationship from TTP to Exploit_Target	CLOSED

Round 3

Proposal	Status
Proposal: Add Parameter_Observables field to CourseOfAction	CLOSED
Proposal: Create RelationshipType Vocabularies	CLOSED
Proposal: Document Redundant fields in KillChainPhaseReferenceType	CLOSED
Proposal: Expand VulnerabilityType in Exploit Target	CLOSED

Others

Proposal	Status
Proposal: Move Indicator Campaign relationships from Campaign construct to Indicator construct	CLOSED
Proposal Enable More Flexible Structuring of STIX Package Content	CLOSED
Proposal: Enhance InformationSourceType to Capture More Complex Sources of Information	CLOSED

Other Changes

A full list of changes being made for this release can be found by looking at both the open and closed issues on the issue tracker.