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
And this got me thinking that we probably have some refinements we can do in that area:
improving how triage is displayed across reports (e.g apparently it's missing in PDF right now)
allowing further customization of reports based on triage
adding how-to guides on common triage scenarios such as...
"how to triage false positives"
"how to add triage comments" (e.g. extended information about mitigations used for a cve which isn't yet fixed)
"how to re-use triage in other projects using merged reports" (e.g. use the triage from a docker base image across multiple projects using the same base)
"tracking changing triage and fixes over time using merged reports"
-Improving, creating, or recommending tools to help with triage data. We have some, but probably not everything anyone could want here. Do we need a command line "add triage to file" option, for example?
Difficulty: Intermediate to Advanced
Hours: 175 or 350 depending on how many of these ideas you propose to tackle. Simple triage display fixes and documentation is likely a 175 hour project, students intending to add additional triage tools and triage-customized reports would likely want to apply for a 350hr slot.
Open to all:
This work was previously flagged as a potential GSoC project, but we didn't get an applicants interested in doing it at that time. It's now available to anyone who wants to work in this area.
The text was updated successfully, but these errors were encountered:
terriko
added
the
gsoc
Tasks related to our participation in Google Summer of Code
label
Mar 28, 2022
The new VEX feature (#1570) may also be worth considering as this offers facilities to support the triage process by using a JSON file. Maybe consider adding some tooling to manipulate the status of a vulnerability rather than just using an editor to edit a large JSON file.
This one didn't happen in GSoC 2022, so I'm going to remove the reserved note and stuff above.
terriko
changed the title
GSoC 2022 idea: Reporting and Triage improvements
Reporting and Triage improvements (was a GSoC idea, now available to all)
Jun 16, 2022
Possible GSoC idea: Reporting and Triage improvements
I just filed 4 feature requests related to the report UI and how we display triage data:
And this got me thinking that we probably have some refinements we can do in that area:
-Improving, creating, or recommending tools to help with triage data. We have some, but probably not everything anyone could want here. Do we need a command line "add triage to file" option, for example?
Difficulty: Intermediate to Advanced
Hours: 175 or 350 depending on how many of these ideas you propose to tackle. Simple triage display fixes and documentation is likely a 175 hour project, students intending to add additional triage tools and triage-customized reports would likely want to apply for a 350hr slot.
Open to all:
This work was previously flagged as a potential GSoC project, but we didn't get an applicants interested in doing it at that time. It's now available to anyone who wants to work in this area.
The text was updated successfully, but these errors were encountered: