/security-hardening
Harden application security configuration
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/security-hardening
Context preview
What this command does when you run it.
Harden application security configuration
Command definition
security-hardening.mdSecurity Hardening
Harden application security configuration
Instructions
1. **Security Assessment and Baseline**
- Conduct comprehensive security audit of current application
- Identify potential vulnerabilities and attack vectors
- Analyze authentication and authorization mechanisms
- Review data handling and storage practices
- Assess network security and communication protocols
2. **Authentication and Authorization Hardening**
- Implement strong password policies and multi-factor authentication
- Configure secure session management with proper timeouts
- Set up role-based access control (RBAC) with least privilege principle
- Implement JWT security best practices or secure session tokens
- Configure account lockout and brute force protection
3. **Input Validation and Sanitization**
- Implement comprehensive input validation for all user inputs
- Set up SQL injection prevention with parameterized queries
- Configure XSS protection with proper output encoding
- Implement CSRF protection with tokens and SameSite cookies
- Set up file upload security with type validation and sandboxing
4. **Secure Communication**
- Configure HTTPS with strong TLS/SSL certificates
- Implement HTTP Strict Transport Security (HSTS)
- Set up secure API communication with proper authentication
- Configure certificate pinning for mobile applications
- Implement end-to-end encryption for sensitive data transmission
5. **Data Protection and Encryption**
- Implement encryption at rest for sensitive data
- Configure secure key management and rotation
- Set up database encryption and access controls
- Implement proper secrets management (avoid hardcoded secrets)
- Configure secure backup and recovery procedures
6. **Security Headers and Policies**
- Configure Content Security Policy (CSP) headers
- Set up X-Frame-Options and X-Content-Type-Options headers
- Implement Referrer Policy and Feature Policy headers
- Configure CORS policies with proper origin validation
- Set up security.txt file for responsible disclosure
7. **Dependency and Supply Chain Security**
- Audit and update all dependencies to latest secure versions
- Implement dependency vulnerability scanning
- Configure automated security updates for critical dependencies
- Set up software composition analysis (SCA) tools
- Implement dependency pinning and integrity checks
8. **Infrastructure Security**
- Configure firewall rules and network segmentation
- Implement intrusion detection and prevention systems
- Set up secure logging and monitoring
- Configure secure container images and runtime security
- Implement infrastructure as code security scanning
9. **Application Security Controls**
- Implement rate limiting and DDoS protection
- Set up web application firewall (WAF) rules
- Configure secure error handling without information disclosure
- Implement proper logging for security events
- Set up security monitoring and alerting
10. **Security Testing and Validation**
- Conduct penetration testing and vulnerability assessments
- Implement automated security testing in CI/CD pipeline
- Set up static application security testing (SAST)
- Configure dynamic application security testing (DAST)
- Create security incident response plan and procedures
- Document security controls and compliance requirements
Read more
Security Hardening
Harden application security configuration
Instructions
1. **Security Assessment and Baseline**
- Conduct comprehensive security audit of current application
- Identify potential vulnerabilities and attack vectors
- Analyze authentication and authorization mechanisms
- Review data handling and storage practices
- Assess network security and communication protocols
2. **Authentication and Authorization Hardening**
- Implement strong password policies and multi-factor authentication
- Configure secure session management with proper timeouts
- Set up role-based access control (RBAC) with least privilege principle
- Implement JWT security best practices or secure session tokens
- Configure account lockout and brute force protection
3. **Input Validation and Sanitization**
- Implement comprehensive input validation for all user inputs
- Set up SQL injection prevention with parameterized queries
- Configure XSS protection with proper output encoding
- Implement CSRF protection with tokens and SameSite cookies
- Set up file upload security with type validation and sandboxing
4. **Secure Communication**
- Configure HTTPS with strong TLS/SSL certificates
- Implement HTTP Strict Transport Security (HSTS)
- Set up secure API communication with proper authentication
- Configure certificate pinning for mobile applications
- Implement end-to-end encryption for sensitive data transmission
5. **Data Protection and Encryption**
- Implement encryption at rest for sensitive data
- Configure secure key management and rotation
- Set up database encryption and access controls
- Implement proper secrets management (avoid hardcoded secrets)
- Configure secure backup and recovery procedures
6. **Security Headers and Policies**
- Configure Content Security Policy (CSP) headers
- Set up X-Frame-Options and X-Content-Type-Options headers
- Implement Referrer Policy and Feature Policy headers
- Configure CORS policies with proper origin validation
- Set up security.txt file for responsible disclosure
7. **Dependency and Supply Chain Security**
- Audit and update all dependencies to latest secure versions
- Implement dependency vulnerability scanning
- Configure automated security updates for critical dependencies
- Set up software composition analysis (SCA) tools
- Implement dependency pinning and integrity checks
8. **Infrastructure Security**
- Configure firewall rules and network segmentation
- Implement intrusion detection and prevention systems
- Set up secure logging and monitoring
- Configure secure container images and runtime security
- Implement infrastructure as code security scanning
9. **Application Security Controls**
- Implement rate limiting and DDoS protection
- Set up web application firewall (WAF) rules
- Configure secure error handling without information disclosure
- Implement proper logging for security events
- Set up security monitoring and alerting
10. **Security Testing and Validation**
- Conduct penetration testing and vulnerability assessments
- Implement automated security testing in CI/CD pipeline
- Set up static application security testing (SAST)
- Configure dynamic application security testing (DAST)
- Create security incident response plan and procedures
- Document security controls and compliance requirements
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Other commands on claude-command-suite.
- /boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Open command - /boundary-detect
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Open command - /boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Open command - /boundary-risk-assess
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Open command - /boundary-safe-bridge
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Open command - /optimize-prompt
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles: common words tokenize more efficiently, unusual words break into more tokens, and conciseness reduces cost.
Open command

