Shield Your ASP.NET MVC Web Applications with Content Security Policy (CSP)
Live Chat Icon For mobile
Live Chat Icon
Popular Categories.NET  (182).NET Core  (28).NET MAUI  (233)Angular  (117)ASP.NET  (49)ASP.NET Core  (81)ASP.NET MVC  (87)Azure  (42)Black Friday Deal  (1)Blazor  (244)BoldSign  (15)DocIO  (24)Essential JS 2  (110)Essential Studio  (201)File Formats  (74)Flutter  (140)JavaScript  (227)Microsoft  (122)PDF  (86)Python  (1)React  (107)Streamlit  (1)Succinctly series  (131)Syncfusion  (993)TypeScript  (33)Uno Platform  (3)UWP  (3)Vue  (46)Webinar  (53)Windows Forms  (59)WinUI  (72)WPF  (165)Xamarin  (159)XlsIO  (38)Other CategoriesBarcode  (5)BI  (29)Bold BI  (8)Bold Reports  (2)Build conference  (11)Business intelligence  (55)Button  (4)C#  (164)Chart  (154)Chart of the week  (62)Cloud  (16)Company  (440)Dashboard  (8)Data Science  (3)Data Validation  (8)DataGrid  (74)Development  (694)Doc  (8)DockingManager  (1)eBook  (99)Enterprise  (22)Entity Framework  (7)Essential Tools  (13)Excel  (43)Extensions  (31)File Manager  (8)Gantt  (23)Gauge  (12)Git  (5)Grid  (31)HTML  (13)Installer  (2)Knockout  (2)Language  (1)LINQPad  (1)Linux  (2)M-Commerce  (1)Metro Studio  (11)Mobile  (530)Mobile MVC  (9)OLAP server  (2)Open source  (1)Orubase  (12)Partners  (21)PDF viewer  (48)Performance  (13)PHP  (2)PivotGrid  (5)Predictive Analytics  (6)Report Server  (3)Reporting  (8)Reporting / Back Office  (9)Rich Text Editor  (12)Road Map  (12)Scheduler  (54)Security  (5)SfDataGrid  (9)Silverlight  (21)Sneak Peek  (32)Solution Services  (4)Spreadsheet  (11)SQL  (15)Stock Chart  (1)Surface  (4)Tablets  (5)Theme  (12)Tips and Tricks  (112)UI  (426)Uncategorized  (68)Unix  (2)User interface  (68)Visual State Manager  (2)Visual Studio  (31)Visual Studio Code  (19)Web  (648)What's new  (354)Windows 8  (19)Windows App  (2)Windows Phone  (15)Windows Phone 7  (9)WinRT  (26)
Shield Your ASP.NET MVC Web Applications with Content Security Policy (CSP)

Shield Your ASP.NET MVC Web Applications with Content Security Policy (CSP)

TL;DR: Fortify your ASP.NET MVC web app against security threats by implementing Content Security Policy (CSP). Mitigate vulnerabilities like XSS and data injection attacks. Learn CSP directives, application methods, and best practices for testing and troubleshooting to secure your app today!

One single vulnerability is all an attacker needs.”

–  Window Snyder

Hackers are everywhere today. The world wide web is also a place for worldwide vulnerabilities. In order to safeguard your application, you need a powerful mechanism. In that case, Content Security Policy (CSP)  is at your service with some excellent features.

In this blog post, we will see how to implement CSP in ASP.NET MVC web applications!


CSP is used to protect your web application. It safeguards it by identifying some types of attacks like cross-site scripting (XSS) and SQL or data injection attacks.

Note: In CSP, some browser features are disabled by default.

If we want to apply CSP to our application, we have to define some CSP content security directives in the desired Content-Security-Policy headers or in the <meta> tags.

When a resource doesn’t match with the defined policy directives, then it won’t be loaded by the browser (scripts and styles from a third-party).

So if a policy restricts images means, then the browser will prevent images from loading when a page contains an <img> tag with a third-party origin in the img src attribute.

