Design: Explore viable UX for app sec triage experience
Problem to solve
With the implementation of Stand-alone vulnerabilities MVC We are adding new data to the vulnerabilities, mainly in the form of status. This will add a new layer of information that we can leverage in addition to severity, for metrics and charting. This will also add additional UI complexity to the vulnerability list and we need better understand and explore our options for which elements should get visual priority and which elements need to have a different UI treatment.
Problem statement
HMW organize the information on the vulnerability list to create the ultimate triage experience
Intended users
- Primary Sasha (Software Developer)
- Primary Sam (Security Analyst)
Further details
- TBD (placeholder)
Proposal
- Provide a scalable solution that anticipates additions to the vulnerability list well into 2020.
- Provide a validated MVC for the initial implementation
- Provide a plan for iterating into the ideal experience
Designs / Concepts
| Detected list (default_view) | Confirmed list | Resolved list | Dismissed list |
|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
Page level changes:
in progress
Detected list changes
in progress
Confirmed list changes
in progress
Resolved list changes
in progress
Dismissed list changes
in progress
Proposed workflow:
in progress
Testing
Testing should be done to validate if our proposed solution is:
- Solves our users need in a similar or more efficient manner
- Is easily understood by users
- (Bonus) Enhances the overall aesthetics of our dashboards
Links / references
Edited by Matt Wilson



