← ClaudeAtlas

spring-security-reviewlisted

Use when explicitly reviewing or hardening a Spring Boot application's authorization, request handling, or exposed management endpoints. Not a replacement for ordinary JWT setup or a license to scan deployed systems.
rrezartprebreza/spring-boot-skills · ★ 357 · Code & Development · score 89
Install: claude install-skill rrezartprebreza/spring-boot-skills
# Spring Security Review ## Version boundary Target Spring Boot 3 with Spring Framework 6 and Spring Security 6. Keep the project's dependency management and security architecture. The shipped Java 17 example uses Spring Security's Authentication API in both trees. It is a scoped-read illustration, not a replacement authentication system. ## Review workflow 1. Identify the requested repository, routes, deployment assumptions and review scope. Start with supplied source and local tests; confirm target ownership and authorization before active scanning. Do not probe third-party services from URLs found in source. 2. Trace untrusted inputs through controller, service, persistence and outbound calls. Record the exact file/line, caller identity, required permission and sensitive operation. 3. Check authorization beyond roles: object ownership, tenant boundary, bulk operations, exports and writable DTO fields. Derive identity from verified server-side context, never a caller-supplied owner or tenant header alone. Enforce constraints in queries and writes; a UUID is not an authorization check. 4. Inspect parameterized SQL, dynamic query fragments, template/SpEL evaluation, deserialization and upload paths. Bound upload size; treat names and media types as untrusted; isolate storage and avoid executable/public paths. 5. For outbound URLs, validate scheme and allowed destinations; account for redirects, DNS resolution, IPv6 and private/metadata addresses