The useful frame is not "is this secure" but "what does an attacker get if this one thing goes wrong, and how quickly would we know".
This piece walks through how we think about it at Paycux, what we have changed our minds about, and where the sharp edges are.
OTPS are better than static password generation
Consider otps are better than static password generation. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.
Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.
OTPs complement MFA
That brings us to otps complement mfa. Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.
Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.
- Scope credentials to the smallest useful blast radius
- Alert on the abuse you cannot prevent
- Exercise the rotation path before you need it
- Log the decision, not just the outcome
How do OTPs work?
How do OTPs work? is where this gets concrete. Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.
Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.
Time-synchronized OTPs generate based on current time
Time-synchronized OTPs generate based on current time deserves its own treatment. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.
Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.
Rotate on a schedule, not on an incident.
Lockstep-synchronized generate based on prior OTP
That brings us to lockstep-synchronized generate based on prior otp. Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.
Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.
Transmission-based OTP generate on activation
Transmission-based OTP generate on activation is where this gets concrete. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.
Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.
OTP-generation depends on triggers and tokens
OTP-generation depends on triggers and tokens deserves its own treatment. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.
Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.
Where this leaves us
The pattern repeats across every system we have looked at: the hard part is not the mechanism, it is keeping the mechanism honest as the surrounding assumptions change.
If you are working through the same problem and want to compare notes, the docs cover the mechanics and the console shows the behaviour on your own data.
Everything here, already built
Sign-in, enterprise SSO, directory provisioning, roles and an audit trail behind one API. Start with the quickstart and have a working sign-in this afternoon.