How a Risk Score Gate Before Password and Email Changes Improves Account Security

A software engineer describes adding a step-up risk scoring system in Go to guard sensitive account mutations like password and email changes, after observing that standard session checks alone failed to prevent account takeovers. The approach involves assigning every security event an immutable correlation ID and feeding behavioral signals — such as failed login velocity and new device detection — into a risk service that returns a score and reasons without acting as an authenticator. Based on the score, the system routes requests through tiered verification challenges, from re-entering a current password at low risk to stronger factors or manual review at high risk. The author warns that thresholds set too tight increase false positives and prompt fatigue, while loose thresholds leave stolen sessions exploitable, so both outcomes are tracked under a defined SLO. The key design principle is placing the risk gate immediately before the state transition, not just at login, and treating the score as a policy-driven decision input rather than proof of identity.