Suspicious Login Detection
New device, unusual location, impossible-travel signals and failed attempts change risk; none proves compromise on its own.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
The system treats a valid credential as conclusive or blocks users on a brittle single heuristic.
The important question is not “what is Suspicious Login Detection?” but “which assumption let untrusted data or an over-scoped identity cross authentication event → risk decision and response?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Layer breached-password checks, MFA and attempt limits Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Layer breached-password checks, MFA and attempt limits · Use risk signals to require step-up rather than blindly block | Correlated failures, new device and implausible location/time patterns | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: User accounts and the ability to distinguish normal from abusive authentication.
- Boundary: Authentication event → risk decision and response
- Primary control: Layer breached-password checks, MFA and attempt limits
- Detection signal: Correlated failures, new device and implausible location/time patterns
- Always ask what limits damage when the primary control fails.
Boundary control exercise
This lesson uses the shared boundary-control exercise.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: A credential stuffer or thief using a valid password/session.
- 2The system treats a valid credential as conclusive or blocks users on a brittle single heuristic.
- 3The weak or missing boundary control is crossed: Authentication event → risk decision and response
- 4Impact: Account takeover or user lockout from false positives.
- Account takeover or user lockout from false positives.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Layer breached-password checks, MFA and attempt limits
- • Use risk signals to require step-up rather than blindly block
- • Correlated failures, new device and implausible location/time patterns
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.