Skip to content

Design: Restructure Instance Security Dashboard

Problem to solve

The current Instance Security Dashboard is effectively a single page housing a vulnerability list and some basic metrics information (in the form of widgets). This setup limits the potential to expand functionality and turn it into more of a "security center" that can contain related functionality such as instance-level security configurations, rules/policies, and other non-vulnerability management items.

Intended users

User experience goal

Users can see the functionality of the current single-page Instance-level dashboard broken apart into components and a new menu structure.

Proposal

Transform the current single-page experience into a new layout and menu structure that sets the framework for future expansion and specialization of security components at the Instance level. This will primarily entail breaking apart the existing page:

  • move the vulnerability list into a separate, dedicated page
  • leaving the metrics widgets as part of a "new" dashboard page
  • move Instance Dashboard configuration into a new setup/configuration area

Design

  • Initial mocks posted in design tab

📣 Vulnerability Report designs located in the project dashboard restructure

🖍 Link to Figma mocks View all levels (project, group, instance) in one location

Further details

We should be cognizant that the vulnerability list is currently a shared component across all 3 Security Dashboards. We need to be thoughtful about keeping this pattern for efficiency of future feature development while balancing against the possible complexity this might be add as Project, Group, and Instance-level lists potentially diverge in information displayed.

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by Andy Volpe