security-scanning
Scan code for security vulnerabilities. Use after implementation changes.
When & Why to Use This Skill
This Claude skill provides automated security scanning capabilities to identify and mitigate vulnerabilities within source code. It streamlines the detection of OWASP Top 10 risks, hardcoded secrets, and improper input handling, ensuring that security best practices are maintained throughout the development lifecycle and after every implementation change.
Use Cases
- Post-Implementation Security Audit: Automatically scan new code changes for potential vulnerabilities immediately after development to ensure no regressions were introduced.
- OWASP Compliance Verification: Systematically check source code against the OWASP Top 10 list to prevent common web-based attacks like injection and broken authentication.
- Secret and Credential Detection: Scan repositories to identify and remove hardcoded API keys, passwords, or sensitive data before they are committed to version control.
- Input/Output Sanitization Review: Analyze code blocks to verify that user inputs are properly validated and outputs are correctly encoded to prevent Cross-Site Scripting (XSS) and other injection flaws.
| name | security-scanning |
|---|---|
| description | Scan code for security vulnerabilities. Use after implementation changes. |
Security Scanning
Verify security requirements are implemented and scan for common vulnerabilities.
Scan Areas
- Controls: Verify required controls are implemented
- OWASP Top 10: Check for common vulnerabilities
- Secrets: Ensure no hardcoded credentials
- Input/Output: Validate proper sanitization
Output
Create security-findings.md using the template in templates/security-findings.md.
Tips
- Check against security-requirements.md
- Look for injection vulnerabilities
- Verify authentication/authorization checks
- Ensure proper error handling (no info leakage)
- Check for hardcoded secrets or sensitive data