← 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 organized by OWASP Top 10 (2021) categories. Each item links to the relevant OWASP Cheat Sheet for detailed guidance. ## How to Use 1. Identify which categories are relevant to the code being written or reviewed 2. Walk through the checklist items in this document for those categories 3. **Consult the reference index below** to find relevant ASVS chapters and cheat sheets by topic 4. **Search local references** for specific requirements — use `Grep` on `references/` for keywords, ASVS IDs (V1, V1.2, V1.2.4), or topic terms. **Never read entire files** — search and read only matching sections with context (30–50 lines). 5. Use `search_standards` MCP tool (if available) to query coding and security 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 the [Framework-Specific Security](#framework-specific-security) section and read or fetch the corresponding cheat sheet 8. Always include OWASP cheat sheet URLs and ASVS requirement IDs in your 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 | |----