Lab
In auditRisk-based MFA and SOC triage
A research thread on using risk signals to prioritise authentication challenges and security-operations triage.
Source audit completed 2026-11-18
- Capabilities
- Security analytics · Risk scoring · SOC operations
- Evidence
- confirmed
- Disclosure
- general
Status
Source audit completed (18 November 2026). The repository was reviewed for committed credentials, client data and licence compliance. Committed credential artefacts and runtime data were removed from every revision of the repository history, CI gates pass on all active branches, and the source is private by design. Any credential that predated the audit is treated as compromised and is being rotated in the issuing services.
The portfolio artefact for this thread will be a deployed demo rather than a code link: the value is showing the workflow running, not opening the repository.
Working question
Security teams do not suffer from a lack of signals. They suffer from too many signals arriving without a defensible order. The question behind this thread is whether the same risk evidence can do two jobs: decide when to ask for a stronger authentication challenge, and explain why one security alert should be triaged before another.
The interesting part is not the scoring model. It is the authority attached to the score. A risk signal that cannot change a decision is a dashboard, not a control.
Boundaries
The work does not use client data and makes no production claims. With the source audit complete, the next steps are deploying a demo environment under the same evidence discipline and documenting the threat model.