Skip to Content
FrontendSecuritySecurity implemented

Security implemented

CSRF Protection

Implementation: Cross-Site Request Forgery protection is enabled on all state-changing API endpoints requests.

Benefits:

  • Prevents unauthorized actions from being performed on behalf of authenticated users
  • Protects state-changing operations (POST, PUT, DELETE, PATCH)

Coverage: All mutation endpoints including form submissions, data updates, and user actions.

Rate Limiting

Implementation: Rate limiting is applied to all API routes without exception.

Benefits:

  • Prevents brute force attacks and credential stuffing
  • Mitigates DoS (Denial of Service) attempts
  • Reduces server load from abusive requests
  • Protects against API abuse and scraping

Coverage: Universal coverage across all API endpoints, including authentication, data fetching, and business logic endpoints.

Centralized Authentication

Architecture: Authentication logic is isolated in a separate, reusable bundle.

Ref : Authorization bundle

Benefits:

  • Single source of truth for authentication logic reduces inconsistencies
  • Easier security auditing with centralized code
  • Consistent security policies across the entire application
  • Simplified maintenance and security updates
  • Reduced attack surface through code reuse validation

Centralized API Functions

Implementation: All generic external API calls are handled through centralized, reusable functions.

Security Benefits:

  • Consistent error handling prevents information leakage
  • Unified request/response validation ensures data integrity
  • Centralized logging for security monitoring
  • Standardized authentication header management
  • Easier security policy enforcement across all external communications

Server-Side Sensitive Data Management

Implementation: All sensitive data processing occurs exclusively on the server side.

Protected Data:

  • API keys and secrets
  • Database credentials
  • User authentication tokens
  • Personal Identifiable Information (PII)

Cookie Security Headers:

{ httpOnly: true, // Prevents XSS access via JavaScript secure: true, // HTTPS-only transmission path: "/", sameSite: "lax" }

Security Benefits:

  • httpOnly: Prevents client-side JavaScript access, mitigating XSS attacks
  • secure: Ensures cookies are only transmitted over HTTPS connections
  • sameSite: “lax”: Provides CSRF protection while maintaining compatibility with legitimate cross-site navigation

Schema-Based Form Validation

Implementation: Form validation using Zod schemas with React Hook Form integration.

Security Architecture:

// Example validation schema const userSchema = z.object({ email: z.string().email("Invalid email format"), password: z.string().min(8, "Password must be at least 8 characters"), });

Security Benefits:

  • Input sanitization at the schema level prevents malicious data injection
  • Type safety ensures data integrity throughout the application
  • Client and server-side validation provides dual-layer protection
  • Consistent validation rules across all forms and API endpoints
  • Prevention of data corruption through strict schema enforcement

Integration with React Hook Form:

  • Real-time validation feedback
  • Optimized re-rendering performance
  • Seamless error handling and user experience
  • Automatic form state management

HTTP Security Headers

Content Security Policy (CSP):

style-src 'self' 'unsafe-inline' img-src 'self' https://icons.phpr.link font-src 'self' frame-ancestors 'none'

Additional Security Headers:

  • Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
  • X-Frame-Options: DENY

Header Security Benefits

Content Security Policy:

  • Prevents XSS attacks by controlling resource loading
  • Restricts inline styles (with controlled exception)
  • Limits image sources to trusted domains
  • Prevents clickjacking with frame-ancestors ‘none’

Strict Transport Security (HSTS):

  • Applies to all subdomains
  • Browser preload eligible for enhanced security

X-Frame-Options:

  • Completely prevents the application from being embedded in frames
  • Additional layer of clickjacking protection

Security Summary

Security Layer
CSRF Protection
Rate Limiting
Centralized Auth
Centralized API
Server-side Data
Secure Cookies
Security Headers
Schema Validation
Last updated on