Spring Security 6 & JWT Authentication · Lesson

Production Security Hardening

Apply essential security configurations and practices to harden your Spring Security application for a production environment.

Production Security Hardening is a free Spring Security 6 & JWT Authentication lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Spring Security 6 & JWT Authentication learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Production Hardening Intro

Welcome to Production Security Hardening! Securing an application in development is one thing, but production environments demand much higher vigilance.

In this lesson, we'll explore essential configurations and best practices to protect your Spring Security application when it goes live.

This isn't just about fixing bugs; it's about building a robust defense against real-world threats.

Why HTTPS is Non-Negotiable

In production, all communication between clients and your server must be encrypted using HTTPS (HTTP Secure).

Data Confidentiality: Protects sensitive data (passwords, personal info) from eavesdropping.
Data Integrity: Ensures data isn't tampered with during transmission.
Authentication: Verifies the server's identity to the client.

Without HTTPS, your application is vulnerable to Man-in-the-Middle (MITM) attacks.

Enforcing HTTPS with Spring Security

Spring Security can enforce that all requests must use a secure channel (HTTPS). If an HTTP request comes in, it will be redirected to HTTPS (if your server is configured for SSL).

The requiresSecure() method ensures this. Try running this minimal Spring Boot app and observe its behavior if you try to access it via HTTP (e.g., http://localhost:8080).

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.userdetails.UserDetails;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.provisioning.InMemoryUserDetailsManager;

@SpringBootApplication
public class HardeningApp {
    public static void main(String[] args) {
        SpringApplication.run(HardeningApp.class, args);
    }

    @Configuration
    @EnableWebSecurity
    static class SecurityConfig {

        @Bean
        public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
            http
                .authorizeHttpRequests(authorize -> authorize
                    .anyRequest().authenticated()
                )
                .requiresChannel(channel -> channel
                    .anyRequest().requiresSecure() // Enforce HTTPS
                )
                .formLogin(); // Basic form login for testing
            return http.build();
        }

        @Bean
        public UserDetailsService userDetailsService() {
            UserDetails user = User.withDefaultPasswordEncoder()
                .username("user")
                .password("password")
                .roles("USER")
                .build();
            return new InMemoryUserDetailsManager(user);
        }
    }
}

Overview of Security Headers

HTTP Security Headers are crucial for preventing common web vulnerabilities. They instruct browsers on how to behave when interacting with your application.

Key headers to configure:

HSTS (Strict-Transport-Security): Forces browsers to use HTTPS for future visits.
CSP (Content-Security-Policy): Prevents XSS attacks by restricting content sources.
X-Frame-Options: Stops clickjacking by controlling if your site can be embedded in an iframe.
X-Content-Type-Options: Prevents MIME-sniffing attacks.
Referrer-Policy: Controls how much referrer information is sent.

Configuring Security Headers

Spring Security provides convenient methods to configure these headers via HttpSecurity.headers(). This ensures your application's responses always include these vital instructions for the client's browser.

Here's how you can set up some common security headers in your configuration:

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.userdetails.UserDetails;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.provisioning.InMemoryUserDetailsManager;
import org.springframework.security.web.header.writers.ReferrerPolicyHeaderWriter;

@SpringBootApplication
public class HeaderApp {
    public static void main(String[] args) {
        SpringApplication.run(HeaderApp.class, args);
    }

    @Configuration
    @EnableWebSecurity
    static class SecurityConfig {

        @Bean
        public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
            http
                .authorizeHttpRequests(authorize -> authorize
                    .anyRequest().authenticated()
                )
                .headers(headers -> headers
                    .httpStrictTransportSecurity(hsts -> hsts
                        .includeSubDomains(true)
                        .maxAgeInSeconds(31536000) // 1 year
                    )
                    .contentSecurityPolicy(csp -> csp
                        .policyDirectives("default-src 'self'; script-src 'self' 'unsafe-inline'; object-src 'none'")
                    )
                    .frameOptions(frameOptions -> frameOptions.deny()) // X-Frame-Options: DENY
                    .xContentTypeOptions() // X-Content-Type-Options: nosniff
                    .referrerPolicy(referrer -> referrer
                        .policy(ReferrerPolicyHeaderWriter.ReferrerPolicy.NO_REFERRER)
                    )
                )
                .formLogin();
            return http.build();
        }

