From this post , it looks like you are defining your content security policy (and, in turn, filling out these headers) directly in your IIS configuration file. An example in a related post
<system.webServer> <httpProtocol> <customHeaders> <add name="Content-Security-Policy" value="default-src 'self';" /> </customHeaders> </httpProtocol> </system.webServer>
demonstrates how to do this; in your configuration file, in the httpProtocol section httpProtocol add an entry to the customHeaders collection containing a name (ie, "Content-Security-Policy" ) and a value that defines the CSP that you want to implement. In the above example, a very simple CSP that allows you to download resources from a local site ( self ).
The second resource you associate lists the various parameters that you can use in your customHeader , and examples of their valid values. It should be remembered that the following parameters should be ; -separated, and the line should end with the final ; .
source share