Content Security Policy (CSP) Changes

A Content Security Policy (CSP) is a browser security mechanism that helps protect a web application against certain types of attacks, such as cross-site scripting (XSS) and unwanted content injection. It does this by defining which sources the browser is allowed to load content from.

In Practice

CSP works as an explicit allowlist. Resources such as scripts, stylesheets, images, fonts, videos, iFrames, analytics tools, APIs, CDN content and other third-party services must be explicitly permitted.

If a required source is not included in the policy, the browser may block it, even if the application itself is working correctly.

Responsibilities for CSP Changes

Activating or changing a CSP can directly affect customer-specific integrations and business-critical workflows. The correct policy depends on how the customer environment is used, which external services are embedded, and which domains or subdomains need to communicate with the platform.

The responsibility for defining the CSP lies with the customer, as they know which integrations, external services and domains their environment uses.

Project Phase:

CSP setup must be planned, defined and completed during the project phase for all environments.

After Go-live:

If changes are required later, for example because new integrations, domains, external services or upstream infrastructure are added, the customer can submit a imc Service Desk ticket of type Request with clear instructions for Scheer IMC Support.

The Scheer IMC Support will then further coordinate this with the Hosting department of Scheer IMC.

If you as a customer are unsure which sources are required, have doubts about possible side effects, or need an impact assessment, Scheer IMC Support can forward the imc Service Desk ticket to Scheer IMC Consulting. The Consulting department of Scheer IMC can then review the your questions, help clarify which domains or services may need to be included in the CSP, and explain possible functional impacts.

Based on this, the consultant will coordinate this further with Scheer IMC Hosting for implementation.

Typical Content Affected by a CSP

  • Embedded videos (eg. Youtube, Vimeo) and media platforms

  • Analytics (e.g. Google Analytics), tracking or tag-management tools

  • Externally hosted images, fonts and stylesheets

  • Content delivery networks (CDNs)

  • iFrames, APIs, PDF viewers and other third-party integrations

Required Preparation

Before a CSP can be enabled or adjusted safely, the customer should provide clear implementation instructions. If you are unsure about the required sources or expected impact, they can clarify this with Scheer IMC Consulting first.

  • Domains and subdomains: All affected URLs, domains and subdomains that must remain accessible

  • External services: Analytics, video services, PDF viewers, CDNs, fonts, APIs, iFrames and other third-party integrations

  • Business-critical workflows: Pages, functions and integrations that must continue to work after the change

  1. Collect and document all required sources and integrations.

  2. Submit a imc Service Desk ticket of Request type with clear instructions.

  3. Scheer IMC Support coordinates the CSP configuration changes with the Scheer IMC Hosting Team, based on the customer's instructions.

  4. If there are doubts or open questions, the customer asks at ticket submission for advise of Scheer IMC Consulting.

  5. Where possible Scheer IMC Hosting enables the policy first in report-only mode on Stage/UAT environment.

  6. Test your business-critical workflows, review blocked resources and provide any justified exceptions that need to be added.

  7. After successful validation, confirm the production go-live and Scheer IMC Support or Scheer IMC Consulting coordinates the production activation with Hosting department of Scheer IMC.

Testing in report-only mode is strongly recommended because it allows missing sources and required exceptions to be identified without immediately disrupting users.