agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/appsec/security-requirements/SKILL.md

security-requirements

Skill0 starsChanged 12 days agoMITView on GitHub

Define verifiable application security requirements using OWASP ASVS 5.0 levels (and MASVS for mobile), mapped to the application's risk, and turn them into acceptance criteria, tests and review checklists. Use when starting a project, writing security acceptance criteria for features, selecting an assurance level, or auditing an application against ASVS.

The file

Files
SKILL.md

Security Requirements (ASVS)

Choose a level

ASVS levelUse for
L1Low-risk apps; minimum baseline, largely testable externally
L2Most apps handling personal or business-sensitive data (default)
L3High-value apps: critical infrastructure, healthcare, finance, high-assurance identity

ASVS 5.0 (released 2025) reorganized chapters (e.g., encoding and sanitization, validation and business logic, web frontend security, API and web service, file handling, authentication, session management, authorization, self-contained tokens, OAuth/OIDC, cryptography, secure communication, configuration, data protection, logging and error handling). Requirement IDs changed from 4.0.3 — cite the version.

For all 17 chapters with example acceptance criteria and verification methods, and mappings to the OWASP Top 10:2025, API Security Top 10 2023 and LLM Top 10 2025, read references/owasp-mappings.md.

Workflow

  1. Classify the app (data, users, exposure) → choose level.
  2. Select relevant chapters (skip N/A: e.g., no file upload) and record why.
  3. Convert each requirement into acceptance criteria for stories, e.g.:
    • "Given a user requests /orders/{id} for an order they don't own, the API returns 403/404 and logs an authorization failure." (authorization)
    • "Session cookies have Secure, HttpOnly, SameSite=Lax or Strict." (session management)
  4. Map each to verification: unit/integration test, SAST rule, DAST check, manual review, pen test.
  5. Track coverage per release; exceptions through risk acceptance.

Output

ASVS ID (v5.0) | Requirement (short) | Applies? | Acceptance criteria | Verification method | Status | Evidence

Related skills

threat-modeling, secure-code-review, mobile-app-security-review, release-gate

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.