AttackIQ · Cybersecurity
Continuous Security Validation Platform
As Director of Product Design and UX at AttackIQ I led the cloud and enterprise subscription product strategy for a platform that validates security controls continuously rather than once a year.
- Role
- Director of Product Design, User Experience (UX), SaaS, Cloud / Enterprise Solutions
- Timeline
- Aug 2017 to Aug 2020, 3 yrs 1 mo, San Diego
- Team
- Design team I built and led, plus product and engineering

The problem
Purple-team validation was expert work: powerful, manual and impossible to scale. The insight lived in the heads of a few operators and in spreadsheets nobody else could read.
The platform had to serve two very different audiences, the operator running emulations and the executive who needs a defensible answer to 'are we covered?'
- , MITRE ATT&CK as a fixed, dense conceptual model users must learn
- , Enterprise buyers with existing SOC tooling and workflows
- , Design team had to be recruited and stood up while shipping
- , Results must be trustworthy enough to present to a board
Process
01
Two readings of one result
Every test result renders twice: technique-level detail for the operator, coverage posture for leadership. Same data, two levels of abstraction, no separate reporting product.

02
Tiered testing experiences
Guided scenarios for teams new to threat-informed defense, full custom emulation for mature teams, one platform, several depths of entry.

03
Design system and team build-out
Established the design language and a component library so a growing team could ship consistently across web and enterprise surfaces.

04
Automate the repetition
Scheduled, continuous validation replaced one-off manual exercises, the core product promise expressed as a workflow.

05
Top Gun Award, 2018
AttackIQ recognized this product design work with its 2018 Top Gun Award.

Screens
Every screen and design artifact from this engagement.












Outcome
- Purple team
- workflow automated end to end
- Top Gun
- award-recognized product work
- 0 → team
- design function built from scratch
What I'd do differently
I would have invested in an ATT&CK onboarding layer sooner. Sophisticated users loved the depth immediately; newer teams needed a bridge we built later than we should have.