Securing actuator endpoints in Spring Boot - Performance & Optimization

Performance: Securing actuator endpoints

MEDIUM IMPACT

This affects the initial page load speed and interaction responsiveness by controlling access to sensitive management endpoints.

Protecting sensitive actuator endpoints in a Spring Boot application

Spring Boot

management.endpoints.web.exposure.include=health,info
spring.security.user.name=admin
spring.security.user.password=strongpassword
# Secure actuator endpoints with basic authentication and limit exposure

Limits exposed endpoints and requires authentication, reducing unauthorized access and protecting server resources.

📈 Performance GainPrevents unnecessary load from unauthorized requests, maintaining stable response times and interaction performance

Protecting sensitive actuator endpoints in a Spring Boot application

Spring Boot

management.endpoints.web.exposure.include=*
# No authentication or authorization configured for actuator endpoints

Exposes all actuator endpoints publicly, risking security and potential abuse which can lead to performance degradation under attack.

📉 Performance CostIncreased risk of high load from unauthorized requests causing slower response times and potential denial of service

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Unsecured actuator endpoints	N/A	N/A	N/A	[X] Bad
Secured and limited actuator endpoints	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Securing actuator endpoints affects the server response phase before any content reaches the browser. It controls whether the request is processed or rejected early, impacting interaction responsiveness.

→Server Request Handling

→Response Generation

⚠️ BottleneckServer Request Handling when unauthorized requests flood endpoints

Core Web Vital Affected

INP

This affects the initial page load speed and interaction responsiveness by controlling access to sensitive management endpoints.

Optimization Tips

1Always require authentication for sensitive actuator endpoints.

2Limit actuator endpoint exposure to only what is necessary.

3Monitor actuator endpoint access to detect and prevent abuse.

Performance Quiz - 3 Questions

What is the main performance risk of leaving actuator endpoints unsecured?

A CSS styles will not load properly

B Unauthorized requests can overload the server causing slow response times

C The browser will block rendering of the page

D JavaScript execution will be delayed

DevTools: Network

How to check: Open DevTools, go to Network tab, request actuator endpoints, and check response status codes and timing.

What to look for: Look for 401 or 403 status codes indicating secured endpoints and fast response times without delays from unauthorized access.

Practice

1. What is the main purpose of securing Spring Boot actuator endpoints?

easy

A. To improve application performance by disabling endpoints

B. To automatically update actuator endpoints without manual configuration

C. To enable actuator endpoints for all users without restrictions

D. To protect sensitive application information from unauthorized access

Solution

1. Step 1: Understand actuator endpoints role

   Actuator endpoints provide information about the app's health, metrics, and configuration.

2. Step 2: Recognize security importance

   Since these endpoints expose sensitive data, securing them prevents unauthorized users from accessing this info.

3. Final Answer:

   To protect sensitive application information from unauthorized access -> Option D

4. Quick Check:

   Actuator security = protect info [OK]

Hint: Actuator endpoints show app info; protect them from strangers [OK]

Common Mistakes:

• Thinking actuator endpoints improve performance
• Assuming all endpoints should be open
• Believing security auto-applies without config

2. Which property correctly exposes only the health and info actuator endpoints in application.properties?

easy

A. management.endpoints.web.expose=health,info

B. management.endpoints.web.exposure.include=health,info

C. management.endpoints.exposure.include=health,info

D. management.web.endpoints.include=health,info

Solution

1. Step 1: Identify correct property name

   The correct property to expose endpoints is management.endpoints.web.exposure.include.

2. Step 2: Verify property value format

   Comma-separated list of endpoints like health,info is correct.

3. Final Answer:

   management.endpoints.web.exposure.include=health,info -> Option B

4. Quick Check:

   Correct property = management.endpoints.web.exposure.include [OK]

Hint: Use 'management.endpoints.web.exposure.include' to list endpoints [OK]

Common Mistakes:

• Using 'expose' instead of 'exposure.include'
• Missing 'web' in the property path
• Incorrect property structure or spelling

3. Given this Spring Security config snippet, what is the effect on actuator endpoints?

http
  .authorizeHttpRequests(auth -> auth
    .requestMatchers("/actuator/**").hasRole("ADMIN")
    .anyRequest().authenticated()
  )

medium

A. Only users with ADMIN role can access any actuator endpoint

B. All users can access actuator endpoints without login

C. Actuator endpoints are disabled

D. Only unauthenticated users can access actuator endpoints

Solution

1. Step 1: Analyze requestMatchers rule

   The matcher "/actuator/**" requires users to have role ADMIN to access.

2. Step 2: Understand anyRequest rule

   All other requests require authentication but no specific role.

3. Final Answer:

   Only users with ADMIN role can access any actuator endpoint -> Option A

4. Quick Check:

   Actuator access = ADMIN role required [OK]

Hint: Check role in requestMatchers for actuator URLs [OK]

Common Mistakes:

• Assuming actuator is open to all
• Confusing authentication with authorization
• Ignoring the role requirement

4. What is wrong with this security configuration for actuator endpoints?

@Bean
public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
  http
    .authorizeHttpRequests(auth -> auth
      .requestMatchers("/actuator/**").authenticated()
      .anyRequest().permitAll()
    );
  return http.build();
}

medium

A. The requestMatchers pattern is incorrect syntax

B. The method should return void, not SecurityFilterChain

C. Actuator endpoints require login but other URLs are open, risking security

D. The configuration disables all security

Solution

1. Step 1: Review authorization rules order

   Actuator endpoints require authentication, but all other requests are permitted without login.

2. Step 2: Identify security risk

   This means non-actuator URLs are open, which might expose sensitive parts unintentionally.

3. Final Answer:

   Actuator endpoints require login but other URLs are open, risking security -> Option C

4. Quick Check:

   PermitAll on anyRequest risks open access [OK]

Hint: Check if anyRequest().permitAll() opens unwanted URLs [OK]

Common Mistakes:

• Thinking method return type is wrong
• Assuming requestMatchers syntax is invalid
• Believing security is fully disabled

5. You want to expose only the health endpoint publicly and secure all other actuator endpoints to ADMIN role. Which configuration achieves this correctly?

hard

A. Expose health only and configure security to permit all on /actuator/health and ADMIN role on /actuator/** except health

B. Expose all endpoints and secure only /actuator/health to ADMIN role

C. Expose health and info endpoints and allow anonymous access to all actuator URLs

D. Expose no endpoints and disable security for actuator URLs

Solution

1. Step 1: Set exposure property

   Use management.endpoints.web.exposure.include=health to expose only health publicly.

2. Step 2: Configure security rules

   Permit all access to /actuator/health and require ADMIN role for other actuator endpoints using requestMatchers.

3. Final Answer:

   Expose health only and configure security to permit all on /actuator/health and ADMIN role on /actuator/** except health -> Option A

4. Quick Check:

   Expose health public + secure others ADMIN [OK]

Hint: Expose health only, secure others with ADMIN role [OK]

Common Mistakes:

• Exposing too many endpoints publicly
• Not securing non-health actuator endpoints
• Allowing anonymous access to sensitive endpoints