Authentication security

This page describes the authentication controls for ManyRows accounts: credential storage, sign-in and sessions. Project roles and field-group restrictions govern access to product records separately. Seeteam access and sharing for those controls.

Passwords & credentials

We protect stored passwords with strong hashing and verify credentials with safeguards against account enumeration.

  • Argon2id hashing, memory-hard and GPU-resistant, tuned to m=64 MiB, t=3, p=1. Cost parameters are recorded with each hash so we can strengthen them over time without invalidating existing passwords.
  • Password strength checks, a zxcvbn-style estimator assesses how easily a password could be guessed, including matches to the account’s email and name, alongside minimum length and strength requirements.
  • Constant-time verification, comparisons run in constant time, and a dummy hash is evaluated for unknown accounts to reduce timing differences that could reveal registered emails.
  • Password reuse controls, our authentication infrastructure supports blocking reuse of recent passwords where required by the account policy.
  • No forced rotation, we don’t expire good passwords on a timer, a practice that encourages weaker, predictable choices.

Multi-factor & strong auth

Our sign-in infrastructure supports phishing-resistant credentials and additional verification factors. Recovery codes and email sign-in secrets are stored as hashes and accepted only once.

  • Passkeys / WebAuthn (FIDO2), phishing-resistant credentials, including discoverable credentials for passwordless sign-in.
  • TOTP authenticator apps (RFC 6238), standard 30-second codes with replay protection that tracks the consumed time-step.
  • One-time recovery codes, stored only as keyed (HMAC) hashes bound to the account and invalidated on use.
  • Magic links & email OTP, short-lived, hashed at rest, single-use, and attempt-capped, with a resend cooldown to prevent inbox flooding.

Sessions & tokens

Signed access tokens and server-side session records work together to verify requests and revoke access when needed.

  • ES256 access tokens, signed with ECDSA P‑256 and short-lived (15 minutes by default). Services verify them against published public keys without sharing signing secrets.
  • Rotating refresh tokens, stored only as SHA‑256 hashes and rotated on every use. Replaying a rotated token revokes the entire session.
  • Device binding support through DPoP (RFC 9449), which can bind a refresh token to a device key to prevent its use without proof of possession of that key.
  • Signing key rotation, an overlap window keeps current and previous public keys available so sessions remain valid during rotation.
  • Protected browser sessions, HttpOnly,Secure, and SameSite cookies, idle and absolute expiry, concurrent-session controls, and server-side revocation.

Encryption & key management

Sensitive authentication secrets are encrypted at rest, with protections against tampering and support for key rotation.

  • AES-GCM encryption, signing keys, OAuth client secrets, SMTP credentials, TOTP seeds, and webhook secrets are encrypted rather than stored in plaintext.
  • Record-bound encryption, additional authenticated data (AAD) binds ciphertext to its database record to prevent encrypted values from being swapped between records.
  • Online key rotation, versioned encryption envelopes and support for previous keys preserve access to retained secrets during a configured key rotation.

Attack resistance

Our authentication infrastructure includes layered defenses against credential stuffing, account enumeration, CSRF, clickjacking, SSRF, and injection attacks.

  • Layered rate limiting, per-IP and per-account limits on authentication endpoints, plus daily per-address caps on outbound emails.
  • Progressive lockout, repeated failures trigger escalating lockout periods within a rolling window.
  • Enumeration resistance, generic responses on login, reset, and registration flows, with rate-limit attempts counted even for unknown emails.
  • CSRF protection, SameSite cookies, OAuth state, OIDC nonce, and PKCE on the relevant flows.
  • Secure headers, HSTS, frame restrictions against clickjacking, X-Content-Type-Options: nosniff, and a strict Referrer-Policy on authentication endpoints.
  • SSRF guards, outbound webhook and identity-provider requests require HTTPS and reject private, loopback, and link-local destinations, with checks repeated at connection time to defend against DNS rebinding.
  • Injection defenses, parameterized database queries and support for additional anti-abuse challenges on registration and password reset.
  • Trusted proxy controls, forwarded client addresses are accepted only from trusted proxies to protect rate limiting and audit records from spoofed headers.

