Security overview
The parts of a login that go wrong quietly are done once, the same way for every app. None of the following is a setting.
| Area | What SeekAuth does | More |
|---|---|---|
| Passwords | Hashed with argon2id (19 MiB, 2 passes). New passwords are checked against known breaches with the Pwned Passwords range API, which sees only the first five characters of a SHA-1 hash. Length rules follow NIST SP 800-63B: 15 to 64 characters, or 8 to 64 where two-step login is required. | Login methods |
| Authorization codes | PKCE with S256 is required on every login. A code works once, for 60 seconds; one presented twice revokes what it issued. | /token |
| Refresh tokens | Opaque, stored as hashes, rotated on every use. One presented twice ends its whole session. | Tokens and sessions |
| Browser tokens | A single-page app’s tokens are bound to a key the browser cannot export (DPoP), so a copied token is no use elsewhere. | DPoP |
| Signing keys | ES256 (and RS256 for clients that ask) per environment, rotated every 90 days with a day of overlap either side. | Keys and secrets |
| Secrets at rest | Secrets that are only compared are stored as hashes; secrets that must be read back are encrypted with AES-256-GCM under the environment’s own key. | Keys and secrets |
| Isolation | Each environment’s rows are kept from every other’s by row-level security in the database itself. | Data and retention |
| Guessing | Login attempts, failures and code emails are limited per environment, per address and per inbox; past a few failures a captcha is asked. | Rate limits |
| Enumeration | The login answers the same for addresses that have an account and addresses that do not. | Bot protection |
| Your team | Everyone who signs in to the dashboard does so with a second factor. | Management API |
| Responses | Nothing is framed (X-Frame-Options: DENY, frame-ancestors 'none'), nosniff, Referrer-Policy: no-referrer, and HSTS on every host. |
|
| Audit | Every login, failed attempt and change of settings is recorded, and the trail cannot be edited. | Data and retention |
What is yours
Section titled “What is yours”- Client secrets, API keys and webhook secrets are shown once. Keep them in your deployment’s secrets; rotate a client secret or webhook secret, or revoke a key, if one leaks.
- Redirect URIs and origins are matched exactly in production. Register only addresses you control.
- The security policy of each environment: two-step login for everyone, a captcha on every sign-up, and which addresses may sign up. See Two-step login and Bot protection.
- Lifetimes: shorter sessions and tokens for sensitive apps. See Lifetimes.
- Your API’s checks: verify the token’s
aud, check permissions per route, and require the DPoP proof of bound tokens. See Protect an API. - Webhook signatures: verify each delivery before acting on it. See Webhooks.