diff --git a/src/_data/toc/compliance.yml b/src/_data/toc/compliance.yml index ee7fecc7831..497c8ec5594 100644 --- a/src/_data/toc/compliance.yml +++ b/src/_data/toc/compliance.yml @@ -1,21 +1,21 @@ label: Security and Compliance pages: - - label: Security - versionless: true - url: /security/security-and-compliance.html - children: - - - label: Content Security Policy - versionless: true - url: /security/content-security-policy.html + - label: Security + versionless: true + url: /security/security-and-compliance.html + children: - - label: Industry Compliance + - label: Content Security Policy versionless: true - url: /compliance/industry-compliance.html + url: /security/content-security-policy.html + + - label: Industry Compliance + versionless: true + url: /compliance/industry-compliance.html - - label: Privacy Regulations - - children: + - label: Privacy Regulations + + children: - label: CCPA versionless: true diff --git a/src/security/content-security-policy.md b/src/security/content-security-policy.md index 8e909474ba0..7efa6f4b29f 100644 --- a/src/security/content-security-policy.md +++ b/src/security/content-security-policy.md @@ -19,7 +19,7 @@ It is important to review all CSP errors as they occur and refine the policies u **Restrict mode**: The browser is instructed to enforce all content policies and limit publication to whitelisted resources. -Because CSP is configured from the server, rather than from the Magento Admin, most merchants need the assistance of a system integrator or developer to configure it properly. +Because CSP is configured from the server, rather than from the Magento Admin, most merchants need the assistance of a system integrator or developer to configure it properly. For more information, see [Content Security Policies]({% link guides/v2.3/extension-dev-guide/content-security-policies.md %}) in the Magento _PHP Developer Guide_. ##Reporting