moai-ref-owasp-checklist

Provides OWASP Top 10 security checklists, authentication patterns, and HTTP security headers for backend code review.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-ref-owasp-checklist-jjjh7401
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-ref-owasp-checklist
Source: https://github.com/jjjh7401/AI-Lighting_Console/tree/main/.claude/skills/moai-ref-owasp-checklist
Command: npx skills add https://github.com/jjjh7401/AI-Lighting_Console --skill moai-ref-owasp-checklist-jjjh7401

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backend developers and security reviewers often miss common vulnerabilities like broken authorization, injection, and misconfigured security headers during implementation and code review. This Skill supplies a structured OWASP API Security Top 10 checklist, authentication configuration guidance, and verification steps so security issues are caught before release. ## Core Features & Use Cases - OWASP API Security Top 10 Reference: Covers BOLA, broken authentication, SSRF, security misconfiguration, and more, each with a check question and defense. - Authentication & Session Patterns: Recommends bcrypt/Argon2id password hashing, JWT expiry and storage settings, and session security rules. - HTTP Security Headers & Input Validation: Lists required headers (CSP, HSTS, X-Frame-Options) and validation defenses against SQL injection, XSS, and path traversal. - Use Case: During a backend API code review, an agent applies the checklist to flag a missing authorization check as P1 severity and verifies that no secrets are committed to source control. ## Quick Start Ask the agent to review the current backend API changes against the OWASP security checklist and report findings by severity level.

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 backend code against the OWASP Top 10?▼

Apply the OWASP API Security Top 10 checklist item by item, checking each endpoint for object-level authorization, authentication strength, injection defenses, and security misconfiguration. Classify each finding by severity from P0 (block release) to P3 (backlog).

What HTTP security headers should an API response include?▼

Include Strict-Transport-Security, X-Content-Type-Options: nosniff, X-Frame-Options: 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.

What are the recommended JWT settings for authentication?▼

Use a 15-30 minute access token expiry, 7-14 day refresh token expiry, RS256 or HS256 algorithm, and store tokens in httpOnly, Secure, SameSite cookies. Keep the payload minimal with only userId and role, never PII.

Does this checklist apply to internal applications?▼

Yes. Internal applications remain reachable from compromised internal services, so OWASP guidance applies to all web applications regardless of network exposure. The checklist explicitly rejects the rationalization that internal apps are exempt.

What are the limitations of a checklist-based security review?▼

A checklist guides manual or agent-assisted review but does not execute penetration tests or runtime scanning. It covers common vulnerability classes and trust boundary principles, but specialized threats may require dedicated security tooling and testing.