better-auth-security-best-practices

Guide Better Auth deployments with cross-cutting security controls.

206|30|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/better-auth/skills --skill better-auth-security-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: better-auth-security-best-practices
Source: https://github.com/better-auth/skills/tree/main/security
Command: npx skills add https://github.com/better-auth/skills --skill better-auth-security-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Better Auth lacks consolidated guidance for cross-cutting security concerns, so this skill provides a cohesive set of best practices that span the entire stack, from rate limiting to auditing, across all plugins.

Core Features & Use Cases

  • Comprehensive guidance on rate limiting, CSRF protection, session security, trusted origins, secret management, OAuth security, IP tracking, and security auditing.
  • Use when deploying or auditing Better Auth implementations to ensure consistent security controls across all components.
  • Real-world scenario: implement a secure authentication flow across multiple services with centralized secret management and monitoring.

Quick Start

Outline a secure deployment plan for a new Better Auth integration that enforces strong secrets, robust session handling, and audit logging.

Frequently Asked Questions about better-auth-security-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I secure a Better Auth deployment with rate limiting and CSRF protection?

Secure Better Auth deployments by enforcing rate limiting, CSRF protection, and trusted origins alongside robust session handling. This skill provides cohesive cross-cutting security controls across all authentication plugins and services.

What is cross-cutting session security and how does it work with OAuth?

Cross-cutting session security centralizes trusted origins, IP tracking, and OAuth security controls across the entire Better Auth stack. It ensures consistent session validation and token management spanning all plugins and services.

Can I use this to audit an existing Better Auth implementation for security gaps?

Yes, you can audit existing Better Auth implementations to identify security gaps. It evaluates rate limiting, CSRF protection, session security, secret management, and OAuth configurations against consolidated best practices.

What's the best way to implement centralized secret management across multiple Better Auth services?

Implement centralized secret management by applying cross-cutting security controls across all Better Auth services. This enforces strong secrets, robust session handling, and audit logging for secure multi-service authentication flows.

Do I need any specific dependencies to configure trusted origins and IP tracking in Better Auth?

No external dependencies are required to configure trusted origins and IP tracking. The skill provides standalone guidance for deployment, configuration, and auditing tasks directly within the Better Auth stack.