All latest versions of browsers Chrome, Edge, Firefox, Opera, and Safari provide support for CSP.

Topics to be covered

Policy directives

The CSP is used to restrict unauthorized third-party content resources. There are many directives available for a source (application). Once Content-Security-Policy headers are included in your application, the browser will reject any other content from sources that are not explicitly included or pre-approved using any of the directives.

You can add the directives in your ASP.NET web application’s HTTP response header GUI in the IIS manager or add the following to your Web.config file.

       <add name="Content-Security-Policy" value="default-src 'self'" />

The following are some of the policy directives:


default-src is used as a fallback if the directives (object-src, img-src, etc.) are not specified. Then, the default-src content policy will be applied for source directives.

  • Use default-src ‘self’ to allow content from the current origin.
  • Use default-src ‘none’ to block everything that’s not added (pre- approved).


<add name="Content-Security-Policy" value="default-src 'self'" />


script-src is used to pre-approve script sources.

  1. Use script-src ‘self’ to allow scripts from the current origin.
  2. You can pre-approve your scripts using script-src ‘*’. It will allow domain scripts in this URL.
  3. script-src ‘* www.example.*’ is used to allow all domain scripts.
  4. Specify unsafe-eval to use eval () methods for creating code from strings.
    <add name="Content-Security-Policy" value="script-src 'self' 'unsafe-inline' 'unsafe-eval' '*' '* https://www.example.*’ " / >
  5. script-src ‘unsafe-inline’ is used to allow inline scripts. In this, you can write <script> </script> directly in the view. Don’t use inline script in your application directly. If you want to use inline script, you should use nonce to avoid security vulnerabilities.
    <script nonce="r@nd0m">
    <add name="Content-Security-Policy" value=" script-src ‘r@nd0m’" />

    Nonce browser support
    The nonce directive is supported from CSP Level 2. It is supported by Chrome and Firefox after the version published in 2015, Safari 10+ or Edge 15+. It’s not supported in all Internet Explorer versions; you need to use the Edge browser for nonce support instead of Internet Explorer.


style-src is used to pre-approve the CSS stylesheet sources.

  1. Use style-src ‘self’ to allow stylesheets from the current origin.
  2. You can pre-approve your styles using style-src ‘*’. It will allow domain styles in this URL.
    <add name="Content-Security-Policy" value=" style-src 'self' '*’ " / >


object-src allows sources for the <object>, <embed>, and <applet> tags. You can specify object-src ‘none’ to prevent loading all URL sources.

<add name="Content-Security-Policy" value="object-src 'none'" / >


img-src is used to restrict image sources. You can pre-approve third-party images in CSP by specifying the domain.

<add name="Content-Security-Policy" value="img-src 'none'" / >


font-src is used to mention sources for loading fonts.

<add name="Content-Security-Policy" value="font-src 'none'" / >


media-src is used to restrict sources from loading sound and video resources.

<add name="Content-Security-Policy" value="media-src 'none'" / >


frame-ancestors is used to restrict URLs that can embed the current source in <iframe>, <object>.

<add name="Content-Security-Policy" value="frame-ancestors 'self'"/ >


upgrade-insecure-requests indicates that the content URL from insecure (HTTP) sources should be acquired securely over HTTPS.

<add name="Content-Security-Policy" value="upgrade-insecure-requests">

Source List Reference

Source ValueExampleDescription
*script-src ‘*’Allows any URL except data: blob: filesystem: schemes
‘none’font-src ‘none’Doesn’t allow loading resources from any source.
‘self’script-src ‘self’Allows loading resources from the same origin.
https:style-src https:Allows loading resources only over HTTPS on any domain.
data:img-src ‘self’ data:Allows loading resources via the data scheme (Base64 encoded images).
*.example.comscript-src ‘*’Allows loading resources from any subdomain under *
https://cdn.comscript-src ‘’Allows loading resources only over HTTPS that matches the given domain.
‘unsafe-inline’script-src ‘unsafe-inline’Allows inline source elements such as style attribute, onclick, or script tag bodies.

