Context
I needed to design and define the behavior of the following features: the user needs one place in the product to observe and mitigate top-attacked policies/applications and top attacks in general. Take action on the following use case: improve false positives, improve false negatives.
I was assigned to this project because of my experience in creating user experiences and user interfaces in websites/mobile apps/operating systems; I assisted the team with understanding the context of the product and the users it would serve.
I was assigned to this project because of my experience in creating user experiences and user interfaces in websites/mobile apps/operating systems; I assisted the team with understanding the context of the product and the users it would serve.
Goals: Explore how today the user performs those actions on older F5 products and gather user insights regarding feature usage: pain points and strengths points. Based on that - define and design a new "Dashboard" feature.
Team: I led the project and collaborated with PM, front-end developers, and back-end developers.
Work Type: Agile.
Success Metrics: Users will successfully observe top-attacked policies/applications along with top attacks in general and mitigate the attacks.
Users will successfully take action on false positives and false negatives.
Persona: SecOps
Talk to potential users
During the Research, I figured out how many steps and screens the users needed to perform to operate the system in older products.
This is how it works on F5 old products:
Design Iterations
Final Design
Main Dashboard. The user can filter from any widget
The user adds exception based on dashboard info & deploys the policy
Conclusions
