Cookies exchanged between the web server and the client, such as session cookies, must have cookie properties set to force the encryption of cookies.

From Web Server Security Requirements Guide

Part of SRG-APP-000439-WSR-000155

Associated with: CCI-002418

SV-70263r2_rule Cookies exchanged between the web server and the client, such as session cookies, must have cookie properties set to force the encryption of cookies.

Vulnerability discussion

Cookies can be sent to a client using TLS/SSL to encrypt the cookies, but TLS/SSL is not used by every hosted application since the data being displayed does not require the encryption of the transmission. To safeguard against cookies, especially session cookies, being sent in plaintext, a cookie can be encrypted before transmission. To force a cookie to be encrypted before transmission, the cookie Secure property can be set.

Check content

Review the web server documentation and deployed configuration to verify that cookies are encrypted before transmission. If the web server is not configured to encrypt cookies, this is a finding.

Fix text

Configure the web server to encrypt cookies before transmission.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer