Hi Tod,
Someone can correct me if I'm wrong but the conversation, as I recall, was 
around storing change history with regards to GDPR considerations.  MITRE 
lawyers are digging into the implications and Madison Oliver is also doing some 
research on behalf of Github and GDPR.

From: Tod Beardsley <tod_beards...@rapid7.com>
Sent: Tuesday, January 24, 2023 5:39 PM
To: Art Manion <zman...@protonmail.com>
Cc: Landfield, Kent <kent.landfi...@trellix.com>; CVE Program Secretariat 
<cve-prog-secretar...@mitre.org>; CVE Editorial Board Discussion 
Subject: [EXTERNAL] Re: CVE Board Meeting Summary: January 18, 2023

I would expect so, Art. Is this a controversial issue? I assume there's some 
context and nuance here.

And yes, I'm fully prepared to take my absentee lumps, Kent. 8am Wednesdays are 
no longer really great for me for calls (though it looks like I can join on the 
bottom half pretty often).

On Tue, Jan 24, 2023 at 3:58 PM Art Manion 
<zman...@protonmail.com<mailto:zman...@protonmail.com>> wrote:
On 2023-01-24 16:48, Kent Landfield wrote:

> Reach out to the CNA community to gauge how important CVE Record Change 
> History is to them.

Opinion:  CVE Record change history should be fully public and transparent.

While partially a separate question, this could be provided through a git repo 
of JSON files.

  - Art

NOTICE OF CONFIDENTIALITY: At Rapid7, the privacy of our customers, partners, 
and employees is paramount. If you received this email in error, please notify 
the sender and delete it from your inbox right away. Learn how Rapid7 handles 
privacy at 
 To opt-out of Rapid7 marketing emails, please click 
 or email priv...@rapid7.com<mailto:priv...@rapid7.com>.

Reply via email to