CSRF protection in Express - Performance & Optimization

Performance: CSRF protection

MEDIUM IMPACT

CSRF protection affects the server response time and client-side interaction by adding security tokens to requests, which can slightly increase payload size and processing.

Protecting forms from CSRF attacks in an Express app

Express

import csurf from 'csurf';
const csrfProtection = csurf({ cookie: true });

app.get('/form', csrfProtection, (req, res) => {
  res.render('form', { csrfToken: req.csrfToken() });
});

app.post('/submit', csrfProtection, (req, res) => {
  processForm(req.body);
  res.send('Form submitted');
});

Validates CSRF tokens on requests, preventing unauthorized actions while adding minimal processing and token size overhead.

📈 Performance GainAdds small token (~100 bytes) and one token validation per request; triggers negligible processing delay (~1-3ms).

Protecting forms from CSRF attacks in an Express app

Express

app.post('/submit', (req, res) => {
  // No CSRF token validation
  processForm(req.body);
  res.send('Form submitted');
});

No CSRF protection means the app is vulnerable to malicious cross-site requests, risking user data and actions.

📉 Performance CostNo direct performance cost but high security risk leading to potential user trust loss.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No CSRF Protection	No extra DOM nodes	0	0	[X] Bad - insecure, no protection
CSRF Token in Form (cookie-based)	Adds hidden input for token	0	Minimal	[OK] Good - secure with minimal overhead

Rendering Pipeline

CSRF protection adds token generation and validation steps on the server before sending or accepting requests, slightly increasing server processing time but not affecting browser rendering stages directly.

→Server Processing

→Network Transfer

⚠️ BottleneckServer Processing due to token generation and validation logic

Core Web Vital Affected

INP

CSRF protection affects the server response time and client-side interaction by adding security tokens to requests, which can slightly increase payload size and processing.

Optimization Tips

1CSRF tokens add minimal server processing delay (~1-3ms) per request.

2Use cookie-based tokens to reduce payload size and simplify validation.

3CSRF protection mainly affects interaction responsiveness (INP), not loading speed (LCP).

Performance Quiz - 3 Questions

How does adding CSRF protection typically affect page load speed?

A Adds large payloads that slow down network transfer significantly

B Blocks browser rendering until token is verified

C Slightly increases server response time due to token generation and validation

D Triggers multiple reflows on the client side

DevTools: Network

How to check: Open DevTools > Network tab, submit a form and inspect the request payload and response headers for CSRF token presence.

What to look for: Look for a CSRF token in request headers or form data and verify no large payload increase; check response times for minimal delay.

Practice

1. What is the main purpose of CSRF protection in an Express app?

easy

A. To prevent unauthorized commands from being sent from other websites

B. To speed up the server response time

C. To encrypt user passwords

D. To log user activity on the server

Solution

1. Step 1: Understand CSRF meaning

   CSRF stands for Cross-Site Request Forgery, which tricks users into submitting unwanted actions.

2. Step 2: Identify CSRF protection goal

   Protection stops other sites from sending commands on behalf of a user without permission.

3. Final Answer:

   To prevent unauthorized commands from being sent from other websites -> Option A

4. Quick Check:

   CSRF protection = prevent unauthorized commands [OK]

Hint: CSRF stops fake requests from other sites [OK]

Common Mistakes:

• Confusing CSRF with password encryption
• Thinking it speeds up server
• Believing it logs user activity

2. Which of the following is the correct way to add CSRF protection middleware in Express using the csurf package?

easy

A. app.use(csurf({ cookie: true }))

B. app.use(csrf())

C. app.use(csrfProtection())

D. app.use(csrf({ session: false }))

Solution

1. Step 1: Recall csurf usage

   The csurf middleware is used as csurf({ cookie: true }) to enable cookie-based CSRF tokens.

2. Step 2: Check options correctness

   Options B, C, and D use wrong function names or invalid options.

3. Final Answer:

   app.use(csurf({ cookie: true })) -> Option A

4. Quick Check:

   Correct csurf syntax = app.use(csurf({ cookie: true })) [OK]

Hint: Use csurf with correct function and options [OK]

Common Mistakes:

• Using wrong function name like csrf()
• Missing the cookie option
• Passing invalid options

3. Given this Express route using csurf middleware, what will happen if the CSRF token is missing or invalid?

app.post('/submit', csurf({ cookie: true }), (req, res) => {
  res.send('Form submitted');
});

medium

A. The server redirects to the home page

B. The server responds with 'Form submitted' anyway

C. The server throws a 403 Forbidden error

D. The server crashes with an uncaught exception

Solution

1. Step 1: Understand csurf error handling

   If the CSRF token is missing or invalid, csurf middleware triggers an error with status 403 Forbidden.

2. Step 2: Check route behavior

   The route handler is not called; instead, Express sends a 403 error response.

3. Final Answer:

   The server throws a 403 Forbidden error -> Option C

4. Quick Check:

   Invalid CSRF token = 403 Forbidden error [OK]

Hint: Missing token causes 403 error, not success [OK]

Common Mistakes:

• Assuming form submits anyway
• Thinking server redirects automatically
• Believing server crashes

4. You added csurf middleware but your form keeps failing CSRF validation. Which of these is the most likely cause?

medium

A. You did not install the cookie-parser package

B. You used app.use(express.json()) before csurf()

C. You set cookie: false in csurf options

D. You forgot to include the CSRF token in the form as a hidden input

Solution

1. Step 1: Check form token inclusion

   CSRF protection requires the token to be sent with the form, usually as a hidden input field.

2. Step 2: Evaluate other options

   While cookie-parser is needed if using cookies, the most common cause is missing token in the form.

3. Final Answer:

   You forgot to include the CSRF token in the form as a hidden input -> Option D

4. Quick Check:

   Missing token in form = validation fails [OK]

Hint: Always add CSRF token hidden input in forms [OK]

Common Mistakes:

• Ignoring token in form fields
• Misordering middleware without reason
• Assuming cookie-parser always required

5. You want to protect an Express app using csurf with cookie-based tokens and render the token in a form. Which code snippet correctly sets up the middleware and passes the token to the template?

hard

A. app.use(csurf({ cookie: false })); app.get('/form', (req, res) => { res.render('form', { csrfToken: req.csrfToken() }); });

B. app.use(csurf({ cookie: true })); app.get('/form', (req, res) => { res.render('form', { csrfToken: req.csrfToken() }); });

C. app.use(csurf()); app.get('/form', (req, res) => { res.render('form', { csrfToken: req.csrfToken }); });

D. app.use(csurf({ cookie: true })); app.get('/form', (req, res) => { res.render('form', { csrfToken: req.csrfToken }); });

Solution

1. Step 1: Setup csurf with cookie option

   Use csurf({ cookie: true }) to enable cookie-based CSRF tokens.

2. Step 2: Call req.csrfToken() as a function

   To get the token string, call req.csrfToken(), not just reference the function.

3. Step 3: Pass token to template

   Pass the token as csrfToken in the render call for the form to use.

4. Final Answer:

   app.use(csurf({ cookie: true })); app.get('/form', (req, res) => { res.render('form', { csrfToken: req.csrfToken() }); }); -> Option B

5. Quick Check:

   Correct csurf setup + token call = app.use(csurf({ cookie: true })); app.get('/form', (req, res) => { res.render('form', { csrfToken: req.csrfToken() }); }); [OK]

Hint: Call req.csrfToken() and enable cookie option [OK]

Common Mistakes:

• Not calling req.csrfToken() as a function
• Using cookie: false when cookies are needed
• Passing function reference instead of token string