New object templates to support new STIX 2.1 Incident extension objects #396
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… as well as its core extension
…uring an incident
…ed in STIX 2.1 Incident object extensions
…cident object extensions
|
Should we merge? or wait for the latest updates of the incident extension in STIX 2.1? |
- We will probably parse scores and build the
attribute value the following way:
"{name} - {description}: {score}"
…pdated some opposite relationships in consequence
|
Thanks a lot for your work on this extension! As the extension is merged on the OASIS side, we can safely merge it here ;-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To be reviewed and improved before merging as some fields are open to discussions.
Notes, and comments on the mapping available here: https://hdoc.csirt-tooling.org/q2uM6tfkS-W-FUwVuujByw?view