diff options
| author | TheSiahxyz <164138827+TheSiahxyz@users.noreply.github.com> | 2026-01-16 08:30:14 +0900 |
|---|---|---|
| committer | TheSiahxyz <164138827+TheSiahxyz@users.noreply.github.com> | 2026-01-16 08:30:14 +0900 |
| commit | 3fbb9a18372f2b6a675dd6c039ba52be76f3eeb4 (patch) | |
| tree | aa694a36cdd323a7853672ee7a2ba60409ac3b06 /default/.claude/commands/security/security-audit.md | |
updates
Diffstat (limited to 'default/.claude/commands/security/security-audit.md')
| -rw-r--r-- | default/.claude/commands/security/security-audit.md | 102 |
1 files changed, 102 insertions, 0 deletions
diff --git a/default/.claude/commands/security/security-audit.md b/default/.claude/commands/security/security-audit.md new file mode 100644 index 0000000..8d0efa4 --- /dev/null +++ b/default/.claude/commands/security/security-audit.md @@ -0,0 +1,102 @@ +# Security Audit + +Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations. + +## Usage Examples + +### Basic Usage +"Run a security audit on this project" +"Check for security vulnerabilities in the authentication module" +"Scan the API endpoints for security issues" + +### Specific Audits +"Check for SQL injection vulnerabilities" +"Audit the file upload functionality for security risks" +"Review authentication and authorization implementation" +"Check for hardcoded secrets and API keys" + +## Instructions for Claude + +When performing a security audit: + +1. **Systematic Scanning**: Examine the codebase systematically for common vulnerability patterns +2. **Use OWASP Guidelines**: Reference OWASP Top 10 and other security standards +3. **Check Multiple Layers**: Review frontend, backend, database, and infrastructure code +4. **Prioritize Findings**: Categorize issues by severity (Critical, High, Medium, Low) +5. **Provide Remediation**: Include specific fixes for each identified issue + +### Security Checklist + +#### Authentication & Authorization +- Password storage and hashing methods +- Session management security +- JWT implementation and validation +- Access control and permission checks +- Multi-factor authentication support + +#### Input Validation & Sanitization +- SQL injection prevention +- XSS (Cross-Site Scripting) protection +- Command injection safeguards +- Path traversal prevention +- File upload validation + +#### Data Protection +- Encryption in transit (HTTPS/TLS) +- Encryption at rest +- Sensitive data exposure +- API key and secret management +- PII handling compliance + +#### Common Vulnerabilities +- CSRF protection +- Clickjacking prevention +- Security headers configuration +- Dependency vulnerabilities +- Insecure direct object references + +#### API Security +- Rate limiting implementation +- API authentication methods +- Input validation on endpoints +- Error message information leakage +- CORS configuration + +### Output Format + +Provide a structured security report with: + +```markdown +## Security Audit Report + +### Summary +- Total issues found: X +- Critical: X, High: X, Medium: X, Low: X + +### Critical Issues +#### 1. [Issue Name] +- **Location**: file.js:line +- **Description**: Detailed explanation +- **Impact**: Potential consequences +- **Remediation**: Specific fix with code example + +### High Priority Issues +[Similar format] + +### Medium Priority Issues +[Similar format] + +### Low Priority Issues +[Similar format] + +### Recommendations +- General security improvements +- Best practices to implement +- Tools and libraries to consider +``` + +Remember to: +- Be specific about file locations and line numbers +- Provide code examples for fixes +- Explain the security impact clearly +- Avoid false positives by understanding the context
\ No newline at end of file |
