security-guidance

Apply OWASP ASVS security guidance with inline citations to planning and code reviews.

Updated Mar 24, 2023
One-click install
npx skills add https://github.com/j4hr3n/dotfiles --skill security-guidance-j4hr3n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-guidance
Source: https://github.com/j4hr3n/dotfiles/tree/main/configs/claude-code/skills/security-guidance
Command: npx skills add https://github.com/j4hr3n/dotfiles --skill security-guidance-j4hr3n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security-centric development guidance aligned with OWASP ASVS to reduce risk in code that handles user input, authentication, data persistence, network communication, file I/O, cryptography, and access control.

Core Features & Use Cases

  • ASVS-aligned decision index to guide secure coding decisions during planning and implementation.
  • Inline citations to applicable ASVS references in code, tests, and reviews.
  • Real-world use cases across planning, design, and development where security gates are applied.

Quick Start

Review the ASVS index and apply the relevant sections to the current task, citing the requirements inline.

Frequently Asked Questions about security-guidance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply OWASP ASVS requirements during secure code review?

OWASP ASVS secure coding guidance applies to planning and implementation tasks by providing an ASVS-aligned decision index and enforcing safe defaults in generated plans and code with inline requirement citations.

When do I need ASVS-aligned secure coding guidance for application planning?

You need ASVS-aligned secure coding guidance when planning features that handle user input, authentication, data persistence, network communication, file I/O, cryptography, or access control to reduce security risk from the design phase.

Can I use this to review access control and cryptography implementation?

Yes, it applies explicit ASVS section references to review access control and cryptography implementation, enforcing safe defaults and reducing risk across diverse task scenarios during design and code reviews.

What is the best way to enforce safe defaults in generated secure code?

Enforce safe defaults in generated secure code by applying OWASP ASVS-guided development, which provides an ASVS-aligned decision index and inline citations for applied security requirements across diverse task scenarios.

Does this security guidance work for network communication and file I/O tasks?

Yes, this security guidance works for network communication and file I/O tasks by applying OWASP ASVS-based requirements to reduce risk and enforce safe defaults in code handling these operations.

How to include inline ASVS citations in secure development plans?

Include inline ASVS citations in secure development plans by reviewing the ASVS index and applying relevant sections to the current task, explicitly citing the requirements directly in generated plans, code, tests, and reviews.