From 37744cb942cc5f1e1aff168b020e7d6b882ac2f6 Mon Sep 17 00:00:00 2001 From: Emmanuelle Vargas-Gonzalez Date: Mon, 8 Feb 2021 15:12:19 -0500 Subject: [PATCH] update resources.md with latest approved CS - update icon to new style - typos or minor changes --- README.md | 5 ++--- contribute.md | 29 +++++++++++++---------------- faq.md | 10 +++++----- img/oasis_icon.png | Bin 865 -> 1019 bytes js/main.js | 6 ++++++ resources.md | 22 ++++++++++++++++++++-- 6 files changed, 46 insertions(+), 26 deletions(-) diff --git a/README.md b/README.md index 34fddb8..be40426 100644 --- a/README.md +++ b/README.md @@ -6,10 +6,9 @@ This repository is a GitHub Pages site storing non-normative information about t ## Developing -Setting up a development environment requires a working Ruby environment (for Jekyll) -and a working Python environment (for running git hooks and validating examples). +Setting up a development environment requires a working Ruby environment (for Jekyll), and a working Python environment (for running git hooks and validating examples). -The following commmands should help: +The following commands should help: ```bash gem install bundler diff --git a/contribute.md b/contribute.md index 1f94a0d..7616a32 100644 --- a/contribute.md +++ b/contribute.md @@ -19,7 +19,6 @@ Contribute and Join The Global Community -

Want to stay up-to-date on the latest STIX discussions?

@@ -30,31 +29,29 @@ Contribute and Join The Global Community
-### Contribute Tools and Libaries +### Contribute Tools and Libraries To have code commited to OASIS repositories a Contributor License Agreement(CLA) must be submitted and approved. -Bug reports, suggestions and help requests about specific OASIS github projects should be done through Github issues on their respective repository. +Bug reports, suggestions and help requests about specific OASIS GitHub projects should be done through GitHub issues on their respective repository.

Contributor License Agreement

- - License Agreement - + + License Agreement +
-
@@ -68,8 +65,8 @@ To be directly involved in the development of the STIX specification one must jo

Join the Technical Committee

