mcpField
O
owasp-top-10

owasp-top-10

github.com/nickcrewSecurity62759 installsUpdated 17w ago
Repository

About owasp-top-10

A security guidance skill for developers and auditors, based on OWASP Top 10 2021. It provides vulnerability references and a workflow for assessing, documenting, and verifying fixes.

Key features

  1. 01Covers OWASP Top 10 2021 risks
  2. 02Provides vulnerability reference guides
  3. 03Outlines audit and remediation steps
  4. 04Includes secure coding principles

Use cases

  1. 01Review application code and access controls
  2. 02Assess input validation and dependencies
  3. 03Document vulnerabilities and verify fixes
  4. 04Prepare for security compliance audits

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nickcrew/claude-cortex --skill owasp-top-10

After installing, type/owasp-top-10in Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
assessment-workflow.md
authentication-failures.md
broken-access-control.md
cryptographic-failures.md
injection.md
insecure-design.md
integrity-failures.md
logging-monitoring.md
prevention-strategies.md
security-misconfiguration.md
ssrf.md
vulnerable-components.md

Details

From the project README

OWASP Top 10 Security Vulnerabilities

Expert guidance for identifying, preventing, and remediating the most critical web application security risks based on OWASP Top 10 2021.

When to Use This Skill

  • Conducting security audits and code reviews
  • Implementing secure coding practices in new features
  • Reviewing authentication and authorization systems
  • Assessing input validation and sanitization
  • Evaluating third-party dependencies for vulnerabilities
  • Designing security controls and defense-in-depth strategies
  • Preparing for security certifications or compliance audits
  • Investigating security incidents or suspicious behavior

OWASP Top 10 2021 Overview

Ranked by Risk Severity:

  1. A01 - Broken Access Control (↑ from #5)
  2. A02 - Cryptographic Failures (formerly Sensitive Data Exposure)
  3. A03 - Injection (↓ from #1)
  4. A04 - Insecure Design (NEW)
  5. A05 - Security Misconfiguration
  6. A06 - Vulnerable and Outdated Components
  7. A07 - Identification and Authentication Failures
  8. A08 - Software and Data Integrity Failures (NEW)
  9. A09 - Security Logging and Monitoring Failures
  10. A10 - Server-Side Request Forgery (SSRF) (NEW)

Quick Reference

Load detailed guidance for each vulnerability:

VulnerabilityReference File
Broken Access Controlskills/owasp-top-10/references/broken-access-control.md
Cryptographic Failuresskills/owasp-top-10/references/cryptographic-failures.md
Injectionskills/owasp-top-10/references/injection.md
Insecure Designskills/owasp-top-10/references/insecure-design.md
Security Misconfigurationskills/owasp-top-10/references/security-misconfiguration.md
Vulnerable Componentsskills/owasp-top-10/references/vulnerable-components.md
Authentication Failuresskills/owasp-top-10/references/authentication-failures.md
Integrity Failuresskills/owasp-top-10/references/integrity-failures.md
Logging & Monitoringskills/owasp-top-10/references/logging-monitoring.md
SSRFskills/owasp-top-10/references/ssrf.md
Prevention Strategiesskills/owasp-top-10/references/prevention-strategies.md
Assessment Workflowskills/owasp-top-10/references/assessment-workflow.md

Security Audit Workflow

  1. Identify Scope: Determine application components and attack surface
  2. Select Vulnerabilities: Choose relevant OWASP categories based on features
  3. Load Reference: Read appropriate reference file(s) for detailed patterns
  4. Analyze Code: Review code against vulnerable and secure patterns
  5. Document Findings: Record vulnerabilities with severity and remediation
  6. Verify Fixes: Test that remediations properly address issues
  7. Test Security: Run automated security testing (SAST, DAST, SCA)

Core Security Principles

Defense in Depth
  • Layer security controls at network, application, data, and monitoring levels
  • Ensure failure of one control doesn't compromise entire system
Secure by Default
  • Deny all access by default, explicitly grant permissions
  • Fail securely (errors don't expose sensitive information)
  • Minimize attack surface (disable unused features)
  • Apply least privilege to all accounts and services
Input Validation
  • Validate type, length, format, and allowed values
  • Use allow-lists over deny-lists
  • Sanitize for specific context (SQL, HTML, shell, etc.)
  • Never trust client input

Common Mistakes

  1. Trusting User Input: Always validate and sanitize all user-supplied data
  2. Rolling Your Own Crypto: Use established libraries (bcrypt, AES-256)
  3. Exposing Errors: Log detailed errors internally, show generic messages to users
  4. Missing Authorization: Check permissions on every request, not just UI
  5. Weak Session Management: Use secure, httpOnly, sameSite cookies with HTTPS
  6. Ignoring Dependencies: Regularly audit and update third-party libraries
  7. No Logging: Log security events for detection and incident response
  8. Default Configurations: Harden all systems, disable defaults

Security Testing Tools

SAST (Static): SonarQube, Semgrep, ESLint security plugins DAST (Dynamic): OWASP ZAP, Burp Suite SCA (Dependencies): npm audit, Snyk, Dependabot Secrets Scanning: GitGuardian, TruffleHog Penetration Testing: Metasploit, Kali Linux tools

Resources

Comments

Markdown supported