Understand restricted CSRF exclusions

This guide explains why only explicitly required endpoints may bypass CSRF checks.

What this guide helps you do

Understand why only explicitly required endpoints may bypass CSRF checks. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Follow these steps

1. Use the supported Britixo CRM release or workflow that produces this security control.
2. Check the expected protection through an authorised test.
3. Record the result in the deployment or security audit evidence.

Fields and options

• Protected form routes
• Explicit approved exclusions

Rules and limits

• Normal browser forms retain CSRF protection.
• Exclusions are restricted to essential approved endpoints.
• Public/API endpoints still require their own token, signature or authentication controls.
• A failing integration is not sufficient reason for a wildcard exclusion.

Check it worked

• The protection is active without weakening another security control.

Security, audit and troubleshooting checks

• Use the exact authorised account, role and record before saving or sending.
• Verify the saved status and downstream record; a browser success message alone is not sufficient evidence.
• Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets.
• Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules.

Related guides