Helmet for security headers in Node.js

Introduction

Helmet helps keep your web app safe by adding special security headers. These headers tell browsers how to handle your site safely.

When you want to protect your website from common security risks like clickjacking or cross-site scripting.

When you are building a Node.js web server using Express and want easy security improvements.

When you want to control what resources browsers can load on your site.

When you want to add security headers without writing them manually.

When you want to improve your site's security with minimal setup.

Syntax

Node.js

import helmet from 'helmet';
import express from 'express';

const app = express();
app.use(helmet());

Use helmet() as middleware in your Express app to add default security headers.

You can customize Helmet by enabling or disabling specific headers.

Examples

Basic use: adds many security headers with default settings.

Node.js

import helmet from 'helmet';
import express from 'express';

const app = express();
app.use(helmet());

Customize Content Security Policy to allow images only from your site and images.com.

Node.js

app.use(helmet.contentSecurityPolicy({
  directives: {
    defaultSrc: ["'self'"],
    imgSrc: ["'self'", 'images.com']
  }
}));

Remove the 'X-Powered-By' header to hide server info.

Node.js

app.use(helmet.hidePoweredBy());

Sample Program

This simple Express server uses Helmet to add security headers automatically. When you visit the homepage, it shows a greeting message.

Node.js

import express from 'express';
import helmet from 'helmet';

const app = express();

// Use Helmet to add security headers
app.use(helmet());

app.get('/', (req, res) => {
  res.send('Hello, secure world!');
});

app.listen(3000, () => {
  console.log('Server running on http://localhost:3000');
});

Important Notes

Helmet sets many headers by default, but you can customize or disable them as needed.

Always test your site after adding Helmet to ensure no features break due to strict headers.

Helmet helps protect against common attacks but does not replace other security practices.

Summary

Helmet adds security headers easily to your Node.js Express app.

It helps protect your site from common web attacks.

You can customize which headers to use for your needs.

Practice

1. What is the main purpose of using helmet in a Node.js Express application?

easy

A. To serve static files like images and CSS

B. To improve the app's database performance

C. To add security headers that protect the app from common web attacks

D. To handle user authentication and sessions

Solution

1. Step 1: Understand Helmet's role

   Helmet is a middleware that adds HTTP headers to improve security.

2. Step 2: Identify its main function

   It protects against attacks like cross-site scripting by setting headers.

3. Final Answer:

   To add security headers that protect the app from common web attacks -> Option C

4. Quick Check:

   Helmet = Security headers [OK]

Hint: Helmet adds security headers, not database or auth [OK]

Common Mistakes:

• Thinking Helmet manages authentication
• Confusing Helmet with static file serving
• Assuming Helmet improves database speed

2. Which of the following is the correct way to use Helmet in an Express app?

easy

A. import helmet from 'helmet'; app.use(helmet());

B. import helmet from 'helmet'; app.use(helmet);

C. const helmet = require('helmet'); app.use(helmet);

D. const helmet = require('helmet'); app.use(helmet());

Solution

1. Step 1: Check import syntax for modern Node.js

   Using ES modules, import helmet from 'helmet' is correct, but in CommonJS require syntax is used differently.

2. Step 2: Use helmet as middleware function

   Helmet must be called as a function: helmet() inside app.use().

3. Final Answer:

   const helmet = require('helmet'); app.use(helmet()); -> Option D

4. Quick Check:

   Require + call helmet() = correct usage [OK]

Hint: Remember to call helmet() when using app.use [OK]

Common Mistakes:

• Forgetting to call helmet() as a function
• Using require without calling helmet()
• Mixing import and require syntax incorrectly

3. Given this Express app code snippet, what HTTP header will Helmet add by default?

import express from 'express';
import helmet from 'helmet';
const app = express();
app.use(helmet());
app.get('/', (req, res) => res.send('Hello'));
app.listen(3000);

medium

A. Content-Security-Policy

B. X-DNS-Prefetch-Control

C. X-Powered-By

D. Strict-Transport-Security

Solution

1. Step 1: Recall Helmet default headers

   Helmet disables 'X-Powered-By' and adds several security headers by default.

2. Step 2: Identify which header Helmet sets by default

   Among options, 'X-DNS-Prefetch-Control' is one of the default headers Helmet adds.

3. Final Answer:

   X-DNS-Prefetch-Control -> Option B

4. Quick Check:

   Helmet default header = X-DNS-Prefetch-Control [OK]

Hint: Helmet adds X-DNS-Prefetch-Control by default [OK]

Common Mistakes:

• Assuming Content-Security-Policy is always set by default
• Thinking X-Powered-By header is added instead of removed
• Confusing Strict-Transport-Security which needs HTTPS setup

4. What is wrong with this Helmet usage in an Express app?

import helmet from 'helmet';
app.use(helmet);

medium

A. Helmet middleware is not called as a function

B. Helmet is not imported correctly

C. Helmet should be used after route definitions

D. Helmet requires additional configuration to work

Solution

1. Step 1: Check how helmet is used in app.use

   Helmet must be called as a function: helmet() not just helmet.

2. Step 2: Identify the error in middleware usage

   Using app.use(helmet) passes the function itself, not the middleware it returns.

3. Final Answer:

   Helmet middleware is not called as a function -> Option A

4. Quick Check:

   Call helmet() to use middleware [OK]

Hint: Always call helmet() in app.use [OK]

Common Mistakes:

• Passing helmet without parentheses
• Importing helmet incorrectly
• Placing helmet after routes (should be before)

5. You want to disable the contentSecurityPolicy header in Helmet but keep all other default headers. Which code snippet correctly does this?

hard

A. app.use(helmet({ contentSecurityPolicy: false }));

B. app.use(helmet.contentSecurityPolicy(false));

C. app.use(helmet.disable('contentSecurityPolicy'));

D. app.use(helmet({ disable: ['contentSecurityPolicy'] }));

Solution

1. Step 1: Understand Helmet configuration object

   Helmet accepts an options object where you can disable specific headers by setting them to false.

2. Step 2: Identify correct syntax to disable contentSecurityPolicy

   Setting contentSecurityPolicy: false inside helmet() disables only that header.

3. Final Answer:

   app.use(helmet({ contentSecurityPolicy: false })); -> Option A

4. Quick Check:

   Disable header by setting false in options [OK]

Hint: Use helmet({ contentSecurityPolicy: false }) to disable it [OK]

Common Mistakes:

• Trying to call helmet.contentSecurityPolicy as a function
• Using non-existent disable method
• Passing disable array instead of options object