Table of Contents

Search

  1. Preface
  2. Introduction
  3. Configuring the Data Director Application
  4. Establishing a Root Node
  5. Defining the Business Entity Model
  6. Configuring Business Entity Properties
  7. Configuring Reference Entity Properties
  8. Transforming Business Entities and Views
  9. Configuring Hierarchy and Network Relationships
  10. Creating Match Rule Sets
  11. Configuring Search
  12. Configuring Tasks
  13. Configuring Security and Data Filters for Business Entities
  14. Configuring the Content Security Policy
  15. Integrating Data as a Service
  16. Configuring External Calls
  17. Designing the Data Director User Interface
  18. Localizing Data Director
  19. Appendix A: Provisioning Tool Frequently Asked Questions

Content Security Policy Defaults

Content Security Policy Defaults

When you install Multidomain MDM, default rules are applied that allow content required for Multidomain MDM to run.
Multidomain MDM has the following default rules:
default-src 'self'; script-src 'self', 'unsafe-eval'; style-src 'self', 'unsafe-inline', 'unsafe-eval', "use.fontawesome.com", "maxcdn.bootstrapcdn.com", "fonts.googleapis.com", "netdna.bootstrapcdn.com"; font-src 'self' data:, "fonts.gstatic.com", "use.fontawesome.com", "maxcdn.bootstrapcdn.com", "fonts.googleapis.com", "netdna.bootstrapcdn.com"; img-src 'self' data:; frame-src 'self' blob:;
The default rules applied during installation can't be changed or deleted. Any additional rules applied during upgrade or after installation can be modified or deleted.
When you upgrade, the upgrade process checks for custom user interface components in the Operational Reference Store (ORS) databases. The following rules are added if any custom user interface components exist:
script-src *; font-src *; style-src *; frame-src *; image-src *; default-src *;
Customize these rules after upgrading Multidomain MDM to secure your system and prevent code injection attacks.
To optimize the content security policy for your organization, configure rules to allow only the approved origins for required content.

0 COMMENTS

We’d like to hear from you!