OAuth, OIDC & SSO

We use standard OAuth and OpenID Connect flows for supported social and corporate sign-in methods, with checks that protect the handoff between ManyRows and the identity provider.

  • PKCE, state & nonce, authorization-code flows use PKCE (S256), a state parameter for CSRF protection, and a nonce for replay protection.
  • Verified ID tokens, signatures, issuers, and audiences are checked, and provider endpoints must use HTTPS.
  • Exact redirect matching, redirect targets must match an allowlist exactly, rather than by substring or prefix.
  • Identity provider support, our sign-in infrastructure supports Google, Apple, Microsoft, GitHub, Kakao, Naver, and other OAuth2 or OIDC providers for corporate SSO. Available sign-in methods depend on the configured service. Custom SSO scope and availability are agreed separately with your team.
  • Consent captured at signup, including social signup, with append-only records of the version, timestamp, and IP.

Isolation & access control

Authentication data and permissions are scoped to keep accounts and organizations separate and restrict access to authorized actions.

  • Scoped data access, authentication queries enforce workspace, project, application, and user-pool boundaries.
  • Separate authentication settings, OAuth credentials, sign-in methods, allowed origins, and redirect allowlists are scoped to each application in our infrastructure.
  • Identity boundaries, user pools control where credentials, password resets, and shared sign-in apply.
  • Roles & permissions, role-based access controls and scoped permissions restrict authorized operations. OIDC scopes limit identity information included in tokens and responses.
  • Scoped authentication API keys, internal server-to-server keys carry limited permissions, are rate-limited, and are shown only once when created.
  • Restricted administration, our authentication infrastructure supports reserving initial administrator access for a designated account.

Audit & observability

We record security events in structured logs to support monitoring, investigation, and incident response.

  • Authentication event logs, sign-in successes and failures, logout, password and MFA changes, session revocation, administrator actions, and organization membership changes.
  • Investigation details, records capture the actor, method, outcome, IP, user-agent, and request ID.
  • Retention controls, authentication logs have configurable retention and automatic cleanup.
  • Service monitoring, health checks and protected metrics help our team monitor authentication infrastructure.

Hosting & service providers

Our application services, including authentication, and managed PostgreSQL database are hosted on Render in Oregon, United States. ManyRows manages application permissions, session configuration and service credentials. Render publishes information about its ownplatform security practicesand platform certifications.

Amazon Web Services stores uploaded images and files. Resend delivers transactional emails such as login codes, password resets and invitations. Cloudflare provides DNS, proxy and content delivery services, traffic security, and Turnstile checks where enabled.

Our provider disclosures andprocessing locations explain these services and international processing. Thedata processing agreement sets out our obligations when processing customer content.

Privacy & data protection

Our authentication infrastructure includes account data export, deletion, consent records, and safeguards for personal information.

  • Account data export, support for exporting profile details, linked identities, sessions, passkeys, organization memberships, and recent authentication history.
  • Verified account deletion, deletion requires confirmation by password or emailed code, removes associated authentication data, and scrubs residual personal information from authentication logs and webhook payloads.
  • Consent records, append-only records preserve what was agreed to and when.
  • Data minimization, authentication logs anonymize IP addresses in standard output and mask emails in operational logs by default.
  • Protected email changes, confirmation from both the old and new email address helps prevent a hijacked session from silently taking over an account.

Security by default

We maintain these protections as part of the ManyRows service. Secure credential storage, session handling, and authentication safeguards are built into our infrastructure.

  • Established standards, Argon2id, ES256, AES-GCM, WebAuthn, OAuth, and OIDC provide recognizable, auditable building blocks.
  • Operational hardening, our team manages TLS termination, cookie scope, trusted proxies, and key rotation for the authentication service.
Found a security issue? Responsible disclosures are welcome.Get in touch and we’ll work with you on a fix and timeline.