Meta CSP policy

AI-generated summary

The discussion revolves around Meta’s CSP (Content Security Policy) settings. cabana3 asks about CSP policy configurations, prompting awesomerobot to confirm that Meta has CSP enabled and recommends its use for security, referencing MDN documentation. Jagster clarifies that Meta does not have many customizable CSP settings, noting that Discourse is not as flexible as other systems, and critiques CSP as overrated due to complexity and conflicts with services like Google Ads. Falco adds that users can customize CSP by adding domains to the script src policy via site settings and that plugins can extend other CSP directives. Jagster acknowledges this capability and expresses appreciation for the information.

Hi,

Can anyone share meta CSP policy settings


We have CSP enabled on Meta, and recommend everyone keeps it enabled on their own sites! It provides a good layer of protection against exploits. Content Security Policy (CSP) - HTTP | MDN

I’ll translate that :wink: We don’t have too many settings of CSP to share. Only on or off…

It is other systems where system admins can easily adjust CSP. Discourse is not one of those.

(Off topic, but CSP is strongly overrated, because there must use so many settings that actually allow too many things weekening CSP. And in global sites google ads and CSP is pain in the tender places…)

You can add new domains to the script src CSP policy in site settings, which is the main use case for our users.

Plugins can extend any other CSP directives.

Good to know I/we can override default with full scale CSP. Everyday something new :+1: