Skip to content

Frontend update for Continuous Vulnerability Scanning

Problem to solve

With the introduction of CVS, customers may be confused by the "Last Updated [timestamp]" text on the Vulnerability Report. Previously, this indicated the last time a security job was run. With CVS, a new vulnerability could be found after the job has run, which would make the timestamp and timeline confusing for someone investigating when a vulnerability was found.

Proposal

  • In all cases, update the Vulnerability Report's "last updated" widget so the text indicates "Security reports last updated [timestamp]."
  • For customers who have enabled dependency scanning or container scanning, update the Vulnerability Report's "last updated" widget so the text indicates "Security reports last updated [timestamp]" and "SBOMs last updated [timestamp]."

Designs

Screenshot_2023-07-19_at_9.39.03_AM

Intended users

Rough Implementation Plan

  • In ee/app/assets/javascripts/security_dashboard/vulnerability_report_init.js add timestamp for pipeline type thats generate SBOMS. Right now only dependency scanning actually creates SBOMS. Container Scanning is in progress.

At the project, level HAML templates, define the timestamp.

ee/app/views/security/vulnerabilities/index.html.haml

ee/app/views/projects/security/vulnerability_report/index.html.haml

Update Ruby Presenter

Findings to follow-up on

  • Seems like looking at the code we only expose last pipeline run data at the Project level. Need to confirm if we see it at the Group and Instance level currently. It appears that the UI does not for group or instance levels.

See for group level: https://gitlab.com/groups/gitlab-org/-/security/vulnerabilities

Instance Level: Need to get screenshot set up locally. But I'm pretty confident we don't show it.

Edited by Fernando Cardenas