" NOT RECOMMENDED", " MAY", and " OPTIONAL" NOT", " SHOULD", " SHOULD NOT", " RECOMMENDED", In the Work Product's prose narrative document(s), the content in the separate The event of a discrepancy between any such plain text file and display content Normative for this Work Product is provided in separate plain text files. Note that any machine-readable content ( Computer Language Definitions) declared Property Rights section of the TC's web page ( ). Have been disclosed that may be essential to implementing this specification,Īnd any offers of patent licensing terms, please refer to the Intellectual This specification is provided under the Non-Assertion Mode of the OASIS IPR Policy, the mode chosen when the Others should send comments to the TC's publicĬomment list, after subscribing to it by following the instructions at the Technical work produced by the Technical Committee (TC) are listed at. Check the "Latest stage" location noted above for possible The level of approval is also listedĪbove. The membership of OASIS on the above date. This document was last revised or approved by This document defines concepts that apply across all of STIX and defines the (STIX) is a language for expressing cyber threat and observable information. Edited by Allan Thomson and Jason Keirstead. STIX/TAXII 2.0 Interoperability Test Document: Part 2 Version 1.0.STIX/TAXII 2.0 Interoperability Test Document: Part 1 Version 1.1.Part 5: STIX Patterning.Įdited by Ivan Kirillov and Trey Darley. Editedīy Rich Piazza, John Wunder, and Bret Jordan. Part 1: STIX Core Concepts.Įdited by Rich Piazza, John Wunder, and Bret Jordan. ![]() This specification replaces or supersedes: Trey Darley ( Jordan ( Piazza ( MITRE Corporation
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |