Review security headers and CSP report-only mode

Review response security headers and the initial Content Security Policy reporting mode.

What this guide covers

Review response security headers and the initial Content Security Policy reporting mode. 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

• Security headers
• Content-Security-Policy-Report-Only
• Report destination

Code-backed validations and workflow rules

• Inspect representative staff, client and public responses.
• Review CSP reports for legitimate resources that would be affected.
• Remediate dependencies before moving from report-only to enforcement.
• Do not silence reports with broad wildcard policies.

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