> For the complete documentation index, see [llms.txt](https://docs.sec1.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sec1.io/user-docs/4-sast/3-javascript/missing-secure-option-in-cookie-configuration.md).

# Missing Secure option in Cookie Configuration

## Overview

* **Rule ID**: `javascript_express_insecure_cookie`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-614

## Description

When a cookie lacks the Secure attribute, it can be transmitted over an unencrypted connection, making it vulnerable to interception by unauthorized parties. Enabling the Secure attribute ensures that cookies are only sent over HTTPS, enhancing the security of data in transit.

## Remediation Guidelines

* **Do** set the `secure` attribute of cookies to `true`. This action mandates that cookies are sent only over HTTPS, safeguarding them from potential eavesdropping.

  ```javascript
  cookie({ secure: true });
  ```

## References

* [**Express Security Best Practices**](https://expressjs.com/en/advanced/best-practice-security.html#use-cookies-securely)
* [**CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute**](https://cwe.mitre.org/data/definitions/614.html)
* [**OWASP Top 10: A05:2021 - Security Misconfiguration**](https://owasp.org/Top10/A05_2021-Security_Misconfiguration/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)