How I turned a table-driven security console into a network-first experience — helping engineers move from seeing a risk to understanding, validating, and acting on it.
As networks moved to hybrid cloud, the perimeter was no longer a sufficient security boundary. Security teams had more traffic data than ever — but turning that data into confident policy remained largely manual.
Customer interviews and research revealed four distinct but entangled problems. Each made the others worse.
Security teams didn't lack information. They lacked a system that could turn information into a confident decision.
The old product had the right data — assets, connections, policies, logs. What it didn't have was a way to move from data → understanding → action.
That wasn't a UI problem.
It was a paradigm problem.
I challenged the assumption that Xshield needed to be another security dashboard. I made the case to the CPO and CEO that the network itself should become the interface — then validated the direction with a working prototype and usability testing before production development.
Every transition was technically possible. The relationship between them existed only in the engineer's head.
Surface what requires attention. Threat state should be understandable before an engineer reads the underlying data.
Put the action next to the context. If an engineer sees suspicious traffic, they shouldn't have to leave that view to create a policy.
Security actions have consequences. Engineers should understand a policy's expected impact before it goes live.
A spatial, relationship-first view of the network — bringing asset groups, traffic flows and threat signals together on one continuous surface.
Impact figures are directional signals drawn from customer interviews and usability research, not broad causal claims.
