security

Guide secure coding and vulnerability identification in code reviews.

18|3|Updated Aug 20, 2009
One-click install
npx skills add https://github.com/booch/config_files --skill security-booch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/booch/config_files/tree/main/ai/skills/security
Command: npx skills add https://github.com/booch/config_files --skill security-booch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides comprehensive guidelines to help developers write secure code and reviewers identify vulnerabilities during code reviews, reducing the risk of exploits.

Core Features & Use Cases

  • Comprehensive security guidelines for secure coding, code review, and threat modeling.
  • Practical checks aligned with OWASP Top 10 and common development stacks.
  • Guidance for proactive security discussions during architecture and design reviews.

Quick Start

Begin by applying the secure coding guidelines to your current project and identify at least three actionable improvements.

Frequently Asked Questions about security

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

FAQPage Schema
How do I find security vulnerabilities during a code review?

To find security vulnerabilities during a code review, apply OWASP-aligned checks and defensive design principles to identify weaknesses in authorization, input validation, and secure coding practices across web, mobile, or backend services.

What is threat modeling and when do I need it for my architecture?

Threat modeling is a proactive process to identify and mitigate potential security exploits during design. You need it during architecture and design reviews to guide defensive decisions and establish incident readiness before implementation begins.

How do I implement secure coding practices aligned with OWASP standards?

Implement secure coding practices by applying comprehensive guidelines that address the OWASP Top 10, enforce input validation and authorization, and satisfy secure coding checklists across your development stack to reduce exploit risks.

Does this secure coding guidance apply to both web and mobile backend services?

Yes, this secure coding guidance applies to web, mobile, and backend services. It provides practical checks for common development stacks, ensuring defensive design and vulnerability mitigation across diverse platforms.

What is the best way to mitigate authorization and authentication vulnerabilities?

The best way to mitigate authorization and authentication vulnerabilities is to follow secure-by-default coding guidelines, apply input validation, and conduct thorough code reviews aligned with OWASP defensive design principles.

What are the limitations of relying solely on secure coding checklists?

Secure coding checklists provide a baseline but do not replace proactive threat modeling. To fully mitigate vulnerabilities, you must combine checklist compliance with defensive design discussions during architecture reviews and continuous code review.