[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV7DPR71EFT4MAP3P0QHMF":3,"skill-same:01M7EV7DPR71EFT4MAP3P0QHMF":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EV7DPR71EFT4MAP3P0QHMF","owasp-security",null,"Apply OWASP frameworks (Top 10, ASVS, SAMM, MASVS, Cheat Sheets) to design, test, and harden web and mobile applications.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-owasp-security\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: owasp-security\ndescription: Apply OWASP frameworks (Top 10, ASVS, SAMM, MASVS, Cheat Sheets) to design, test, and harden web and mobile applications.\ncategory: security\n---\n\n## Overview\n\nOWASP (Open Worldwide Application Security Project) publishes community standards that are the common language of application security. The **OWASP Top 10** catalogs the most critical web-app risks; **ASVS** (Application Security Verification Standard) gives testable requirements at three assurance levels; **SAMM** (Software Assurance Maturity Model) guides program maturity; **MASVS** covers mobile; and the **Cheat Sheet Series** gives concise defensive implementation guidance.\n\nThis skill is how you turn those documents into practice: threat-driven secure design, checklist-based code review, and measurable verification. Everything here is defensive — the goal is building software that withstands attacks, not producing attacks.\n\nStart with the project's risk profile, not the document set: a public-facing payment API needs ASVS Level 2 verified end to end, while an internal dashboard may live at Level 1 with selected Level 2 controls. The documents are a menu driven by risk, and the cheat sheets are the recipes your developers will actually open during implementation.\n\n## When to use\n\n- Starting a new web\u002FAPI\u002Fmobile project and you need the baseline security requirements.\n- Reviewing code or architecture for injection, auth, crypto, and misconfiguration issues.\n- Defining security acceptance criteria for a release (\"ASVS Level 2 verified\").\n- Responding to a pentest or bug-bounty report and mapping findings to remediations.\n- Running developer security training anchored in a shared vocabulary.\n\n## Core concepts\n\n- **Top 10 risk categories (2021, with 2025 refresh direction):** broken access control, cryptographic failures, injection, insecure design, security misconfiguration, vulnerable\u002Foutdated components, identification & authentication failures, software\u002Fdata integrity failures, logging & monitoring failures, SSRF.\n- **ASVS levels:** L1 (opportunistic attackers — every app), L2 (most apps handling sensitive data — default target), L3 (high-value targets). Pick a level per app and verify against it.\n- **Insecure design vs insecure implementation:** the former is a missing threat model (e.g., no rate limiting on a password reset), the latter is a coding bug. Fix design issues in requirements, not just code.\n- **Defense in depth:** no single control is enough. Validate input AND parameterize queries AND encode output AND set least-privilege DB accounts.\n- **Positive\u002Fallowlist validation** beats denylist validation. Canonicalize, then validate against a strict allowlist.\n- **Cheat sheets as building blocks:** authentication, session management, XSS prevention, SQL injection prevention, secrets management, error handling — each maps to concrete code patterns.\n\n- **Security requirements are functional requirements.** 'Reset tokens expire in 15 minutes' belongs in the same backlog, with the same acceptance criteria, as any feature — otherwise it gets cut under schedule pressure.\n- **Map every control to a verification method.** For each ASVS requirement, decide how you will prove it: code review, SAST rule, DAST check, or manual test. Unverifiable requirements are wishes.\n- **Version-pin your baseline.** OWASP guidance evolves; record which Top 10\u002FASVS version you verified against so future assessments compare apples to apples.\n\n## Practical workflow\n\n1. **Classify the app:** data sensitivity, exposure (internal vs internet), compliance needs. Use this to pick an ASVS level (L1\u002FL2\u002FL3).\n2. **Threat-model the data flows:** draw trust boundaries, list entry points, enumerate Top 10 risks per flow. Capture as abuse cases alongside user stories.\n3. **Bake requirements in:** turn cheat-sheet guidance into backlog items — e.g., \"All DB queries parameterized (ASVS 5.3.1)\", \"Session tokens rotate on privilege change (ASVS 3.2.4)\".\n4. **Review against the list:** during code review, run the Top 10 as a mental checklist on every diff touching auth, input handling, crypto, or config.\n5. **Verify with testing:** map SAST\u002FDAST findings and manual tests to ASVS requirements; track pass\u002Ffail per requirement, not just raw finding counts.\n6. **Harden defaults:** disable debug, remove default creds, set security headers (CSP, HSTS, X-Content-Type-Options), lock down error messages.\n7. **Log and monitor:** ensure authentication failures, access-control failures, and input-validation failures produce alerts (Top 10 A09 — logging & monitoring failures).\n\n### Quick checklists\n\n**Injection:** parameterize all queries; use ORM safely (no raw string concatenation); validate and encode all output contexts (HTML, JS, URL, SQL, shell).\n**Broken access control:** deny by default; enforce checks server-side on every request; protect against IDOR by verifying ownership; test with a low-privilege account.\n**Crypto failures:** TLS 1.2+ everywhere; no custom crypto; passwords hashed with Argon2id\u002Fbcrypt\u002Fscrypt; secrets in a vault, never in code.\n**Auth failures:** MFA for privileged accounts; lockout + rate limiting; secure session lifecycle (HttpOnly, Secure, SameSite; rotation on privilege change).\n\n### Sustaining the practice\n\n- Re-run the ASVS verification on every major release, not just the first one\n- Keep cheat-sheet links inside your secure-coding guide where developers already look\n- Review the Top 10 delta on each new release and brief engineering on what changed\n- Track requirement pass-rate trends per application in the security dashboard\n\n### Metrics that prove it works\n\n- ASVS requirement pass rate at the target level, per application\n- % of new features with a threat model before build\n- Mean time to remediate Top-10-class findings, by severity\n- % of releases passing the secure-code review checklist\n\n## Common pitfalls\n\n- **Treating the Top 10 as a complete checklist.** It is a risk awareness list, not an exhaustive standard. Pair it with ASVS for verification.\n- **Fixing findings without fixing the class.** One XSS fixed while the templating pattern stays vulnerable means ten more next sprint. Fix the pattern, add the rule to review checklists.\n- **Scanning without triage.** DAST\u002FSAST output mapped to \"fix everything\" burns out teams. Prioritize by exploitability × data exposure, track by ASVS requirement.\n- **Security headers as decoration.** CSP only works if you remove `unsafe-inline`; HSTS needs includeSubDomains and preload discipline.\n- **Ignoring logging.** An app with no audit trail of auth failures fails ASVS and blinds incident response. Logging is a security control, not a nice-to-have.\n- **One-time assessments.** Security posture decays as code changes. Re-verify ASVS level on major releases; keep cheat sheets linked from your secure-coding guide.\n- **Treating the Top 10 as a priority order.** The list is not ranked for your app — rank by your data flows and exposure, not the list order.\n- **Letting the ASVS target drift.** Pick a level per app, document it, and re-verify on major releases — otherwise verification quietly decays to L1.\n- **Developer guidance that lives in a PDF nobody opens.** Put the cheat-sheet content into code-review checklists, linters, and PR templates — where the work happens.\n- **Verifying once at launch.** Dependencies, frameworks, and attack techniques move on. Re-verification cadence is part of the control, not optional.\n","## Overview\n\nOWASP (Open Worldwide Application Security Project) publishes community standards that are the common language of application security. The **OWASP Top 10** catalogs the most critical web-app risks; **ASVS** (Application Security Verification Standard) gives testable requirements at three assurance levels; **SAMM** (Software Assurance Maturity Model) guides program maturity; **MASVS** covers mobile; and the **Cheat Sheet Series** gives concise defensive implementation guidance.\n\nThis skill is how you turn those documents into practice: threat-driven secure design, checklist-based code review, and measurable verification. Everything here is defensive — the goal is building software that withstands attacks, not producing attacks.\n\nStart with the project's risk profile, not the document set: a public-facing payment API needs ASVS Level 2 verified end to end, while an internal dashboard may live at Level 1 with selected Level 2 controls. The documents are a menu driven by risk, and the cheat sheets are the recipes your developers will actually open during implementation.\n\n## When to use\n\n- Starting a new web\u002FAPI\u002Fmobile project and you need the baseline security requirements.\n- Reviewing code or architecture for injection, auth, crypto, and misconfiguration issues.\n- Defining security acceptance criteria for a release (\"ASVS Level 2 verified\").\n- Responding to a pentest or bug-bounty report and mapping findings to remediations.\n- Running developer security training anchored in a shared vocabulary.\n\n## Core concepts\n\n- **Top 10 risk categories (2021, with 2025 refresh direction):** broken access control, cryptographic failures, injection, insecure design, security misconfiguration, vulnerable\u002Foutdated components, identification & authentication failures, software\u002Fdata integrity failures, logging & monitoring failures, SSRF.\n- **ASVS levels:** L1 (opportunistic attackers — every app), L2 (most apps handling sensitive data — default target), L3 (high-value targets). Pick a level per app and verify against it.\n- **Insecure design vs insecure implementation:** the former is a missing threat model (e.g., no rate limiting on a password reset), the latter is a coding bug. Fix design issues in requirements, not just code.\n- **Defense in depth:** no single control is enough. Validate input AND parameterize queries AND encode output AND set least-privilege DB accounts.\n- **Positive\u002Fallowlist validation** beats denylist validation. Canonicalize, then validate against a strict allowlist.\n- **Cheat sheets as building blocks:** authentication, session management, XSS prevention, SQL injection prevention, secrets management, error handling — each maps to concrete code patterns.\n\n- **Security requirements are functional requirements.** 'Reset tokens expire in 15 minutes' belongs in the same backlog, with the same acceptance criteria, as any feature — otherwise it gets cut under schedule pressure.\n- **Map every control to a verification method.** For each ASVS requirement, decide how you will prove it: code review, SAST rule, DAST check, or manual test. Unverifiable requirements are wishes.\n- **Version-pin your baseline.** OWASP guidance evolves; record which Top 10\u002FASVS version you verified against so future assessments compare apples to apples.\n\n## Practical workflow\n\n1. **Classify the app:** data sensitivity, exposure (internal vs internet), compliance needs. Use this to pick an ASVS level (L1\u002FL2\u002FL3).\n2. **Threat-model the data flows:** draw trust boundaries, list entry points, enumerate Top 10 risks per flow. Capture as abuse cases alongside user stories.\n3. **Bake requirements in:** turn cheat-sheet guidance into backlog items — e.g., \"All DB queries parameterized (ASVS 5.3.1)\", \"Session tokens rotate on privilege change (ASVS 3.2.4)\".\n4. **Review against the list:** during code review, run the Top 10 as a mental checklist on every diff touching auth, input handling, crypto, or config.\n5. **Verify with testing:** map SAST\u002FDAST findings and manual tests to ASVS requirements; track pass\u002Ffail per requirement, not just raw finding counts.\n6. **Harden defaults:** disable debug, remove default creds, set security headers (CSP, HSTS, X-Content-Type-Options), lock down error messages.\n7. **Log and monitor:** ensure authentication failures, access-control failures, and input-validation failures produce alerts (Top 10 A09 — logging & monitoring failures).\n\n### Quick checklists\n\n**Injection:** parameterize all queries; use ORM safely (no raw string concatenation); validate and encode all output contexts (HTML, JS, URL, SQL, shell).\n**Broken access control:** deny by default; enforce checks server-side on every request; protect against IDOR by verifying ownership; test with a low-privilege account.\n**Crypto failures:** TLS 1.2+ everywhere; no custom crypto; passwords hashed with Argon2id\u002Fbcrypt\u002Fscrypt; secrets in a vault, never in code.\n**Auth failures:** MFA for privileged accounts; lockout + rate limiting; secure session lifecycle (HttpOnly, Secure, SameSite; rotation on privilege change).\n\n### Sustaining the practice\n\n- Re-run the ASVS verification on every major release, not just the first one\n- Keep cheat-sheet links inside your secure-coding guide where developers already look\n- Review the Top 10 delta on each new release and brief engineering on what changed\n- Track requirement pass-rate trends per application in the security dashboard\n\n### Metrics that prove it works\n\n- ASVS requirement pass rate at the target level, per application\n- % of new features with a threat model before build\n- Mean time to remediate Top-10-class findings, by severity\n- % of releases passing the secure-code review checklist\n\n## Common pitfalls\n\n- **Treating the Top 10 as a complete checklist.** It is a risk awareness list, not an exhaustive standard. Pair it with ASVS for verification.\n- **Fixing findings without fixing the class.** One XSS fixed while the templating pattern stays vulnerable means ten more next sprint. Fix the pattern, add the rule to review checklists.\n- **Scanning without triage.** DAST\u002FSAST output mapped to \"fix everything\" burns out teams. Prioritize by exploitability × data exposure, track by ASVS requirement.\n- **Security headers as decoration.** CSP only works if you remove `unsafe-inline`; HSTS needs includeSubDomains and preload discipline.\n- **Ignoring logging.** An app with no audit trail of auth failures fails ASVS and blinds incident response. Logging is a security control, not a nice-to-have.\n- **One-time assessments.** Security posture decays as code changes. Re-verify ASVS level on major releases; keep cheat sheets linked from your secure-coding guide.\n- **Treating the Top 10 as a priority order.** The list is not ranked for your app — rank by your data flows and exposure, not the list order.\n- **Letting the ASVS target drift.** Pick a level per app, document it, and re-verify on major releases — otherwise verification quietly decays to L1.\n- **Developer guidance that lives in a PDF nobody opens.** Put the cheat-sheet content into code-review checklists, linters, and PR templates — where the work happens.\n- **Verifying once at launch.** Dependencies, frameworks, and attack techniques move on. Re-verification cadence is part of the control, not optional.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-owasp-security",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill owasp-security",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill owasp-security",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill owasp-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-owasp-security\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]