owasp-top10-review

Assess a codebase category-by-category against the OWASP Top 10:2025 taxonomy.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/gener8v/gener8v.claude-skills --skill owasp-top10-review-gener8v
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: owasp-top10-review
Source: https://github.com/gener8v/gener8v.claude-skills/tree/main/skills/owasp-top10-review
Command: npx skills add https://github.com/gener8v/gener8v.claude-skills --skill owasp-top10-review-gener8v

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews that hunt bugs bottom-up often miss entire risk categories, leaving teams unable to answer "are we OWASP-compliant?" before an audit or customer security questionnaire. This Skill walks all ten OWASP Top 10:2025 categories top-down, maps existing SEC-XXX findings onto the framework, and produces a coverage matrix that makes gaps and strengths legible. ## Core Features & Use Cases - Category-by-Category Coverage Assessment: Walks A01 through A10 of the 2025 edition, recording what was checked, evidence of controls, and gaps for every category including "not applicable" ones. - Finding Mapping and Re-Ranking: Maps existing per-ticket security review findings (SEC-XXX) onto the taxonomy and re-ranks priorities according to the 2025 weighting, without duplicating prior work. - Under-Probed Category Verification: Actively greps for deserialization risks, security logging gaps, fail-open exception handling, and SSRF, plus deep passes on the new A03 supply chain and A10 exceptional-conditions categories. - Use Case: Before a customer security questionnaire, run the assessment to map six months of accumulated security review findings onto the OWASP Top 10:2025, discover that A09 logging was never probed, and receive a re-ranked priority list with new findings ready for ticket breakdown. ## Quick Start Ask the AI to run an OWASP Top 10 assessment on your system by providing its slug, for example "assess the billing-api system against the OWASP Top 10".

Frequently Asked Questions about owasp-top10-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my codebase is OWASP Top 10 compliant?▼

Run a category-by-category assessment that walks all ten OWASP Top 10:2025 categories, records evidence of controls for each, and maps existing security findings onto the taxonomy. The output is a coverage matrix showing which categories are adequate and which have gaps.

What changed in the OWASP Top 10 2025 edition?▼

The 2025 edition moved Security Misconfiguration to #2, introduced Software Supply Chain Failures at #3, and added Mishandling of Exceptional Conditions at #10. SSRF is no longer a standalone category and is assessed as a sub-check under other categories.

What is the difference between a security review and an OWASP Top 10 assessment?▼

A security review hunts individual vulnerabilities bottom-up for a delivered ticket, while an OWASP Top 10 assessment works top-down to prove coverage across all ten categories. The assessment maps existing findings onto the framework rather than re-deriving them.

Can I run an OWASP assessment without prior security review reports?▼

Yes, the assessment degrades gracefully and derives findings directly from the codebase when no prior security reviews exist. With existing reports, it maps their findings onto categories and supplements with newly discovered issues.

Why do bottom-up security reviews miss some OWASP categories?▼

Bug-hunting passes reliably under-probe insecure deserialization, security logging gaps, fail-open error handling, and SSRF because these require targeted searches rather than route-by-route inspection. The assessment actively greps for patterns like pickle, yaml.load, broad except clauses, and backend fetches of user-controlled URLs.

When should I not use an OWASP Top 10 assessment?▼

Do not use it for reviewing a single delivered ticket, which belongs to a per-ticket security review, or for assessing the model surface of an LLM application, which belongs to the OWASP LLM Top 10 review. It also does not replace deep bug-hunting or threat modeling.