Understand session regeneration improvements

This guide explains improved session-identifier replacement around authentication and security-sensitive state changes. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

What you’ll accomplish

Understand improved session-identifier replacement around authentication and security-sensitive state changes. 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 to review

• Authenticated session identifier

Rules the system enforces

• Session identifiers are regenerated while legitimate session data remains available.
• Prior identifiers must not remain reusable after the protected transition.
• Users must not copy session cookies between accounts or browsers.

How to confirm 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.

Continue with related guidance