9.6. Coordinating with browser security countermeasure function¶

Caution

This version is already obsolete. Please check the latest guideline.

Table of contents

Overview
- Security headers supported by default
How to use

9.6.1. Overview ¶

This chapter explains how to coordinate with the security countermeasure function provided by browser.

Main Web browser provides a few security countermeasure functions so that the functions provided by the browser are not affected. Some security countermeasure functions provided by the browser can control the operations by displaying response header of HTTP at the server side.

Spring Security provides a system to enhance security of Web application by offering function to output the security response header.

Note

Security risk

Even if the security response header is displayed, it does not guarantee 100% elimination of security risk. Ultimately, user should consider it as a support function to reduce the security risk.

Note that, the support status of security header varies depending on the browser.

Note

Overwriting HTTP header

HTTP header may be overwritten by the application even though the following settings are done.

9.6.1.1. Security headers supported by default ¶

The following 7 response headers are supported by Spring Security by default.

Cache-Control (Pragma, Expires)
X-Frame-Options
X-Content-Type-Options
X-XSS-Protection
Strict-Transport-Security
Content-Security-Policy(Content-Security-Policy-Report-Only)
Public-Key-Pins(Public-Key-Pins-Report-Only)

Tip

Support status of browser

Some browsers do not support handling these headers. Refer official site of the browser or the following pages.

https://www.owasp.org/index.php/HTTP_Strict_Transport_Security (Strict-Transport-Security)
https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet (X-Frame-Options)
https://www.owasp.org/index.php/List_of_useful_HTTP_headers (X-Content-Type-Options, X-XSS-Protection, Content-Security-Policy, Public-Key-Pins)

9.6.1.1.1. Cache-Control ¶

Cache-Control header indicates a method to cache the contents. Risk of unauthorized users viewing the protected contents can be reduced by disabling caching for the protected contents of the browser..

The following header is output to disable caching the contents.

Output example of response header

Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0

Note

Overwriting Cache-Control header

Cache-Control header is overwritten when Controller class of Spring MVC defines form class of @SessionAttributes or uses Model of @SessionAttributes attribute in the request handler.

Note

Browser compatible with HTTP1.0

Pragma header and Expires header are also output to enable Spring Security support the browser compatible with HTTP1.0 as well.

9.6.1.1.2. X-Frame-Options ¶

X-Frame-Options header indicates whether the contents within the frame (<frame> or <iframe> element) are authorized. Risk of confidential information being stolen by using the malicious practice called Clickjacking can be eliminated by disabling the display of contents within a frame.

The following header is output to deny the display within the frame.

Output example of response header (Default output of Spring Security)

X-Frame-Options: DENY

Note that, options other than the output example can be specified in X-Frame-Options header.

9.6.1.1.3. X-Content-Type-Options ¶

X-Content-Type-Options header indicates a method to determine the contents type. Some browsers ignore the value of Content-Type header and determine the contents by looking at the content details. Risk of attack using cross-site scripting can be reduced when you disable contents view while determining the contents type.

The following header is output in order to disable viewing the content details while determining the type of contents.

Output example of response header

X-Content-Type-Options: nosniff

9.6.1.1.4. X-XSS-Protection ¶

X-XSS-Protection header indicates the method to detect harmful script using XSS filter function of the browser. Risk of attack using cross-site scripting can be reduced by enabling the XSS filter function and detecting harmful script.

Following header is output to enable XSS filter function and detect harmful script.

Output example of response header (Default output of Spring Security)

X-XSS-Protection: 1; mode=block

Further, options other than the output example can be specified in X-XSS-Protection header.

9.6.1.1.5. Strict-Transport-Security ¶

Strict-Transport-Security header indicates that user should access the browser by replacing HTTP with HTTPS when user accesses the browser using HTTPS and then tries to access it using HTTP. Risk of user being directed to malicious sites using malicious technique called as Man-in-the-Middle attack can be reduced by disabling HTTP use after accessing the browser using HTTPS.

Following header is output to disable the use of HTTP after accessing browser using HTTPS.

Output example of response header (Default output of Spring Security)

Strict-Transport-Security: max-age=31536000 ; includeSubDomains

Note

Strict-Transport-Security

Strict-Transport-Security header is output only when the application server is accessed using HTTPS in the default implementation of Spring Security. Note that, Strict-Transport-Security header value can be changed by specifying the option.

9.6.1.1.6. Content-Security-Policy ¶

The Content-Security-Policy header is a header to instruct the content to be allowed to be read by the browser. Since the browser reads only the contents of the whitelist specified in the Content - Security - Policy header, it can reduce the risk of receiving attacks (such as crosssite scripting attacks) executed by loading malicious content.

