Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

STIXProject / specifications Public

Notifications You must be signed in to change notification settings
Fork 7
Star 20

Code
Issues 75
Pull requests
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

CTI STIX SC Work Product Roadmap

Jump to bottom Edit New page

sbarnum edited this page Aug 20, 2015 · 10 revisions

*[STIX 1.2.1] *[STIX 2.0]

Add a custom footer

Toggle table of contents Pages 40

Home
Active Issue: IDable Construct Properties
Active Issue: Relating Source
Collaborative specification work
CTI Consensus Items
CTI STIX SC Work Product Roadmap
Idea Exploration: Data Markings Alternatives
Indicator Tranche Working Page
Outline of proposed 2.0 language specification development process
STIX 2.0 Idea Exploration
STIX 2.0 Issue Triage
STIX 2.0 Open Questions
STIX 2.0 Proposal1 : Extend core constructs from a single base class (#148)
STIX 2.0 Proposal10 : Make field names consistent for usages of Information Source (#263)
STIX 2.0 Proposal11 : Abstract Sightings into an independent construct rather than embedded within Indicator (#306)
STIX 2.0 Proposal12 : Clarify semantics of different types of TTPs as expressed in the TTP construct (#360)
STIX 2.0 Proposal13 : Refactor Kill Chain Types (#117, #191, #241, #190, #47)
STIX 2.0 Proposal14 : Flatten list layers in Package (#382)
STIX 2.0 Proposal15 : Remove abstract base types for "top level" objects (#386)
STIX 2.0 Proposal16 : Refactor Report Object (#385)
STIX 2.0 Proposal17: Clarify semantics of different types of Exploit Targets as expressed in the Exploit Target construct (#387)
STIX 2.0 Proposal18: Abstract Victim to top level construct rather than embedded only within Incident and TTP (#149)
STIX 2.0 Proposal2 : Make IDs required (#221)
STIX 2.0 Proposal3: Add Alternative_IDs to all top level objects (#358, #187)
STIX 2.0 Proposal4: Remove Short_Description (#194)
STIX 2.0 Proposal5 : Abstract Source to top level construct rather than embedded only within other constructs (#233)
STIX 2.0 Proposal6 : Remove the @id\@idref attribute from some constructs (#336)
STIX 2.0 Proposal7 : Make Observable structure align with other components (#160)
STIX 2.0 Proposal8 : Remove either embedded or referenced relationships (#201)
STIX 2.0 Proposal9 : Abstract relationships as top level constructs rather than embedded within other constructs (#291)
STIX 2.0 Requriements
STIX 2.0 Roadmap
STIX 2.0 Round 1 Strawman Proposals
STIX 2.0 Tranche 1 Plan: Indicators
STIX 2.0 Tranche Plan (draft)
STIX 2.0 Use Cases
STIX Use Cases
Work Product: STIX 1.2.1 Specification
Work Product: STIX 1.2.1 XML Binding Specification 1.0
Work Product: STIX 2.0 Specification

Add a custom sidebar

Clone this wiki locally

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.