# Missing Helmet configuration on HTTP headers

## Overview

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

## Description

Helmet can help protect your app from well-known web vulnerabilities by setting HTTP headers appropriately. Failing to configure Helmet for HTTP headers leaves your application exposed to various web attacks.

## Remediation Guidelines

* **Do use** Helmet middleware to secure your app by adding it to your application's middleware.

  ```java
  const helmet = require("helmet");
  app.use(helmet());
  ```

## References

* [**Express Security Best Practices: Use Helmet**](https://expressjs.com/en/advanced/best-practice-security.html#use-helmet)
* [**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/missing-helmet-configuration-on-http-headers.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.