If you do not send the Content-Security-Policy header, the browser applies the same standard origin policy.

In order to restrict the source of content to only the same origin, the following header is output.

Output example of response header

Content-Security-Policy: default-src 'self'

Note

About sending reports when a policy violation occurs

If a report is to be send at policy violation, specify the reporting URI in the report-uri directive.

In order to block the content if there is a violation of the same origin policy and send the report to /csp_report, output the following header.

Output example of response header

Content-Security-Policy: default-src 'self'; report-uri /csp_report;

In addition, if there is a policy violation, if a report is to be send without blocking content, use the Content-Security-Policy-Report-Only header. By collecting reports using the Content-Security-Policy-Report-Only header and gradually modifying the policy and content,can reduce the risk of not being able to work correctly if the policy is applied to sites that already provide service.

In order to send a report if there is a violation of the same origin policy to /csp_reportwithout blocking the content , output the following header.

Output example of response header

Content-Security-Policy-Report-Only: default-src 'self'; report-uri /csp_report;

9.6.1.1.7. Public-Key-Pins ¶

Public-Key-Pins header presents the public key of the certificate associated with the site, to the browser in order to ensure authenticity of the certificate of the site. Even when the user visits the site again and is directed to a malicious site by using an attack technique called “man-in-the-middle” attack, a mismatch between public key of authentic site certificate retained by browser and public key of certificate presented by malicious site is detected and the access to the site can be blocked.

Following header is output in order to block access to a site when a certificate which does not match the information retained by browser, is detected.

Output example of response header

Public-Key-Pins: max-age=5184000 ; pin-sha256="d6qzRu9zOECb90Uez27xWltNsj0e1Md7GkYYkVoZWmM=" ; pin-sha256="E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g="

Note

Regarding sending a violation report

A report-uri directive is specified similar to Content-Security-Policy in order to send a violation report to browser when the access is blocked.

Further, a Public-Key-Pins-Report-Only header is used instead of Public-Key-Pins header to send a violation report to the browser without blocking the access.

Note

Regarding settings of Public-Key-Pins header

If an error occurs in settings of Public-Key-Pins header, it is likely that user will not be able to access the site for a long period of time. Hence, it is recommended to switch to Public-Key-Pins header after conducting a thorough testing by using Public-Key-Pins-Report-Only header.

9.6.2. How to use ¶

9.6.2.1. Applying security header output function ¶

A method to apply the above mentioned security header output function is decribed.

The security header output function is added from Spring 3.2 and is applied by default except for the following security header .

Content-Security-Policy
Public-Key-Pins

Therefore, a specific definition is not required to enable the security header output function. Further, when the security header output function is not to be applied, it must be disabled explicitly.

Define a bean as given below when the security header output function is to be disabled.

Definition example for spring-security.xml

<sec:http>
    <!-- omitted -->
    <sec:headers disabled="true"/> <!-- Disable by setting true in "disabled" attribute -->
    <!-- omitted -->
</sec:http>

9.6.2.2. Selecting security header ¶

Define a bean as given below for selecting the security header to be output. Here, the example denotes output of all security headers provided by Spring Security, but only required headers should be specified in practice.

Definition example for spring-security.xml

<sec:headers defaults-disabled="true"> <!-- (1) -->
    <sec:cache-control/> <!-- (2) -->
    <sec:frame-options/> <!-- (3) -->
    <sec:content-type-options/> <!-- (4) -->
    <sec:xss-protection/> <!-- (5) -->
    <sec:hsts/> <!-- (6) -->
    <sec:content-security-policy policy-directives="default-src 'self'" /> <!-- (7) -->
    <sec:hpkp report-uri="https://www.example.net/hpkp-report"> <!-- (8) -->
        <sec:pins>
            <sec:pin algorithm="sha256">d6qzRu9zOECb90Uez27xWltNsj0e1Md7GkYYkVoZWmM=</sec:pin>
            <sec:pin algorithm="sha256">E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g=</sec:pin>
        </sec:pins>
    </sec:hpkp>
</sec:headers>