<script> </script> and <style> </style>

‘unsafe-eval’script-src ‘unsafe-eval’Allows unsafe dynamic code evaluation such as JavaScript eval ().
‘nonce-‘script-src ‘nonce-r@nd0m’Allows inline script or CSS to execute if the script (<script nonce = “r@nd0m ” >) tag contains a nonce attribute matching the nonce specified in the CSP header.

The nonce should be a secure random string and should not be reused. It is applicable from CSP Level 2.

‘strict-dynamic’script-src ‘strict-dynamic’Allows script to load additional scripts via non-“parser-inserted” script elements (document.createElement(‘script’); is allowed). It is applicable from CSP Level 3.

Apply the policy

Use <system.webServer> tag to apply the CSP.

Place the directives in the name attribute value. Separate directives with a semicolon (;). Refer to the following code example.

            <add name="Content-Security-Policy" value="upgrade-insecure-requests; default-src 'self'; style-src 'self'; script-src 'self'; img-src 'none'; frame-ancestors 'self'" />

Test your policy

After implementing the CSP in your application, you can validate your CSP directives. It helps to confirm that third-party scripts are not inadvertently blocked. If any of the CSP have failed in your application, you can generate a report to rectify them.

For more information, see MDN web docs: Content-Security-Policy-Report-Only and Google CSP evaluator.

Browser supports

CSP supports all latest versions of modern browsers but not Internet Explorer at all. Refer to the following links.


There are many open tools available to scan your application. OWASP is one of the finest applications for finding security vulnerabilities. Once you implement the CSP, you can scan your complete application. This will not affect your application’s performance. You can also scan your production site for:

See more about security vulnerabilities here.


If CSP is not implemented properly in your application, the errors will appear in your browser console. The browser will provide the details about the scripts that are blocked by your webpage. It will also provide the details like:

    • How to change the policy to allow a blocked item.
    • Elements that don’t accept the policy.

Note: CSP is only effective when the client’s browser supports all the included directives. For the latest browser support matrix, check Can I use: Content-Security-Policy.


In this blog, we have seen the steps to implement Content Security Policy (CSP) in your ASP.NET MVC web applications. I hope this blog post was helpful to you.

Syncfusion provides 80+ ASP.NET Core, and ASP.NET MVC UI controls for web application development. We encourage you to take a moment to learn about our products and browse our interactive demos.

For existing customers, the latest version of our products is available for download from the License and Downloads page. If you are not yet a Syncfusion customer, you can try our 30-day free trial to check out our available features. Also, try our samples from this GitHub location.

For questions, you can contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs


Share this post:

Comments (3)

Hi kartik, mvc5 and ejs not render scriptmanager, can you please help me?

Hi Francisco,

I think the problem here might be you missed to include @Html.EJS().ScriptManager() in the view page.

Can you please share more details, so I will try to provide the solution.

Karthik A.

Hi Karthik,

I am trying to invoke an API using ARC/Postman tool residing on a dev server. However, while I request some POST json data it throws me “400-Bad request-Value cannot be null. Parameter name: source”. Firstly I thought some code issue or Database issue, but I observed the following:
400-Bad request
Cache-Control: no-cache
Pragma: no-cache
Content-Type: application/json; charset=utf-8
Expires: -1
Server: Microsoft-IIS/10.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Content-Security-Policy: default-src https: data: ‘unsafe-inline’ ‘unsafe-eval’
Content-Length: 154

Is there any issue with CSP? Because the same API is working fine in localhost and other Dev Servers.

The Response Header from a different Dev-Server (where I get the correct data output):
200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: application/json; charset=utf-8
Expires: -1
Server: Microsoft-IIS/10.0
X-AspNet-Version: 4.0.30319
Content-Length: 154

Comments are closed.

Popular Now

Be the first to get updates

Subscribe RSS feed

Be the first to get updates

Subscribe RSS feed