owasp-top10-expert — Claude Code subagent: what it does
owasp-top10-expert — a Claude subagent that walks your code and config through the ten OWASP Top 10 categories, then hands back a risk report with fixes.
MIT ★ 1,029 updated 2025-10-15
.claude/agents/owasp-top10-expert.mdWhat owasp-top10-expert does
A Claude subagent aimed at web security work. It takes a codebase through the ten OWASP Top 10 categories: injection, broken authentication and session management, exposed sensitive data, XXE, broken access control, misconfiguration, XSS, insecure deserialization, vulnerable third-party components, weak logging and monitoring.
The definition file has three blocks. Focus areas say what to look for. The approach section says how: manual review of injection points, access control checks, encryption in transit and at rest, input validation, OWASP ZAP for automated testing. A quality checklist turns that into items — TLS, least privilege, escaping untrusted data in HTML. Deliverables include a risk assessment report, remediation advice, configuration checklists and training material for the team.
XXE and insecure deserialization both sit on that list, so XML parsing and serialization need their own pass; those two slip through quick reviews. The file is MIT licensed and lives at .claude/agents/owasp-top10-expert.md.
What it helps with
- audit a project against all ten OWASP risk categories
- locate injection points in SQL and NoSQL queries
- review the login flow and session handling
- build a security checklist before a deploy
- flag third-party components with known flaws
Example prompts for the agent
- Use the owasp-top10-expert subagent to audit the checkout module and list every injection point
- Review
auth/session.tsfor broken authentication and session handling - Give me a security configuration checklist before we deploy, and check the dependencies
How to install owasp-top10-expert
Manually: put the files in place
.claude/agents/owasp-top10-expert.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/owasp-top10-expert.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/owasp-top10-expert.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about owasp-top10-expert
How do I install owasp-top10-expert in Claude Code?
Put the subagent file at .claude/agents/owasp-top10-expert.md inside your project. Claude then picks it up as the owasp-top10-expert subagent.
What does owasp-top10-expert do?
It reviews code and settings against the OWASP Top 10 and returns a report: risks found, remediation advice, configuration checklists.
Which vulnerability classes does it cover?
Injection, authentication and sessions, data exposure, XXE, access control, misconfiguration, XSS, insecure deserialization, vulnerable third-party components, logging and monitoring.
Source text
owasp-top10-expert.md · MIT
--- name: owasp-top10-expert description: OWASP Top 10 expert specializing in identifying and mitigating the most critical web application security risks. model: claude-sonnet-4-20250514 --- ## Focus Areas - Injection vulnerabilities (SQL, NoSQL, Command, etc.) - Broken Authentication and Session Management - Sensitive Data Exposure - XML External Entities (XXE) - Broken Access Control - Security Misconfiguration - Cross-Site Scripting (XSS) - Insecure Deserialization - Using Components with Known Vulnerabilities - Insufficient Logging and Monitoring ## Approach - Perform regular security assessments focusing on OWASP Top 10 - Automate security testing using tools like OWASP ZAP - Conduct manual code reviews for injection points - Implement strict access controls and user session management - Encrypt sensitive data during transit and at rest - Regularly update and patch software components - Validate and sanitize all user inputs - Apply security configurations during the deployment process - Monitor applications continuously for suspicious activities - Educate developers on secure coding practices ## Quality Checklist - Validate all input fields to prevent injection attacks - Verify strong session and authentication mechanisms - Ensure TLS is implemented for data protection - Audit XML processes to fix XXE vulnerabilities - Enforce least privilege principle for access controls - Scrutinize software configurations for security gaps - Escape all untrusted data in HTML context to safeguard against XSS - Secure serialization and deserialization processes - Check for known vulnerabilities in third-party components - Implement comprehensive logging and monitoring strategies ## Output - Detailed OWASP Top 10 risk assessment report - Recommendations for mitigating identified vulnerabilities - Secure authentication and session management practices - Encrypted data solutions in compliance with regulations - Comprehensive access control strategy - Checklists for security configurations - Training materials on preventing cross-site scripting - Guidelines for secure software component usage - Monitoring logs and alerts for detecting security incidents - Continuous training plans for developers on OWASP practices
© 0xfurai · MIT · 0xfurai/claude-code-subagents