← ClaudeAtlas

security-best-practiceslisted

OWASP-based secure programming practices. Use when writing or reviewing code handling auth, crypto, user input, secrets, or API endpoints. Consult proactively during reviews and planning.
lklimek/claudius · ★ 1 · API & Backend · score 67
Install: claude install-skill lklimek/claudius
# Secure Programming Best Practices Actionable security checklists by OWASP Top 10 (2021) category; each item links to the relevant OWASP Cheat Sheet. ## How to Use 1. Identify the categories relevant to the code being written or reviewed 2. Walk their checklist items below 3. **Consult the reference index below** for relevant ASVS chapters and cheat sheets by topic 4. **Search local references** — `Grep` `references/` for keywords, ASVS IDs (V1, V1.2, V1.2.4), or topic terms. **Never read entire files** — read only matching sections with context (30–50 lines) 5. Use the `search_standards` MCP tool (if available) for standards beyond local references 6. **Fetch OWASP cheat sheets** for implementation detail when local references aren't enough — fetch the linked URL for every relevant checklist item 7. For framework-specific guidance, see [Framework-Specific Security](#framework-specific-security) and read or fetch the corresponding cheat sheet 8. Always include OWASP cheat sheet URLs and ASVS requirement IDs in output ### Local Reference Index **ASVS 5.0** — `references/OWASP_Application_Security_Verification_Standard_5.0.0_en.csv` CSV columns: `chapter_id,chapter_name,section_id,section_name,req_id,req_description,level` (L1=basic, L2=standard, L3=advanced) | ID | Chapter | Key sections | |----|---------|-------------| | V1 | Encoding and Sanitization | V1.1 Architecture, V1.2 Injection Prevention, V1.3 Sanitization, V1.4 Memory, V1.5 Safe Deserialization | | V2 | Vali