Sr. No.	Description
(1)	First disable the registration of the component which outputs the header applied by default.
(2)	Register the component which outputs Cache-Control(Pragma, Expires) header.
(3)	Register the component which outputs Frame-Options header.
(4)	Register the component which outputs X-Content-Type-Options header.
(5)	Register the component which outputs X-XSS-Protection header.
(6)	Register the component which outputs Strict-Transport-Security header.
(7)	Register the component which outputs Content-Security-Policy header and Content-Security-Policy-Report-Only header.
(8)	Register the component which outputs Public-Key-Pins header and Public-Key-Pins-Report-Only header. When the public key of the certificate presented by the site does not match, a violation report is sent to `https://www.example.net/hpkp-report` without blocking the access. Public key information for the backup is set to prevent inconsistencies of public key when the certificate is updated for the reasons such as compromise in the certificate and expiry of the certificate etc

Note

Regarding output of Public-Key-Pins header

Default setting of Spring Security outputs Public-Key-Pins-Report-Only header rather than Public-Key-Pins header.

Further, in the default setting of Spring Security, Public-Key-Pins header is output only when the application server is accessed using HTTPS.

Further, a method is also provided which disables security headers which are not required.

Definition example for spring-security.xml

<sec:headers>
    <sec:cache-control disabled="true"/> <!-- Disable by setting true in "disabled" attribute -->
</sec:headers>

In the above example, only Cache-Control header is not output.

For details of security header, refer Official reference.

9.6.2.3. Specifying options of security header ¶

Contents which are output by Spring Security by default, can be changed in the following header.

X-Frame-Options
X-XSS-Protection
Strict-Transport-Security
Content-Security-Policy(Content-Security-Policy-Report-Only)
Public-Key-Pins(Public-Key-Pins-Report-Only)

An option [1] can be specified in the attribute of each element by changing the bean definition of Spring Security.

Definition example for spring-security.xml

<sec:frame-options policy="SAMEORIGIN" />

[1]	Refer http://docs.spring.io/spring-security/site/docs/4.1.4.RELEASE/reference/htmlsingle/#nsa-headers for the options which can be specified in each element.

9.6.2.4. Output of custom header ¶

Spring Security can also output the headers which are not provided by default.

A case study wherein following header is output, is explained.

X-WebKit-CSP: default-src 'self'

Define a bean as follows when the header described above is to be output.

Definition example for spring-security.xml

<sec:headers>
    <sec:header name="X-WebKit-CSP" value="default-src 'self'"/>
</sec:headers>

Sr. No.	Description
(1)	Add `<sec:header>` as child element of `<sec:headers>` element and specify the header name in `name` attribute and header value in `value` attribute.

9.6.2.5. Displaying security header for each request pattern ¶

Spring Security can control the output of security header for each request pattern by using RequestMatcher interface system.

For example, when the contents to be protected are stored under the path /secure/ and Cache-Control header is to be output only when the contents to be protected are accessed, define a bean as follows.

Definition example for spring-security.xml

<!-- (1) -->
<bean id="secureCacheControlHeadersWriter"
      class="org.springframework.security.web.header.writers.DelegatingRequestMatcherHeaderWriter">
    <constructor-arg>
        <bean class="org.springframework.security.web.util.matcher.AntPathRequestMatcher">
            <constructor-arg value="/secure/**"/>
        </bean>
    </constructor-arg>
    <constructor-arg>
        <bean class="org.springframework.security.web.header.writers.CacheControlHeadersWriter"/>
    </constructor-arg>
</bean>

<sec:http>
    <!-- omitted -->
    <sec:headers>
        <sec:header ref="secureCacheControlHeadersWriter"/> <!-- (2) -->
    </sec:headers>
    <!-- omitted -->
</sec:http>

Sr. No.	Description
(1)	Specify implementation class of `RequestMatcher` and `HeadersWriter` interface and define a bean for `DelegatingRequestMatcherHeaderWriter` class.
(2)	Add `<sec:header>` as child element of `<sec:headers>` element and specify a bean for `HeaderWriter` defined in (1) in `ref` attribute.

Table Of Contents

Previous topic

Next topic

This Page

9.6. Coordinating with browser security countermeasure function¶

9.6.1. Overview ¶

9.6.1.1. Security headers supported by default ¶

9.6.1.1.1. Cache-Control ¶

9.6.1.1.2. X-Frame-Options ¶

9.6.1.1.3. X-Content-Type-Options ¶

9.6.1.1.4. X-XSS-Protection ¶

9.6.1.1.5. Strict-Transport-Security ¶

9.6.1.1.6. Content-Security-Policy ¶

9.6.1.1.7. Public-Key-Pins ¶

9.6.2. How to use ¶

9.6.2.1. Applying security header output function ¶

9.6.2.2. Selecting security header ¶

9.6.2.3. Specifying options of security header ¶

9.6.2.4. Output of custom header ¶

9.6.2.5. Displaying security header for each request pattern ¶