moai-ref-owasp-checklist

Applies OWASP Top 10 security checklists to authentication, input validation, and HTTP header reviews.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/yekinya/moai-novel --skill moai-ref-owasp-checklist-yekinya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-ref-owasp-checklist
Source: https://github.com/yekinya/moai-novel/tree/main/moai-novel/.claude/skills/moai-ref-owasp-checklist
Command: npx skills add https://github.com/yekinya/moai-novel --skill moai-ref-owasp-checklist-yekinya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews often miss common vulnerabilities like broken authorization, injection flaws, and misconfigured headers because teams lack a structured, consistent checklist during development and audits. ## Core Features & Use Cases - OWASP API Security Top 10 Checklist: Covers BOLA, broken authentication, SSRF, and misconfiguration with concrete checks and defenses for each vulnerability class. - Authentication & Session Guidance: Provides password policy rules, JWT configuration values (expiry, algorithm, storage), and session security practices. - HTTP Security Headers & Input Validation: Supplies ready-to-apply header values (CSP, HSTS, X-Frame-Options) and validation patterns for SQL injection, XSS, path traversal, and file uploads. - Use Case: During a backend API security audit, an agent walks the OWASP Top 10 table, verifies JWT settings against the recommended values, and flags missing Content-Security-Policy headers with P0-P3 severity labels. ## Quick Start Ask the agent to review your API endpoints against the OWASP Top 10 checklist and report any missing security headers or authentication weaknesses.

Frequently Asked Questions about moai-ref-owasp-checklist

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

FAQPage Schema
How do I review an API against the OWASP Top 10?

Walk each of the ten vulnerability classes in the checklist, from BOLA to unsafe API consumption, and verify the listed check for every endpoint. The skill pairs each vulnerability with a concrete defense such as object ownership verification, rate limiting, or URL whitelisting.

What are the recommended JWT configuration settings?

Use a 15-30 minute access token expiry, 7-14 day refresh token expiry, and RS256 or HS256 algorithms. Store tokens in httpOnly, secure, sameSite cookies and keep payloads minimal with only userId and role, excluding PII.

Which HTTP security headers should every API response include?

Include Strict-Transport-Security, X-Content-Type-Options set to nosniff, X-Frame-Options set to DENY or SAMEORIGIN, Content-Security-Policy, Referrer-Policy, and Permissions-Policy. Each header blocks a specific attack class such as clickjacking, MIME sniffing, or XSS.

How should passwords be stored and validated securely?

Hash passwords with bcrypt at cost factor 12 or higher, or use Argon2id. Enforce a minimum of 8 characters, lock accounts temporarily after 5 failed attempts, and prevent reuse of the last 5 passwords.

When should this OWASP checklist not be used?

The checklist is scoped to backend security, authentication, and input validation. It does not cover frontend UI concerns, DevOps deployment, performance optimization, or testing strategy, so use domain-specific guidance for those areas.