verify-security

To verify Helmet CSP settings, validate that production configurations prevent unsafe-inline and unsafe-eval usage. This ensures frontend security controls are correctly enforced across the application to minimize attack surface exposure.

Checking Next.js security headers involves verifying the presence of six essential security headers across your application. Use this validation as a pre-deploy check to ensure configurations are correct and maintain compliance before releasing to production.

Site-scoped data isolation restricts data access using a 4-parameter enforceSiteAccess signature and SiteScopeInterceptor patterns. This mechanism ensures proper isolation in production environments by enforcing strict access boundaries between different sites.

PermissionsGuard should run in DENY mode in production to enforce strict access controls and align with audit modes. Enforcing this mode prevents unauthorized state-changing endpoints and minimizes the system's overall attack surface.

Auditing @Public() usage detects improper application on state-changing endpoints to minimize attack surface. This process identifies exposed routes in your production codebase and generates a remediation plan to secure vulnerable configurations.

Yes, you can use security verification for post-change validations to maintain compliance. It validates production security configurations across frontend and backend layers, detecting configuration drift and providing remediation steps after code changes.