| 1 |
CVSS v2/v3 use in CVRF 1.2 |
17 |
Apr 2017 |
| 2 |
Modified: OASIS CSAF TC MONTHLY MEETING |
12 |
Feb 2017 |
| 3 |
I see a CSAF meeting on my calendar for tomorrow |
8 |
Oct 2017 |
| 4 |
Modified: OASIS CSAF TC Monthly Meeting |
8 |
Nov 2018 |
| 5 |
[OASIS Issue Tracker] (CSAF-20) Analysis of CVE Automation and JSON format |
6 |
Feb 2017 |
| 6 |
Re: [csaf] CVSS v2/v3 use in CVRF 1.2 |
6 |
Apr 2017 |
| 7 |
OASIS CSAF TC MONTHLY MEETING |
6 |
Nov 2017 |
| 8 |
[CSAF JSON Schema] Combining "document____" properties |
6 |
May 2018 |
| 9 |
[CSAF JSON Schema] Follow-on discussion about language support |
6 |
May 2018 |
| 10 |
Generic Software Identification Parameter/Attribute to be included in CSAF 2.0 schema. |
6 |
Nov 2018 |
| 11 |
Motion to request a SMV for CSAF to submit to ISO |
6 |
Feb 2023 |
| 12 |
Motion to elect the TC secretary |
6 |
Sep 2023 |
| 13 |
Motion to publish approved errata 01 of CSAF v2.0 Re: [csaf] was: Invitation to comment on Common Security Advisory Framework v2.0 Errata 01 - ends January 4th |
6 |
Jan 2024 |
| 14 |
[OASIS Issue Tracker] (CSAF-4) Analysis of "Application Vulnerability Description Language (AVDL)" and any possible relation to CSAF work products |
5 |
Feb 2017 |
| 15 |
Groups - PDF - CSAF Common Vulnerability Reporting Framework (CVRF) Version 1.2 uploaded |
5 |
Mar 2017 |
| 16 |
CSAF JSON Schema - specifying the language of the document? |
5 |
May 2018 |
| 17 |
Contemplating how to describe products in JSON. |
5 |
Nov 2018 |
| 18 |
Item: Various possible enhancements to the JSON format for representing vulnerabilities |
5 |
Aug 2019 |
| 19 |
Notice of upcoming change to OASIS TC Open Repositories |
5 |
Oct 2019 |
| 20 |
Suggestion to postpone the April meeting to May 4 |
5 |
Apr 2022 |
| 21 |
Inviting nominations for Chair of OASIS Common Security Advisory Framework (CSAF) TC |
4 |
Nov 2016 |
| 22 |
Groups - Zip(schemas) - CSAF Common Vulnerability Reporting Framework (CVRF) Version 1.2 uploaded |
4 |
Mar 2017 |
| 23 |
[OASIS Issue Tracker] (CSAF-28) Proposal for CVSS future embrace |
4 |
Apr 2017 |
| 24 |
RE: [csaf] Proposal for CVSS future embrace |
4 |
Apr 2017 |
| 25 |
Meeting cancelled today? |
4 |
Jul 2017 |
| 26 |
CSAF Documentation Website at the GitHub Open Repository |
4 |
Nov 2017 |
| 27 |
Modified: OASIS CSAF TC MONTHLY MEETING |
4 |
Feb 2018 |
| 28 |
Today's meeting cancelled? |
4 |
Mar 2018 |
| 29 |
[OASIS Issue Tracker] (CSAF-33) Crate a JSON Schema for CSAF 2.0 |
4 |
Apr 2018 |
| 30 |
CSAF JSON Schema - remove a level of nesting for lists of things. |
4 |
May 2018 |
| 31 |
CSAF product identification and version numbers |
4 |
Jan 2019 |
| 32 |
Modified: OASIS CSAF TC working session |
4 |
May 2019 |
| 33 |
Switching to use the first.org JSON schemas for CVSS scoring - issue #1 |
4 |
Nov 2019 |
| 34 |
Switching to use the first.org JSON schemas for CVSS scoring - issue #2 |
4 |
Nov 2019 |
| 35 |
Would CSAF be appropriate for SBOM VEX? |
4 |
Feb 2021 |
| 36 |
Hashtag for CSAF |
4 |
May 2021 |
| 37 |
E-Mail motion to submit current editor draft as CSD 01 / CSDPR 01 |
4 |
Jul 2021 |
| 38 |
Fwd: Email sent to voters re: [csaf] Groups - Ballot closed: "Vote on Common Security Advisory Framework Version 2.0 with Non-Material Changes as a CS?" |
4 |
Nov 2021 |
| 39 |
Common Security Advisory Framework v2.0 from CSAF TC approved as a Committee Specification |
4 |
Nov 2021 |
| 40 |
Data on Use of CSAF VEX profile |
4 |
May 2023 |
| 41 |
Groups - Draft visual representation of TC issue workflow uploaded |
3 |
Nov 2016 |
| 42 |
Groups - Draft visual representation of TC issue workflow (source) uploaded |
3 |
Nov 2016 |
| 43 |
[OASIS Issue Tracker] (CSAF-12) Document CSAF TC meeting collaboration and minuting chat |
3 |
Dec 2016 |
| 44 |
backward compatibility in 1.2 clarification |
3 |
Jan 2017 |
| 45 |
[OASIS Issue Tracker] (CSAF-21) zero or more CVSSv3 scores, overall CVSS logic |
3 |
Feb 2017 |
| 46 |
Groups - CSAF Common Vulnerability Reporting Framework (CVRF) Version 1.2 uploaded |
3 |
Mar 2017 |
| 47 |
Issue on p.1 of draft? |
3 |
Mar 2017 |
| 48 |
Perhaps foolish of me to have done so, but I did an editing pass on draft of 1.2 |
3 |
Apr 2017 |
| 49 |
Request submitted "Publish Committee Draft and release for public review" |
3 |
May 2017 |
| 50 |
CSAF Common Vulnerability Reporting Framework (CVRF) V1.2 is now a Committee Specification |
3 |
Sep 2017 |
| 51 |
[OASIS Issue Tracker] (CSAF-33) Create a JSON Schema for CSAF 2.0 |
3 |
Apr 2018 |
| 52 |
First question that comes up when creating a JSON schema - what's the naming convention for fields? |
3 |
Apr 2018 |
| 53 |
CSAF JSON Schema - what to do about product statuses? |
3 |
May 2018 |
| 54 |
[CSAF JSON Schema] limits to field lengths |
3 |
May 2018 |
| 55 |
[OASIS Issue Tracker] (CSAF-34) CSAF 2.0 Localization Support |
3 |
May 2018 |
| 56 |
Groups - Minutes of 2018-05-30 Meeting#16.html uploaded |
3 |
Jun 2018 |
| 57 |
FYI, I submitted a pull request to consolidate document related properties. |
3 |
Jun 2018 |
| 58 |
Pull request just sent... "lang" changes |
3 |
Nov 2018 |
| 59 |
design "version" in json |
3 |
Nov 2018 |
| 60 |
Groups - Minutes of CSAF Monthly Meeting on 2019-04-24 modified |
3 |
Jul 2019 |
| 61 |
CSAF 2.0 JSON Schema Visualizer |
3 |
Aug 2019 |
| 62 |
Switching to use the first.org JSON schemas for CVSS scoring - issue #3 |
3 |
Nov 2019 |
| 63 |
Suggested enhancements to CSAF spec |
3 |
Apr 2020 |
| 64 |
CSAF presentation & Where to find CSAF documents |
3 |
Jan 2021 |
| 65 |
CSAF member support for SBOM use of CSAF |
3 |
Mar 2021 |
| 66 |
broken announcement links |
3 |
Apr 2021 |
| 67 |
Provider Metadata - Feedback needed |
3 |
Jul 2021 |
| 68 |
E-Mail motion to submit current editor draft as CS 01 / CSPR 01 |
3 |
Oct 2021 |
| 69 |
Four small notes on our minutes of meeting |
3 |
Oct 2021 |
| 70 |
Motion requesting that TC Administration hold a Special Majority Vote to approve Common Security Advisory Framework Version 2.0, Committee Specification 01 |
3 |
Oct 2021 |
| 71 |
Motion to start work on committee note - WhatÂs new in CSAF 2.0 |
3 |
Oct 2021 |
| 72 |
CSAF - Statement of use (Template) |
3 |
Jan 2022 |
| 73 |
Meeting tomorrow |
3 |
May 2022 |
| 74 |
General CSAF Overview Slides Needed |
3 |
Jun 2022 |
| 75 |
Statement Of Use |
3 |
Jul 2022 |
| 76 |
CSAF v2.0 Press Release & Call for Sponsor Quotes |
3 |
Oct 2022 |
| 77 |
OpenVEX at OSSF |
3 |
Mar 2023 |
| 78 |
CSAF draft to JTC 1 SC 27, for any nits or improvement. Target to send: 31 July |
3 |
Jul 2023 |
| 79 |
[Motion] #530 |
3 |
Oct 2023 |
| 80 |
Approved Errata for Common Security Advisory Framework v2.0 published |
3 |
Feb 2024 |
| 81 |
Proposal to create JIRA instance for tracking TC work |
2 |
Nov 2016 |
| 82 |
Groups - TC CSAF Issue Processing Workflow Proposal uploaded |
2 |
Nov 2016 |
| 83 |
Groups - Minutes of 2016-12-14 Meeting#2 uploaded |
2 |
Dec 2016 |
| 84 |
CVRF 1.2 and Support for CVSSv3 |
2 |
Jan 2017 |
| 85 |
Groups - CSAF Common Vulnerability Reporting Framework (CVRF) Version 1.2 uploaded |
2 |
Feb 2017 |
| 86 |
Groups - CSAF CVRF v1.2 CSD01 WD01 uploaded |
2 |
Mar 2017 |
| 87 |
Use of informal "info" instead of information in places throughout the draft |
2 |
Mar 2017 |
| 88 |
Spurious paragraph in section 2 |
2 |
Mar 2017 |
| 89 |
Groups - Minutes of 2017-03-29 Meeting#5 uploaded |
2 |
Apr 2017 |
| 90 |
Re: [csaf] Persistent non-voting Member Status |
2 |
Apr 2017 |
| 91 |
Groups - Minutes of 2017-06-28 Meeting#8 uploaded |
2 |
Jun 2017 |
| 92 |
Sponsorship opportunities for Borderless Cyber Conference & FIRST Technical Symposium on CTI, 6-7 December, Prague |
2 |
Jul 2017 |
| 93 |
[OASIS Issue Tracker] (CSAF-30) CSD01 WD01 Review comments from Beth Pumo |
2 |
Aug 2017 |
| 94 |
[OASIS Issue Tracker] (CSAF-9) Consider the creation of a GitHub-based website |
2 |
Sep 2017 |
| 95 |
[OASIS Issue Tracker] (CSAF-14) Add CVSSv3 support to CVRF |
2 |
Sep 2017 |
| 96 |
Request an OASIS Open Repository project be created |
2 |
Oct 2017 |
| 97 |
CSAF JSON Schema - distinction between an array of instances and just one instance. |
2 |
May 2018 |
| 98 |
[OASIS Issue Tracker] (CSAF-35) CSAF 2.0 Product Representation |
2 |
May 2018 |
| 99 |
Notes on localization - analysis of STIX and applicability to CSAF |
2 |
Jun 2018 |
| 100 |
Requesting leave of absence from CSAF TC - July 23 - 27 |
2 |
Jul 2018 |
| 101 |
Discussion on Generic Software Identification Parameter/Attribute |
2 |
Oct 2018 |
| 102 |
Request for leave of absence |
2 |
Nov 2018 |
| 103 |
Groups - Minutes of CSAF Monthly Meeting on 2019-01-09 uploaded |
2 |
Jan 2019 |
| 104 |
FYI: Submitted pull request for changes to CSAF JSON schema |
2 |
Apr 2019 |
| 105 |
Groups - Minutes of CSAF Monthly Meeting on 2019-03-27 modified |
2 |
May 2019 |
| 106 |
CSAF 2.0 JSON schema draft review elements |
2 |
Jun 2019 |
| 107 |
On vacation for this week |
2 |
Jul 2019 |
| 108 |
Groups - Minutes of CSAF working Meeting on 2019-5-15-19.pdf modified |
2 |
Jul 2019 |
| 109 |
Groups - Minutes of CSAF working Meeting on 2019 -7-17 uploaded |
2 |
Jul 2019 |
| 110 |
Making progress on documenting CSAF specification |
2 |
Apr 2020 |
| 111 |
Sad news |
2 |
May 2020 |
| 112 |
Overview of CSAF web sites |
2 |
May 2020 |
| 113 |
Groups - Minutes of CSAF Monthly Meeting on June 24, 2020 modified |
2 |
Jul 2020 |
| 114 |
Groups - Minutes of CSAF Monthly Meeting on September 2, 2020 uploaded |
2 |
Sep 2020 |
| 115 |
Groups - Minutes of CSAF Monthly Meeting on November 25 2020 modified |
2 |
Jan 2021 |
| 116 |
RE: [csaf] Motion to reappoint and approve Omar Santos as chair of the OASIS CSAF TC |
2 |
Apr 2021 |
| 117 |
RE: [csaf] E-Mail motion for Thomas Schmidt to become a co-editor |
2 |
Apr 2021 |
| 118 |
Groups - Minutes of CSAF Monthly Meeting Feb 24, 2021 uploaded |
2 |
Apr 2021 |
| 119 |
A Special Majority Vote to re-consider a charter clarification has been set up |
2 |
Apr 2021 |
| 120 |
Groups - Minutes of OASIS CSAF TC Working Meeting April 14 2021 uploaded |
2 |
Apr 2021 |
| 121 |
A shared vulnerability format for open-source packages |
2 |
Apr 2021 |
| 122 |
RE: [csaf] We are still at least 2 votes short from approval of CS01 |
2 |
Nov 2021 |
| 123 |
Re: [csaf] That is good news - 14 of 17 in favor already |
2 |
Nov 2021 |
| 124 |
version range defined in CVE JSON 5.0 |
2 |
Mar 2022 |
| 125 |
Link to request we publish a CSD and put it out for public review |
2 |
Mar 2022 |
| 126 |
CSAF 2.0 CSD02 request |
2 |
Apr 2022 |
| 127 |
CSAF Editorial changes needed for OASIS standard |
2 |
Jul 2022 |
| 128 |
Motion to approve CS03 |
2 |
Jul 2022 |
| 129 |
Motion to register "hash" and "signature" |
2 |
Sep 2022 |
| 130 |
CSAF Announcement - Blog and webinar opportunity |
2 |
Sep 2022 |
| 131 |
still TLP 1.0 in CSAF 2.0? |
2 |
Nov 2022 |
| 132 |
A Special Majority Vote to consider submitting Common Security Advisory Framework V2.0 OS to ISO has been set up |
2 |
Feb 2023 |
| 133 |
Three IANA registrations completed for CSAF v2.0 |
2 |
Feb 2023 |
| 134 |
Member Review of Proposed Submission of CSAF V2.0 OASIS Standard to ISO/IEC JTC1 SC 27 |
2 |
Feb 2023 |
| 135 |
IANA registration of "csaf" as a ROLIE feed type is complete (with IANA comment) |
2 |
Apr 2023 |
| 136 |
Submit a talk for Borderless Cyber 2023 by 26 May |
2 |
May 2023 |
| 137 |
CISA Adds OASIS CSAF 2.0 Standard to ICS Advisories |
2 |
Sep 2023 |
| 138 |
[Motion] #616 |
2 |
Oct 2023 |
| 139 |
[Motion] #652 |
2 |
Nov 2023 |
| 140 |
Receipt for CSAF v2.0 Errata01 starter pack |
2 |
Dec 2023 |
| 141 |
E-Mail motion to progress the CSAF v2.0 Errata01-CSD01 |
2 |
Dec 2023 |
| 142 |
Ballot upcoming |
2 |
Dec 2023 |
| 143 |
Tell Us Your Thoughts on the CSAF TC - Please take this short survey! |
2 |
Dec 2023 |
| 144 |
Upcoming OCA CASP Plugfest |
2 |
Jan 2024 |
| 145 |
Call for Participation: OASIS Common Security Advisory Framework (CSAF) TC |
1 |
Oct 2016 |
| 146 |
Modified: OASIS Common Security Advisory Framework (CSAF) TC Inaugural Meeting |
1 |
Oct 2016 |
| 147 |
IMPORTANT: Deadline for joining as an eligible voter for the CSAF TC first meeting |
1 |
Nov 2016 |
| 148 |
Offering to serve as secretary to the TC |
1 |
Nov 2016 |
| 149 |
List of eligible voting members for the CSAF TC inaugural meeting |
1 |
Nov 2016 |
| 150 |
New Member Orientation |
1 |
Nov 2016 |
| 151 |
Monthly CSAF TC Meetings |
1 |
Nov 2016 |
| 152 |
OASIS CSAF TC Comment List has been activated |
1 |
Nov 2016 |
| 153 |
test (ignore) |
1 |
Nov 2016 |
| 154 |
Groups - Minutes of 2016-11-16 Meeting#1 uploaded |
1 |
Nov 2016 |
| 155 |
Public link to minutes draft from inaugural meeting (#1) |
1 |
Nov 2016 |
| 156 |
Groups - Action Item "Create Github repository for standards track work" added |
1 |
Nov 2016 |
| 157 |
Form submission from: Request a JIRA, wiki or version control instance for your TC |
1 |
Nov 2016 |
| 158 |
CSAF TC: Your JIRA project is ready to use |
1 |
Nov 2016 |
| 159 |
List of useful OASIS resources for your TC |
1 |
Nov 2016 |
| 160 |
Two opportuinities for use of GitHub repositories by the OASIS CSAF TC |
1 |
Nov 2016 |
| 161 |
Form submission from: Request TC document folders be created |
1 |
Nov 2016 |
| 162 |
Your folders are set up |
1 |
Nov 2016 |
| 163 |
Groups - CVRF v1.1 Dictionary of Elements uploaded |
1 |
Nov 2016 |
| 164 |
Groups - The Missing Manual: CVRF 1.1 uploaded |
1 |
Nov 2016 |
| 165 |
Groups - CVRF v1.1 Mindmap uploaded |
1 |
Nov 2016 |
| 166 |
Groups - CVRF 1.1 Common Data Types uploaded |
1 |
Nov 2016 |
| 167 |
Groups - CVRF v1.1 Dictionary Schema uploaded |
1 |
Nov 2016 |
| 168 |
Groups - TC CSAF Issue Processing Workflow Proposal (Source) uploaded |
1 |
Nov 2016 |
| 169 |
Monthly meetings update |
1 |
Nov 2016 |
| 170 |
Groups - Doodle Results for Monthly Meeting Selection uploaded |
1 |
Nov 2016 |
| 171 |
Groups - Action Item "Create Github repository for standards track work" Modified |
1 |
Dec 2016 |
| 172 |
Fwd: Nominate Your Interoperability Solution: Deadline Dec. 15 |
1 |
Dec 2016 |
| 173 |
OASIS press release to announce CSAF TC |
1 |
Dec 2016 |
| 174 |
Raw chat trace of meeting #2 - 2016-DEC-14 |
1 |
Dec 2016 |
| 175 |
Groups - Minutes of 2016-11-16 Meeting#1 modified |
1 |
Dec 2016 |
| 176 |
CSAF TC GitHub Sandbox and CVRF 1.2 proposed schema |
1 |
Dec 2016 |
| 177 |
Sponsor quotes for CSAF press release due this week |
1 |
Jan 2017 |
| 178 |
Re: Sponsor quotes for CSAF press release: deadline extended |
1 |
Jan 2017 |
| 179 |
Promote CSAF TC press release |
1 |
Jan 2017 |
| 180 |
Borderless Cyber Call for Presentations Closes Today |
1 |
Jan 2017 |
| 181 |
Standard Agenda draft for todays meeting |
1 |
Jan 2017 |
| 182 |
Groups - Minutes of 2016-12-14 Meeting#2 modified |
1 |
Jan 2017 |
| 183 |
Raw chat trace of meeting #3 - 2017-JAN-25 |
1 |
Jan 2017 |
| 184 |
Groups - CSAF TC January Monthly Call Presentation uploaded |
1 |
Jan 2017 |
| 185 |
HTTP scheme URIs for namespace identifiers |
1 |
Jan 2017 |
| 186 |
Groups - Minutes of 2017-01-25 Meeting#3 uploaded |
1 |
Jan 2017 |
| 187 |
Raw minutes from chat meeting #4 on 2017-FEB-22 |
1 |
Feb 2017 |
| 188 |
CVSS logic |
1 |
Feb 2017 |
| 189 |
Form submission from: Request a template / starter document |
1 |
Feb 2017 |
| 190 |
Starter Document for CSAF Common Vulnerability Reporting Framework (CVRF) Version 1.2 |
1 |
Feb 2017 |
| 191 |
Invitation to sponsor OASIS Borderless Cyber NYC 2017 |
1 |
Feb 2017 |
| 192 |
OASIS Security Standards Showcase for RSA 2018: Reserve now. |
1 |
Mar 2017 |
| 193 |
First revision of CSAF CVRF v1.2 CSD01 WD01 (2017-03-10) available |
1 |
Mar 2017 |
| 194 |
Borderless Cyber USA 2017 – C-Suite discuss cyber economics in NYC |
1 |
Mar 2017 |
| 195 |
Groups - Minutes of 2017-02-22 Meeting#4 uploaded |
1 |
Mar 2017 |
| 196 |
Groups - Editor notes on the CSAF CVRF v1.2 CSD01 WD01 2017-03-24 revision uploaded |
1 |
Mar 2017 |
| 197 |
Agenda draft for meeting #5 on 2017-03-29 (today) |
1 |
Mar 2017 |
| 198 |
Raw chat trace of meeting #5 - 2017-MAR-29 |
1 |
Mar 2017 |
| 199 |
Motion to approve the Minutes from Previous Meeting #4 (2017-02-22) |
1 |
Mar 2017 |
| 200 |
RE: [csaf] Motion to approve the Minutes from Previous Meeting #4 (2017-02-22) |
1 |
Mar 2017 |
