---
title: Web.config security settings
related:
  - https://docs.kentico.com/13/securing-websites/designing-secure-websites/securing-and-protecting-the-system/session-protection.md
  - https://docs.kentico.com/13/securing-websites/developing-secure-websites/cross-site-request-forgery-csrf-xsrf.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

This page lists the most important security-related settings, which can be configured in the web.config file of projects. Please note that most of the settings apply only when working with the administration application.

## Cookies

You should set the following attributes related to cookies:

- **httpOnlyCookies** – adds a _httpOnly_ flag to cookies and makes it impossible to read cookies from the client. This serves as protection against XSS (for example prevents attackers from reading the session ID from cookies or the forms authentication ticket from the authentication cookie).
- **requireSSL** – configures cookies to require an SSL connection, which prevents communication eavesdropping. Note: Only enable the _requireSSL_ attribute if your website is configured to use an encrypted HTTPS connection (see [Configuring SSL](https://docs.kentico.com/13/securing-websites/deploying-websites-to-a-secure-environment/configuring-ssl.md)).

```xml

<system.Web>
    <httpCookies httpOnlyCookies="true" requireSSL="true">
</system.Web>

```

## Error messages and disabling the debug

You should unify handling of all types of errors and exceptions in your application. For more information see [Handling 404 errors](https://docs.kentico.com/13/securing-websites/developing-secure-websites/handling-error-messages-securely/handling-404-errors.md).

Before deploying your website to the live environment, you should also disable debugging in the web.config file, as this information should not be revealed to users.

You can disable **debugging** in your application by including this code in the __ section:

```xml

<system.web>
    <compilation debug="false"/>
</system.web>

```

## Encrypting individual sections of the web.config file

You can encrypt chosen sections of the web.config file, which can prevent attackers from obtaining sensitive information (passwords, connection string, etc.) if they manage to get hold of the file. For more information, see [Encrypting and Decrypting Configuration Sections](https://docs.microsoft.com/en-us/previous-versions/aspnet/zhhddkxy\(v=vs.100\)).

Encoding is supported natively by ASP.NET, so the web application does not need to provide any additional support.

## Authentication

You can set the default authentication mode for the administration interface using the **mode** attribute, which has the following possible values: Windows, Forms, Passport, None

```xml

<authentication mode="Windows">
</authentication>

```

See [authentication Element (ASP.NET Settings Schema)](http://msdn.microsoft.com/en-us/library/532aee0e\(v=vs.100\).aspx) for reference.

### Forms authentication type

When using **Forms** authentication for the Xperience administration interface, you can further configure the authentication using the **forms** element. It is recommended to use session cookies (not to use cookieless authentication) to prevent session hijacking. This can be done by changing the **cookieless** attribute of the form element. You can also set these attributes:

- **cookieless** – defines whether cookies are used and how they are used.
- **timeout** – specifies the number of minutes after which the authentication cookie expires.
- **slidingExpiration** – specifies, whether the expiration time of an authentication cookie should be reset upon each request in a session. If set to true, then the authentication cookie is refreshed with every request, so the cookie does not expire so easily.

```xml

<authentication mode="Forms">
    <forms loginUrl="CMSPages/logon.aspx" name=".ASPXFORMSAUTH" cookieless="UseCookies" requireSSL="true" timeout="15" slidingExpiration="false" />
</authentication>

```

The most secure solution is to set a short timeout interval (e.g., 15 minutes) and disable sliding expiration. This way, if attackers manage to steal the session, they only have a limited time interval to abuse it. However, users would need to submit their credentials and authenticate every time the session expires (set by the timeout attribute).

See [forms Element for authentication (ASP.NET Settings Schema)](http://msdn.microsoft.com/en-us/library/1d3t3c61%28v=vs.100%29.aspx) for reference.

## Session

When developing custom functionality for the administration interface, you should use cookies instead of query strings to pass the session ID. This prevents session stealing, as it is easier to steal the session ID from query strings than cookies. See [Session protection](https://docs.kentico.com/13/securing-websites/designing-secure-websites/securing-and-protecting-the-system/session-protection.md).

To protect the sessions against attacks, you should set the following attributes in the **sessionState** element:

- **mode** – specifies where to store session state values.
- **cookieless** – specifies how cookies are used for a Web application.
- **timeout** – specifies the number of minutes a session can be idle before it is abandoned.

```xml

<sessionState mode="InProc" cookieless="false" timeout="20" />

```

See [sessionState Element (ASP.NET Settings Schema)](http://msdn.microsoft.com/en-us/library/h6bb9cz9\(v=vs.85\).aspx) for reference.

## View state validation

In the Xperience administration application, the view state validation is encoded using the machine key and also a private user key.

You can enable view state validation for the whole administration in the web.config file:

```xml

<configuration>
  <system.web>
    <pages enableViewStateMac="true" />
  </system.web>
</configuration>

```

It is also possible to encrypt the view state to further increase its protection. See [Encrypt ViewState in ASP.NET 2.0](http://msdn.microsoft.com/en-us/library/aa479501.aspx) for more information.