        @Bean
        public UserDetailsService userDetailsService() {
            UserDetails user = User.withDefaultPasswordEncoder()
                .username("user")
                .password("password")
                .roles("USER")
                .build();
            return new InMemoryUserDetailsManager(user);
        }
    }
}

Disabling Sensitive Endpoints

In production, you should disable or restrict access to any endpoints that could reveal sensitive information or allow unintended control.

Actuator Endpoints: Spring Boot Actuator provides useful operational insights (/actuator/**). In production, expose only necessary endpoints (e.g., /health, /info) and secure them.
HTTP TRACE/OPTIONS Methods: These methods can sometimes be exploited for information disclosure or cross-site tracing attacks. It's often best to disable them.

Always review what's exposed and ensure it's absolutely necessary and secured.

Custom Error Handling

Default error pages in development can expose stack traces and internal server details, which are valuable to attackers.

In production, configure custom error pages that provide minimal information. For example, a simple 'Error 500 - Internal Server Error' message without specifics.

Spring Boot allows you to define custom error pages (e.g., src/main/resources/public/error.html or src/main/resources/templates/error/404.html for specific status codes).

Secure Session Management

Session cookies are critical for maintaining user state, so they need robust protection. Spring Security helps, but you can further harden them.

HttpOnly: Prevents client-side scripts from accessing the cookie.
Secure: Ensures the cookie is only sent over HTTPS.
SameSite: Mitigates CSRF attacks by restricting when cookies are sent with cross-site requests (Lax or Strict).

These are often configured in application.properties, but Spring Security's sessionManagement() also offers controls.

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.security.config.http.SessionCreationPolicy;
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.userdetails.UserDetails;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.provisioning.InMemoryUserDetailsManager;

@SpringBootApplication
public class SessionApp {
    public static void main(String[] args) {
        SpringApplication.run(SessionApp.class, args);
    }

    @Configuration
    @EnableWebSecurity
    static class SecurityConfig {

        @Bean
        public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
            http
                .authorizeHttpRequests(authorize -> authorize
                    .anyRequest().authenticated()
                )
                .sessionManagement(session -> session
                    .sessionCreationPolicy(SessionCreationPolicy.IF_REQUIRED) // Default, but good to be explicit
                    .sessionFixation().migrateSession() // Protects against session fixation attacks
                )
                .csrf(csrf -> csrf.disable()) // CSRF is enabled by default, disable for simplicity in this example
                .formLogin();
            return http.build();
        }

        @Bean
        public UserDetailsService userDetailsService() {
            UserDetails user = User.withDefaultPasswordEncoder()
                .username("user")
                .password("password")
                .roles("USER")
                .build();
            return new InMemoryUserDetailsManager(user);
        }
    }
}

Secure Secrets Management

Never hardcode sensitive information (secrets) like database credentials, API keys, or encryption keys directly in your code or configuration files.

Best practices for managing secrets in production:

Environment Variables: Load secrets from environment variables.
Externalized Configuration: Use Spring Cloud Config Server or similar tools.
Dedicated Secret Management Services: HashiCorp Vault, AWS Secrets Manager, Azure Key Vault are designed for this purpose.

This prevents secrets from being exposed in source control or build artifacts.

Production Hardening Check

Which of the following are recommended practices for hardening a Spring Security application in a production environment? Select all that apply.

Recap & Next Steps

Great job! You've learned crucial steps to harden your Spring Security application for production.

We covered:

The necessity of HTTPS and how to enforce it.
Configuring vital HTTP security headers.
Restricting sensitive endpoints and providing custom error pages.
Implementing secure session management practices.
Best practices for managing secrets.

These practices form a strong foundation for a secure deployment. Next, we'll dive into logging and monitoring security events to detect and respond to threats effectively.

Frequently asked questions

Is the “Production Security Hardening” lesson free?

Yes — the full text of “Production Security Hardening” is free to read here on the web, and the Spring Security 6 & JWT Authentication course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Spring Security 6 & JWT Authentication course, upgrade to CoddyKit PRO.

What will I learn in “Production Security Hardening”?

Apply essential security configurations and practices to harden your Spring Security application for a production environment. You practise Spring Security 6 & JWT Authentication with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Spring Security 6 & JWT Authentication?

No prior experience is required. Spring Security 6 & JWT Authentication on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Production Security Hardening” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Spring Security 6 & JWT Authentication lesson?

Yes. Every Spring Security 6 & JWT Authentication lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Spring Security 6 & JWT Authentication