Use central security audit logging

Use the consolidated event trail for security-sensitive activity.

What this guide covers

Use the consolidated event trail for security-sensitive activity. 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

• Actor/token identity
• Event type
• Timestamp
• Source/context
• Outcome

Code-backed validations and workflow rules

• Correlate actor/token, event type, time, source, context and outcome.
• Do not record plaintext passwords, reusable tokens or unnecessary sensitive content.
• Preserve events according to the authorised retention and investigation process.

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