What problem does it solve? Securing a Better Auth deployment requires correctly configuring many scattered options—secrets, rate limits, CSRF checks, trusted origins, cookies, and OAuth token encryption—and misconfiguring any one of them leaves the authentication layer exposed to brute force, CSRF, or session hijacking attacks. ## Core Features & Use Cases - Rate Limiting & Brute Force Defense: Configure global and per-endpoint rate limits with memory, database, or Redis-backed storage, including stricter rules for sign-in and sign-up endpoints. - Session, Cookie & CSRF Hardening: Set session expiration, encrypted cookie caching (compact, JWT, or JWE), secure cookie attributes, cross-subdomain cookies, and multi-layer CSRF protection with trusted origin validation including wildcard and dynamic patterns. - OAuth & Audit Security: Encrypt stored OAuth tokens with AES-256-GCM, manage state parameters, track client IP addresses, and implement audit logging through database hooks for sessions, users, and accounts. - Use Case: Before deploying a SaaS app to production, apply the complete security configuration example and run through the included checklist to verify secrets, HTTPS, trusted origins, rate limits, and audit logging are all in place. ## Quick Start Ask the AI to generate a production-ready Better Auth configuration with rate limiting, trusted origins, encrypted OAuth tokens, and audit logging for your application.
