moai-ref-owasp-checklist

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

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-ref-owasp-checklist-seung-zedd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-ref-owasp-checklist
Source: https://github.com/Seung-zedd/secure-file-upload/tree/main/.claude/skills/moai-ref-owasp-checklist
Command: npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-ref-owasp-checklist-seung-zedd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backend developers and reviewers often miss common vulnerabilities like broken authorization, injection, or missing security headers because security knowledge is scattered. This Skill consolidates the OWASP API Security Top 10, authentication configuration guidance, input validation rules, and HTTP security headers into a single reference that agents can apply during implementation and security audits. ## Core Features & Use Cases - OWASP API Security Top 10 Checklist: Covers BOLA, broken authentication, SSRF, security misconfiguration, and more, each with a concrete check and defense. - Authentication & Session Guidance: Recommends bcrypt cost factors, JWT expiry settings, cookie attributes, and session handling rules. - Security Review Severity Model: Classifies findings from P0 (block release) to P3 (backlog) so teams can triage consistently. - Use Case: While reviewing a new API endpoint, an agent checks each OWASP item, verifies parameterized queries and security headers, and reports findings with severity levels and reason codes. ## Quick Start Ask the agent to review the current backend changes against the OWASP security checklist and report any findings with severity levels.

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 through each OWASP API Security Top 10 item and check the corresponding defense, such as verifying object ownership for BOLA and enforcing rate limits for resource consumption. Record which items were evaluated and assign each finding a severity from P0 to P3.

What are the recommended JWT security 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, never PII.

Which HTTP security headers should every API response include?▼

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

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 reference explicitly lists this as a common rationalization to reject.

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

A checklist guides manual or agent-driven review but does not execute dynamic scans or penetration tests. It is a reference for implementation and audit workflows, not a substitute for runtime vulnerability scanning or dedicated security tooling.