# Usage of default Cookie Configuration

## Overview

* **Rule ID**: `javascript_express_default_cookie_config`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-693

## Description

Using default cookie configurations can expose your application to security risks. This vulnerability occurs when cookies are set with default values, making them predictable and easier for attackers to exploit.

## Remediation Guidelines

* **Do not** rely on default cookie names.
* **Do use** generic, non-descriptive names for session cookies. This makes it harder for attackers to identify and exploit your application's session management mechanism.
* **Do always** specify a `maxAge` or `expires` value to control the cookie's lifetime.

## References

* [**Express Security Best Practices**](https://expressjs.com/en/advanced/best-practice-security.html#use-cookies-securely)
* [**CWE-693: Protection Mechanism Failure**](https://cwe.mitre.org/data/definitions/693.html)

## 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)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sec1.io/user-docs/4-sast/3-javascript/usage-of-default-cookie-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.