[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVE-CNA JSON Format Proposal

To: "Coffin, Chris" <ccoffin@mitre.org>, Kurt Seifried <kurt@seifried.org>
Subject: Re: CVE-CNA JSON Format Proposal
From: Art Manion <amanion@cert.org>
Date: Tue, 28 Mar 2017 10:50:58 -0400
Authentication-results: spf=none (sender IP is 129.83.29.2) smtp.mailfrom=LISTS.MITRE.ORG; mitre.mail.onmicrosoft.com; dkim=none (message not signed) header.d=none;mitre.mail.onmicrosoft.com; dmarc=none action=none header.from=cert.org;
Cc: "Booth, Harold (Fed)" <harold.booth@nist.gov>, cve-editorial-board-list <cve-editorial-board-list@lists.mitre.org>
Delivery-date: Tue Mar 28 11:26:36 2017
Dkim-filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu v2SEp3ZI040676
In-reply-to: <MWHPR09MB14856D1A82B27AA9D98F9A00A1330@MWHPR09MB1485.namprd09.prod.outlook.com>
List-help: <mailto:LISTSERV@LISTS.MITRE.ORG?body=INFO%20CVE-EDITORIAL-BOARD-LIST>
List-owner: <mailto:CVE-EDITORIAL-BOARD-LIST-request@LISTS.MITRE.ORG>
List-subscribe: <mailto:CVE-EDITORIAL-BOARD-LIST-subscribe-request@LISTS.MITRE.ORG>
List-unsubscribe: <mailto:CVE-EDITORIAL-BOARD-LIST-unsubscribe-request@LISTS.MITRE.ORG>
References: <CY4PR09MB1255F37BD20E03336BDE025AE63D0@CY4PR09MB1255.namprd09.prod.outlook.com> <e8f6e4e4-080d-14ce-998a-3b9bccaec013@cert.org> <CABqVa38X1wKQyRJYUOsg0pDR9++QT_-6SZig6nGqND6uw9gQ2Q@mail.gmail.com> <8120ae8d-d9e6-cb66-ffe0-372f34c44ddf@cert.org> <CABqVa3_2N5=XGK12C3pgBgnqTdUnZJ72+s06mXJHD0Ke5O8JCQ@mail.gmail.com> <MWHPR09MB14856D1A82B27AA9D98F9A00A1330@MWHPR09MB1485.namprd09.prod.outlook.com>
Sender: <owner-cve-editorial-board-list@lists.mitre.org>
Spamdiagnosticmetadata: 6cdb8bfc89744bd8bfee511e3e65aa05
Spamdiagnosticoutput: 1:2
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

On 2017-03-27 19:01, Coffin, Chris wrote:

> Art: Are you ok with moving forward if we just make sure to include
> ASSIGNER as part of the minimum JSON format?

Absolutely.

In a more distributed CVE world, I envision CNAs publishing CVE JSON
(...over a standard transport like RSS/Atom...) and users choosing which
feeds to consume.  MITRE and any other aggregators could consume all the
CNA feeds, hopefully automating that part of the process.

In a world of JSON blobs everywhere, knowing ASSIGNER seems to be more
important.

 - Art

Follow-Ups:
- RE: CVE-CNA JSON Format Proposal
  - From: "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>

References:
- CVE-CNA JSON Format Proposal
  - From: "Booth, Harold (Fed)" <harold.booth@nist.gov>
- Re: CVE-CNA JSON Format Proposal
  - From: Art Manion <amanion@cert.org>
- Re: CVE-CNA JSON Format Proposal
  - From: Kurt Seifried <kurt@seifried.org>
- Re: CVE-CNA JSON Format Proposal
  - From: Art Manion <amanion@cert.org>
- Re: CVE-CNA JSON Format Proposal
  - From: Kurt Seifried <kurt@seifried.org>
- RE: CVE-CNA JSON Format Proposal
  - From: "Coffin, Chris" <ccoffin@mitre.org>

Prev by Date: Re: CVE-CNA JSON Format Proposal
Next by Date: Re: CVE-CNA JSON Format Proposal
Previous by thread: Re: CVE-CNA JSON Format Proposal
Next by thread: RE: CVE-CNA JSON Format Proposal
Index(es):
- Date
- Thread