Back

Kubernetes / Security · 2023

Attack Path Visualization

A feature that empowers Kubernetes users to proactively visualize and neutralize security threats along the paths attackers can take.

Company
ARMO
Platform
Kubernetes Security Dashboard (Web)
Role
Product Designer
Duration
3 months · Q1 2024
01

Overview

An attack path is the sequence of steps an attacker takes to exploit security weaknesses — from an initial point of entry to the ultimate target. The path is displayed as a node-graph, with each node representing an exploitable step, its role in the attack, and the misconfigurations or vulnerabilities it exposes.

My role As product designer at ARMO, I conceptualized, designed, and contributed to the implementation of the Attack Path feature — working closely with cross-functional teams to keep user-centric design principles at the forefront.

02

Pain points

ARMO users

  • New users are presented with an overwhelming amount of information.
  • Users who want to improve security don't know what action would have the most impact.

General users

  • Hundreds of cyber attacks per minute create massive amounts of intelligence to sift through.
  • Whatever solution a business chooses, it can drown in signal without a way to prioritize.
03

Challenges & goals

  • Help users understand all the ways attackers can exploit their environment.
  • Show what to do right away to break the attack path.
  • Help prioritize issues by security-posture impact.
  • Give users a clearer view of their Kubernetes exposure level.

Jobs to be done

  • When I sign up, I want to see the attack paths so I can fix what matters most first.
  • When I review one, I want full context so I can understand why it's risky.
  • When a new attack path arises, I want to be notified immediately.
04

Research

User interviews We spoke in depth with DevOps and DevSecOps practitioners about their daily workflows and security concerns.

Competitive analysis We examined similar tools to identify opportunities to differentiate the Attack Path feature.

Prototyping & testing Prototypes went in front of users at multiple stages, shaping the final design.

05

Design process — first version

We prioritized clarity and empowerment. Each node makes its role in the attack legible; each edge suggests where to intervene.

Attack path main screen — first draft
Graph node with key assets marked — first draft
06

Final version

The final layout supports branching, provides clear success and empty states, and maps the end-to-end user flow.

Single attack path — graph node with key assets marked
Success state
Empty state
End-to-end user flow
−50%
Time to understand an attack

Clearer visualization.

Adoption

Analysts preferred this method over manual log correlation.

IR efficiency

Teams could take action faster.

07

Summary

The Attack Path graph is a visual way for users to see the route an attacker can take to infiltrate their Kubernetes environment. Readability, size, and contrast are as critical as the data itself.

Next steps

  • Improving existing attack paths and developing new ones.
  • Analyzing usage data to inform further improvements.
  • Establishing a design system for consistent UI.