Use secure HttpOnly and SameSite cookie defaults

Understand the hardened defaults applied to authentication and session cookies.

What this guide covers

Understand the hardened defaults applied to authentication and session cookies. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Exact step-by-step process

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

Fields, choices and supported possibilities

• Secure
• HttpOnly
• SameSite

Code-backed validations and workflow rules

• Secure limits transport to HTTPS.
• HttpOnly prevents normal browser JavaScript from reading the cookie.
• SameSite restricts unintended cross-site delivery.
• Do not weaken cookie defaults to solve an unrelated integration problem.

Expected result and verification

• 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