You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider the addition of Date of First Known Exploitation (first_known_exploitation_date)
Background information:
As discussed in today's meeting (2024-12-18) and as a follow up to Stefan's statement above, we will also create a new issue to address address the second element discussed here (Date of First Known Exploitation (first_known_exploitation_date)) in a separate issue.
The issue was further discussed during the 2024-12-18 TC meeting with focus on part 1 renaming the existing field release_date to disclosure_date. Omar moved to reinstate the field name for the date a vulnerability was first published from release_date to disclosure_date, Denny seconded. No discussion, no objections, the motion carries.
The text was updated successfully, but these errors were encountered:
santosomar
changed the title
As discussed in today's meeting (2024-12-18) and as a follow up to [Stefan's statement above](https://github.com/oasis-tcs/csaf/issues/782#issuecomment-2552050595), we will also create a new issue to address address the second element discussed here (Date of First Known Exploitation (first_known_exploitation_date)) in a separate issue.
Date of First Known Exploitation (first_known_exploitation_date):
Dec 18, 2024
santosomar
changed the title
Date of First Known Exploitation (first_known_exploitation_date):
Date of First Known Exploitation (first_known_exploitation_date)
Dec 18, 2024
Consider the addition of Date of First Known Exploitation (
first_known_exploitation_date
)Background information:
As discussed in today's meeting (2024-12-18) and as a follow up to Stefan's statement above, we will also create a new issue to address address the second element discussed here (Date of First Known Exploitation (
first_known_exploitation_date
)) in a separate issue.Originally posted by @santosomar in #782 (comment)
The text was updated successfully, but these errors were encountered: