Request to add CVE column to Security Advisory list in Wiki

mrottlander commented 3 years ago

@smaliakkal - could we add more columns to the Security Advisory table in the Wiki? At least the CVE's need to be in the list, optimal with short topic column. Customer security teams tend to query for certain CVE's if they are fixed. In the current documentation we'd need to open each advisory and search for the CVE.

smaliakkal commented 3 years ago

@mrottlander

Thanks for suggestion. We will discuss about this change and will update accordingly.

Vilocify commented 2 years ago

@smaliakkal

Seems like this change in the security advisories wiki pages was implemented, however it introduced some breaking changes in the way we track them:

You changed the format of the Advisory ID, excluding the version from it. Tools like nessus still use the old format, see: https://www.tenable.com/plugins/nessus/155853. Is there a rationale behind this change that justifies changing the Advisory ID of all old published advisories?
In the new Security Advisory list one of the columns is titled Publish Date, which is actually the Issue Date which differs from the date the advisory is available to the public. We suggest tracking them separately as "Issue Date" and "Publish Date", or clarifying why they differ.

vmware / photon

Request to add CVE column to Security Advisory list in Wiki #1212