better-auth-security-best-practices

Securing Better Auth involves hardening secrets, enabling rate limiting, validating trusted origins, and configuring CSRF protection. This skill provides ready-to-apply configuration patterns covering sessions, cookies, OAuth, and auditing for full-stack apps.

The best way to configure rate limiting and CSRF protection in Better Auth is by applying per-endpoint protections and origin validation. This skill offers example implementations for environment-driven security settings and extensible hooks.

Better Auth handles OAuth token encryption and session freshness through configurable security settings and environment-driven secrets. This skill guides implementing safe token handling and maintaining secure session states.

Yes, Better Auth security configurations are ideal for SaaS backends and admin panels. This skill helps defend authentication and data access in services relying on Better Auth by applying comprehensive hardening across multiple security domains.

Trusted origins and IP tracking are needed in Better Auth setups to validate request sources and monitor authentication events. This skill provides patterns for implementing origin validation, IP tracking, and comprehensive audit logging.

Default Better Auth cookie security settings may lack strict environment-driven configurations needed for production. This skill addresses limitations by providing quick-start-ready patterns for secure cookies, secret management, and extensible hooks.