Financial Platform Security

Use when implementing Spring Security 6, JWT/Session authentication, RBAC, PII masking, and HMAC message integrity verification.

SahilKhan30 Updated

File contents

Financial Platform Security Skill

Purpose

Standardize authentication, authorization, PII protection, and message integrity across financial applications.


1. Principles & Rules

MANDATORY

  • PII Protection: Sensitive PII data (PAN, Aadhaar, VPA, Card Number) MUST be masked in logs and encrypted at rest (e.g. 4532-XXXX-XXXX-8921).
  • Input Parameterization: Use JPA parameterization and sanitized inputs to prevent SQL injection and XSS vulnerabilities.

REQUIREMENT-DRIVEN SECURITY

  • Authentication & CSRF: Derive authentication mechanism (stateless JWT vs session cookies) from explicit application requirements.
    • If authentication uses stateless bearer tokens (JWT) in headers, CSRF protection may be disabled (csrf -> csrf.disable()).
    • If authentication relies on browser cookies, CSRF protection MUST NOT be blindly disabled.
  • HMAC Signatures: Apply HMAC payload signature verification (X-Signature) ONLY when external message authenticity/integrity is explicitly required by gateway integration specifications.

SahilKhan30/claude-skill/tree/main/.claude/skills/security/financial-platform-security commit ff651dc073

Frequently asked questions

npx skillmds@latest add sahilkhan30/financial-platform-security