06 / PRACTICE BRIEF

Five seconds to know.
One click to act safely.

A cybersecurity hiring brief, shared with me as a practice exercise. I set myself a three-day timebox to design an investigation side panel and a presentation that could stand on its own.

Practice brief · Desktop side panelCompany anonymizedAI-assisted, human-decided
Suspicious data downloadDemo · Alert #1042 · Sarah, Finance
95AI assessment

Likely data exfiltration.
Account takeover not ruled out.

What argues against it

Folder access matches her role. MFA was approved on a known iPhone. No previous alerts in 12 months.

Volume · 38 points

~180 MB a day → 50.2 GB in 38 minutes

Device · 24 points

Two known devices → unmanaged laptop

A five-minute response scenario, designed for a five-second first read.

Design targets, not measured results. The people, devices and events are demo data.

01 / THE BRIEF

What I was asked to design.

A security operations center analyst receives a high-risk alert. My task was the panel used to investigate it, within an existing dashboard.

THE USER

Daniel, SOC analyst.

Many tools open, many alerts, little time. He needs a quick first read before deciding where to investigate.

THE ALERT

Risk 95.

A Finance employee downloaded 50 GB of customer data at 2 AM, from an unrecognized device.

THE ASK

Four challenges, one flow.

Hierarchy, explainable AI, actions with guardrails, and drill-down. One complete flow that reviewers could follow without me.

The brief asked forIn other wordsWhere it lives
Hierarchy and AI summaryWho, what, how severe, and what next.01 · The first read
Explainable AIShow what makes this suspicious.02 · Why 95
Actions with guardrailsEasy to reach, hard to get wrong.05 · Block · 06 · Suspend
Drill-downExplore files and devices without losing context.03 · Files · 04 · Device
A complete flowFrom opening the alert to containment and escalation.01 → 07
One panel. One decision.
02 / BEFORE I DESIGN

Four criteria before any screen.

I translated the brief into criteria I could check each design against.

01

5-second read

Who, what, how severe and what to do, before scrolling.

02

Trust

Each factor next to its baseline, with counter-evidence visible.

03

Safe action

Narrow and reversible actions are quick. Disruptive actions show their impact first.

04

Keep context

Drill-down preserves the alert, score and next step.

Behavior before pixels. First what Daniel needs to understand, then how it looks.

03 / WHAT RESEARCH CHANGED

Three insights shaped the panel.

AI-assisted desk research across industry reports, studies and product references informed these choices. This was not a user-interview study.

01

The score is a claim. The baseline is evidence.

A 95 is hard to assess in isolation. Comparing each factor with normal activity makes the reasoning inspectable.

02

It may not be her at all.

An unfamiliar device keeps account takeover on the table. The AI should weigh explanations, not judge a person.

03

Friction should match the impact.

Identical confirmations encourage automatic clicks. The action’s scope and consequences need to be clear.

False positives were the top detection challenge for 73% of respondents in the 2025 SANS Detection & Response Survey, according to Stamus Networks’ survey summary ↗.

Product references: CrowdStrike · Microsoft · SentinelOne · Varonis · Wiz · Island · Wonderful

04 / THE EVIDENCE MODEL

Why 95, factor by factor.

A demo score breakdown makes the hierarchy concrete: the strongest signals first, each next to a baseline.

Volume~180 MB a day50.2 GB in 38 min38 pts
Device2 known devicesUnmanaged Windows laptop24 pts
Time08:00–18:3002:03–02:4414 pts
Data typeReports and ledgers96% customer PII11 pts
NetworkOffice or homeCommercial VPN, Frankfurt8 pts

Illustrative contributions total 95 points, not percentages. Her team’s highest day in 90 days was 2.1 GB, about 24 times less than this event.

LAYER 0

The first read

Title, score, verdict, next step and counter-evidence.

LAYER 1

The case

Factors, baselines, hypotheses and response plan.

LAYER 2

The proof

Files, device details and logs beside the panel.

05 / FROM SKETCH TO SCREEN

Three options each. One direction chosen.

I compared low-fidelity options against the four criteria. Here are the selected structures and the final screens they informed.

CHOSEN WIREFRAME
Selected low-fidelity structure: Verdict first
FINAL SCREEN
Designed investigation panel: Verdict first

Verdict first

The verdict and next step come first. Entity-first answered who before what; score tiles gave a number without an explanation.

CHOSEN WIREFRAME
Selected low-fidelity structure: Factors vs. baseline
FINAL SCREEN
Designed investigation panel: Factors vs. baseline

Factors vs. baseline

Each claim sits next to a baseline, with counter-evidence visible too. A score followed by a paragraph would still hide the reasoning.

CHOSEN WIREFRAME
Selected low-fidelity structure: A response plan
FINAL SCREEN
Designed investigation panel: A response plan

A response plan

The sequence explains what to do next, and friction grows with impact. Equal buttons would flatten those differences; automatic containment would remove the human decision.

CHOSEN WIREFRAME
Selected low-fidelity structure: Detail beside the panel
FINAL SCREEN
Designed investigation panel: Detail beside the panel

Detail beside the panel

The verdict and response plan stay visible during drill-down. Tabs would hide the actions; a separate page would lose the alert.

I rejected the first visual draft as too generic. The structure stayed; a dark verdict card, stronger type hierarchy and purposeful color made the priorities clearer.

06 / THE FLOW

One alert, one complete response.

Seven screens tell a simulated night from 02:51 to 02:56. The timestamps illustrate the intended flow, not a tested completion time.

01

Answer first.

One dark card holds the verdict, score and next step. Counter-evidence sits just below to help the analyst question the AI’s conclusion.

02

Go deeper, keep the verdict.

Files and device details open beside the panel, preserving the alert and response plan.

03

Friction matches the impact.

Block has a short undo window. Suspend requires reviewing the impact and entering a reason. Escalation remains a human decision.

07 / UP CLOSE

Evidence that sharpens the next question.

The unknown laptop sits beside her managed devices. A known iPhone approved the sign-in, but that alone cannot establish who used the laptop. The design keeps uncertainty visible while supporting a narrow first action.

  1. No security agent and no IT record are explicit.
  2. Known devices provide a comparison.
  3. Blocking updates the same device state throughout the panel.
Device investigation: unrecognized Windows laptop, security agent status, known managed devices and block action.
08 / ASSUMPTIONS

What I assumed, and how I’d check.

These dependencies would need validation with the product and security teams before implementation.

Model explainability

Confirm which factors and baselines the engine can reliably expose.

Permissions and policy

Check containment permissions, escalation ownership and employee-impact decisions.

Reversibility

Verify which actions can be undone and what a 30-second window actually guarantees.

What I’d measure

  1. Time from opening an alert to an informed decision.
  2. How often a closed alert is reopened.
  3. How often Undo is used, and why.
09 / AI AND OWNERSHIP

AI sped it up. I owned the decisions.

Where AI helped. Research synthesis, first drafts of the framing and hypotheses, evidence-model options, edge cases, and screen construction in Figma.

What I owned. Reviewing those drafts, choosing the four design directions, setting the visual direction, rejecting the generic first pass, and approving the final screens.

What I’d explore next. Pseudonymized triage until escalation, and a second flow for closing the alert as legitimate when IT confirms the device.