[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Contributing to the Best Practices Guide
Hi All, As Emily stated at the Monthly CTI TC call(s) yesterday, the STIX Best Practices Guide has been published by OASIS as a committee note. https://docs.oasis-open.org/cti/stix-bp/v1.0.0/cn01/stix-bp-v1.0.0-cn01.html
However, it is not too late to suggest your own best practices to be included!
As is stated in the guide, this document should be considered an initial assessment of the best practices
for expressing cyber threat information in STIX 2.1. We hope it is a “living” document which will be improved by the community of users contributing additional best practices. Additionally, some of the best practices in the guide
might be found to be useless or misguided, or a better best practice for the situation might be discovered.
If you have suggestions, please add them to the STIX issue tracker (https://github.com/oasis-tcs/cti-stix2/issues).
The STIX issue tracker contains a new label which can be used to highlight a new best practice suggestion. The process of determining which suggestions are to be included in the guide and how often the document should be updated will be discussed in a future working call. Rich -- Rich Piazza Lead Cyber Security Engineer The MITRE Corporation 781-271-3760 –––––––––––––––––––––––––––––––––––– MITRE - Solving Problems for a Safer World™ |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]