- Join Technical Committee - + Join Technical Committee +
diff --git a/faq.md b/faq.md index 3034f26..50a6acb 100644 --- a/faq.md +++ b/faq.md @@ -9,15 +9,15 @@ Frequently Asked Questions ===================================================
- + Official FAQ Google Doc - + - + Question not found? Send it in! - +
- +
diff --git a/img/oasis_icon.png b/img/oasis_icon.png index c4229e6b73872f40cbf941cad2c1b87170e14346..9e9506c5f550f3b1a21a7b5d21895598ec360dde 100644 GIT binary patch literal 1019 zcmV1uUC$*Rf^AJjQpbNw7fRGV%p`di~A`(N=f-sXHy6DC%mC%f&G|P&i6cvnt zP(-^hBp64s3yG2vN|PML!VAsuFpkZv?|r*)X8LFTnQ>S}C z#VJ`~B7?F~h6s1hm5sui?6kOk#t2G1Dz05pkDIADZalb#GK`8r#@&voE297p9A)k_ zOev#)be;97#msr>o2!-oO9~Psn`dlKEr)=XLB`%@vvkqkwwp>S!0>hNJ>dR~Fmr8I zyzteP+R`~-8X#R7WPAm;wzpHh^!kw)paKP-h-P9xD1HUr@v&800i+RsBTpm6D zi_2-a0@Ctkq3{zD4a%-lT%%tUk}#Wyf_VmoQRa%W4=ej%1V5<5e=2Nc+9Ug{!WR{^ zSaj@LHoCtJ4$F?mD2opjeo;Xx63_$Hg}Ck^HY?oT`Me{tFDd)Hg5#0>volQ!AC@@Z zv}TNpsJrxNOt!p3!PH?2=yav?c~@+7&o3);MB!Zub~=3G;JR`8SHQ11Nz8GuN#XHj z5YQDb1-~hKi^TSB5Ustt$~JqAR{<9(->9&eYi^z^Uu^ z?Lj(}`k20cEXLYyTRXX`h_6c;uU0ykqVNJ`Kc&oF5w7YFRK2U9cUc$4c7fS(&3vG+^XzJ5!|Be)G1(mWZ$Rk2Nc|)?CL^R6fz~f*{so)8x%ZR zVCQLPf2v@MXJoMA>lj~cm6`r8XtOzew_Jhh)cDd4(qO|;^=2>iw>>GO7mzDWm z;mykIwtcpK#>gRW!r5#7!ofs^Usdq3!gYlyO3P1br{$*$Z7Jw>D7!tfe^jtr;XMw1 z+5Gq@4OPg@mFGq{SfcQ11$A8lDoD)sz(rF7JcL;dEF>|kgK6WcF@M{xH+%qebaNm< zZR)Y8`$k*hL`rPi{Me|D;qs^How4nhjkXUA45H#pJ0-TK#IgSjLHQi!6QH&KACqDS zE|A#w*{q@GzW4a{y>Zy=2Ywp#zhO%Jp5SN+yFm-)P`?iJQESa4E|qHa@79kqa0GBg pU%Rb11L<6H>L_VLG^c^9{{Rq;hTVsUbt3=(002ovPDHLkV1hyg`=I~; literal 865 zcmV-n1D^beP)A!Wg%iFm0X z7NrY{sLEr(V@o0)3qXMlf*p@6+9)C|2*Nu!KzSq(OkPgx>)h9zE^Lxu0vyd^=FEI^ z&YbxVBO)giOZA*1I{|>;7JT!Itd#%&U>a6?^NS}f9j0M}0f44!3)fXdXN8%aipAS1 z?R1=RfZ*|$O`3Z}QlkL6W4(vhp6KkemRrwrAYN)zsc4P4Slke?IJF2YTs?OBS*!$qG zmjLFkDqB{+NVsAGk^}-X{{YbU#@x5!LNcLSBTnMo;J)gkyHJ#7A}p;O2XB~RsecP_W1*&r5cOLxSX9Zo?Awq6@qP=jOE5;u5Ah{4xqZeQn&`sAQj^SCzOeR+Ff*bAWP_e-*O>>2X7 zA7RPY$31}sT4YV>kCEg5?TP){-E!`qhOJE{<=Ml9-?&h(U;vY;!1*NA-+?4mo;Q=h~EYvRWh@BJp9k zBpmYk=j2b{lsTH}H{N!}ZPT*SmXS_Jil6(3C0!OTeQ&QFK1F- rhJ5#8@cM~c8DZ(+{CPEHp{W0V@;5;IC1-nc00000NkvXXu0mjfcVd@+ diff --git a/js/main.js b/js/main.js index 7b8aee0..28fb5b3 100644 --- a/js/main.js +++ b/js/main.js @@ -16,3 +16,9 @@ $(document).ready(function($) { $('.btn-spec').tooltip(); }); + + +$('#toggle-tabs a').click(function (e) { + e.preventDefault() + $(this).tab('show') +}); diff --git a/resources.md b/resources.md index 1c20cb9..77109da 100644 --- a/resources.md +++ b/resources.md @@ -15,14 +15,23 @@ categories: resources ### Individual Specification Documents +
+ + + +
+
#### STIX 2.1 Specification | HTML | PDF | Word | Description | | --- | --- | --- | --- | -| [**STIX 2.1 Specification**](https://docs.oasis-open.org/cti/stix/v2.1/cs01/stix-v2.1-cs01.html) | [**STIX 2.1 Specification**](https://docs.oasis-open.org/cti/stix/v2.1/cs01/stix-v2.1-cs01.pdf) | [**STIX 2.1 Specification**](https://docs.oasis-open.org/cti/stix/v2.1/cs01/stix-v2.1-cs01.docx) | Defines concepts and structure of the STIX language, domain objects, relationship objects, cyber observable objects, and meta objects. Defines the patterning language to enable the detection of possibly malicious activity on networks and endpoints | +| [**STIX 2.1 Specification**](https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02.html) | [**STIX 2.1 Specification**](https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02.pdf) | [**STIX 2.1 Specification**](https://docs.oasis-open.org/cti/stix/v2.1/cs02/stix-v2.1-cs02.docx) | Defines concepts and structure of the STIX language, domain objects, relationship objects, cyber observable objects, and meta objects. Defines the patterning language to enable the detection of possibly malicious activity on networks and endpoints | -Note: This version of the specification is no longer a multipart document. +Note: This version of the specification is no longer a multipart document. Older STIX 2.1 documents can be found [**here**](https://docs.oasis-open.org/cti/stix/v2.1/) #### TAXII 2.1 Specification @@ -30,6 +39,12 @@ Note: This version of the specification is no longer a multipart document. | --- | --- | --- | --- | | [**TAXII 2.1 Specification**](https://docs.oasis-open.org/cti/taxii/v2.1/cs01/taxii-v2.1-cs01.html) | [**TAXII 2.1 Specification**](https://docs.oasis-open.org/cti/taxii/v2.1/cs01/taxii-v2.1-cs01.pdf) | [**TAXII 2.1 Specification**](https://docs.oasis-open.org/cti/taxii/v2.1/cs01/taxii-v2.1-cs01.docx) | Defines the TAXII RESTful API and its resources along with the requirements for TAXII Client and Server implementations | +#### STIX/TAXII 2.1 Interoperability Documents + +**These documents are currently in progress.** + +
+
#### STIX 2.0 Specification @@ -54,6 +69,9 @@ Note: This version of the specification is no longer a multipart document. | [**Part 1: STIX/TAXII 2.0 Interoperability Test Document**](https://docs.oasis-open.org/cti/stix-taxii-2-interop-p1/v1.1/stix-taxii-2-interop-p1-v1.1.html) | [**Part 1: STIX/TAXII 2.0 Interoperability Test Document**](https://docs.oasis-open.org/cti/stix-taxii-2-interop-p1/v1.1/stix-taxii-2-interop-p1-v1.1.pdf) | [**Part 1: STIX/TAXII 2.0 Interoperability Test Document**](https://docs.oasis-open.org/cti/stix-taxii-2-interop-p1/v1.1/stix-taxii-2-interop-p1-v1.1.docx) | Document that provides detailed requirements on how producers of products within the threat intelligence ecosystem may demonstrate conformity with STIX/TAXII 2.0 if they wish to self-certify that their software is verified as interoperable | | [**Part 2: STIX/TAXII 2.0 Interoperability Test Document**](https://docs.oasis-open.org/cti/stix-taxii-2-interop-p2/v1.0/stix-taxii-2-interop-p2-v1.0.html) | [**Part 2: STIX/TAXII 2.0 Interoperability Test Document**](https://docs.oasis-open.org/cti/stix-taxii-2-interop-p2/v1.0/stix-taxii-2-interop-p2-v1.0.pdf) | [**Part 2: STIX/TAXII 2.0 Interoperability Test Document**](https://docs.oasis-open.org/cti/stix-taxii-2-interop-p2/v1.0/stix-taxii-2-interop-p2-v1.0.docx) | Document that provides detailed requirements on how producers of products within the threat intelligence ecosystem may demonstrate conformity with STIX/TAXII 2.0 if they wish to self-certify that their software is verified as interoperable | +
+
+
### OASIS CTI TC [Open Repositories](https://www.oasis-open.org/resources/open-repositories/){: target="_blank"}