top of page
attack path Desktop HD Copy 4.png
armo logo.png

Attack Path

Product feature, UX/UI

'Attack Path' empowers Kubernetes users to proactively visualize and neutralize security threats.


In response to the ever-evolving landscape of cybersecurity and the challenges faced by DevOps and DevSecOps users in Kubernetes environments, we introduced the 'Attack Path' feature. This feature serves as a strategic roadmap for defending against potential threats by mapping out attack sequences that exploit security weaknesses. Our goal was to empower users to prioritize and address security issues effectively.


As a product designer at ARMO, my role in this project was to conceptualize, design, and contribute to the implementation of the 'Attack Path' feature. I worked closely with cross-functional teams, ensuring that user-centric design principles were at the forefront of our efforts. My contributions influenced the design decisions that led to the feature's successful implementation.


In today's world of limited time, we need to be laser-focused on our priorities. This goes double for mission-critical activities, like cybersecurity. We want to prioritize fixing the issues that have the most significant impact on our security posture.


An attack path is like a roadmap for attackers, outlining the steps they can take to exploit security weaknesses. They start from an initial entry point and navigate through vulnerabilities and misconfigurations to reach valuable assets, aiming to steal data or cause harm.


The importance of mapping attack paths is that it allows you to concentrate on the activities that generate the most value for your cyber security defense. In an environment like Kubernetes that is constantly changing and can include thousands of different weaknesses (misconfigurations, vulnerabilities and access control), the question as to which step and weakness to concentrate on, becomes even more pressing.


With the release of the new attack path feature, ARMO is enabling Kubernetes users to easily find the answer. It enables teams to prioritize work and offers ways to fix security issues based on their real impact. Issues are addressed in context, instead of in isolation. Thus, making your security investment much more effective.

Our journey to develop the 'Attack Path' feature began with a deep dive into understanding the unique challenges and pain points faced by DevOps and DevSecOps professionals within Kubernetes environments. We recognized that the key to effective cybersecurity in Kubernetes lay in identifying and mitigating vulnerabilities and misconfigurations efficiently. To achieve this, robust user research was essential.
User Interviews

We initiated our research by conducting in-depth user interviews with a diverse group of DevOps and DevSecOps practitioners. These interviews allowed us to gain invaluable insights into their daily workflows, security concerns, and the specific hurdles they faced in managing Kubernetes security. Users candidly shared their experiences, highlighting the need for a solution that would help them focus their efforts where it mattered most.

Competitive Analysis

To gain a comprehensive view of the cybersecurity landscape, we conducted a competitive analysis, examining similar tools and features in the market. This analysis not only informed our design process but also helped us identify opportunities to innovate and differentiate our 'Attack Path' feature.

Prototyping and Testing

Armed with user insights and a clear understanding of our users' needs, we began the process of prototyping and user testing. We created prototypes of the 'Attack Path' feature and sought feedback from users at various stages of development. Their input was instrumental in refining the feature's design and usability.

Iterative Design

The research phase was iterative, with continuous feedback loops between users and our design and development teams. This iterative approach ensured that the 'Attack Path' feature would align seamlessly with user expectations and needs.

The culmination of this extensive research was the creation of a user-centric 'Attack Path' feature that directly addressed the challenges identified during our research phase. By prioritizing user feedback and insights, we were able to develop a tool that empowers DevOps and DevSecOps users to protect their Kubernetes environments effectively.

Read more about our research journey in our blog post, where we delve deeper into the findings and user stories that shaped the 'Attack Path' feature.


Our approach to bringing the 'Attack Path' feature to life was a well-structured, user-focused process:

  • Wireframing and Conceptualization: We began with wireframing and conceptualizing the feature, outlining the initial user interface and flow.

  • Prototyping and User Testing: Interactive prototypes were created to visualize the user experience. User testing at various stages gathered crucial feedback that informed improvements.

  • Iterative Design: Continuous iterations based on user insights fine-tuned design details and optimized usability.

  • Collaboration: Close collaboration among design, development, security experts, and product management ensured alignment with user needs and technical capabilities.

  • Accessibility and Usability: Accessibility and usability were core considerations throughout the process, ensuring inclusivity.

  • Finalization: After multiple iterations, we arrived at the user-centric, effective 'Attack Path' feature.

Our process reflects our commitment to delivering a valuable tool for the DevOps and DevSecOps community, addressing their specific challenges.


In designing the 'Attack Path' feature, we prioritized user-centricity and clarity. The visual and functional elements were meticulously crafted to ensure that users could effectively understand, interact with, and benefit from the feature:

  • Visual Representation: The core of the 'Attack Path' feature is its visual representation of potential attack paths. We designed this visual element to be intuitive and informative. Each step an attacker could take is represented as a node in the graph, making it easy for users to follow the sequence.

  • Clarity of Information: We recognized the importance of clarity in security visualization. Each node in the graph contains specific details about its role within the attack and the exploitable weaknesses, be it misconfigurations or vulnerabilities. Users can quickly grasp the security context at each step.

  • User-Friendliness: The user interface was designed with simplicity and user-friendliness in mind. Navigating the 'Attack Path' feature is intuitive, allowing users to effortlessly interact with the graph and explore potential threats.

  • Empowering Users: Our design choices aimed to empower users in two crucial ways. First, by providing a clear understanding of the attack paths, users are better equipped to proactively protect their Kubernetes environments. Second, by visualizing potential vulnerabilities and misconfigurations at each step, users can prioritize their efforts effectively.

  • Contextual Information: Users can access context-specific information within the feature, helping them make informed decisions. Whether it's understanding a specific misconfiguration or learning how to remediate a vulnerability, the 'Attack Path' feature provides context at every level.

  • Consistency and Branding: The design maintained consistency with our platform's overall user interface while incorporating branding elements. This ensured that users felt at home with the feature while recognizing it as an integral part of our cybersecurity product.

  • User Feedback Integration: Throughout the design process, user feedback played a central role. It informed design decisions, ensuring that the feature resonated with the needs and expectations of our users.

  • Laptop Responsiveness: Recognizing the importance of flexibility, the 'Attack Path' feature was designed to be responsive, ensuring usability on laptops and various desktop devices.

  • Accessibility: Accessibility was a top priority. The feature was designed to be inclusive, accommodating users with diverse needs, and adhering to best practices in user interface design.

The design of the 'Attack Path' feature represents a careful balance between aesthetics and functionality. It places critical security information at the forefront while prioritizing user experience. Our aim was to create a tool that empowers users to take decisive actions in securing their Kubernetes environments, all within an intuitive and visually engaging interface.

Attack Threats - Single chain.png
Attack Threats - Single chain - cve.png


To measure the success of the 'Attack Path' feature, we established clear criteria. These included the ability to block attack chains effectively and the time saved in addressing vulnerabilities and misconfigurations.


In conclusion, the 'Attack Path' feature has transformed the way users approach cybersecurity in Kubernetes environments. By visualizing potential attack paths, prioritizing vulnerabilities, and enabling users to fortify their defenses, we have empowered our users to stay ahead of malicious actors. The feature ensures that threats are not just managed but neutralized, enhancing Kubernetes security.

Other Projects

Side-by-Side Remediation

Scan history Desktop HD Copy 4.png

Perception Point Scan History 

Scan history Desktop HD Copy.png
bottom of page