← All case studies

Which threats can a security team actually detect?

I designed a way to connect each priority threat to the evidence a responder would need.

A test for a useful alert

A high severity score tells a team little about what it can see. I worked from each threat to a specific question: which event would distinguish suspicious activity from an ordinary change? I used that question to define the data and tests a detection would need.

For example, a change in access rights might be routine. A reviewer needs to know who made it, what changed and whether it was approved. If the approval record is missing, the alert leaves that question open.

Public modelRisk decisions remain traceable into detection

A persistent trace connects the threat record, prioritisation decision, evidence contract and expected detection test.