Security Hardening
Harden application security configuration with comprehensive security controls
npx claude-code-templates@latest --command security/security-hardening Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
Security Hardening
Harden application security configuration and controls: $ARGUMENTS
Current Security Posture
- Framework: @package.json or @requirements.txt or @Cargo.toml (detect framework)
- Security headers: !
curl -I http://localhost:3000 2>/dev/null | grep -i 'x-\|content-security\|strict-transport' || echo "No server running" - Environment config: @.env* (check for security-related variables)
- Dependencies: !
npm audit --audit-level=moderate 2>/dev/null || echo "Run dependency audit first"
Task
Implement comprehensive security hardening based on security best practices:
Hardening Focus: Use $ARGUMENTS to target specific areas or apply comprehensive hardening
Security Controls:
- Authentication & Authorization - MFA, RBAC, session security, password policies
- Input Validation - XSS prevention, SQL injection protection, CSRF tokens
- Secure Communication - HTTPS/TLS, HSTS, certificate management
- Data Protection - Encryption at rest/transit, key management, secure storage
- Security Headers - CSP, CORS, security response headers
- Infrastructure Security - Container hardening, network segmentation, monitoring
Output: Hardened application with comprehensive security controls, proper configuration, and monitoring capabilities.