security-review-checklist

Detect security vulnerabilities like missing authorization checks and privilege escalation in code.

2.3k|769|Updated Jan 14, 2016
One-click install
npx skills add https://github.com/Bottelet/DaybydayCRM --skill security-review-checklist-bottelet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review-checklist
Source: https://github.com/Bottelet/DaybydayCRM/tree/main/.claude/skills/security-review-checklist
Command: npx skills add https://github.com/Bottelet/DaybydayCRM --skill security-review-checklist-bottelet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides static review rules to identify potential security vulnerabilities in code, streamlining the review process and enhancing code safety.

Core Features & Use Cases

  • Authorization Checks: Ensures that sensitive actions have explicit authorization checks.
  • Policy Usage: Validates the correctness of policy usage in the code.
  • Privilege Escalation Risks: Identifies potential risks of privilege escalation.
  • Controller and Action Exposure: Alerts on unsafe exposure of controllers or actions.
  • Validation Gaps: Checks for gaps in validation of external inputs.
  • Use Case: Ideal for security audits in software development projects to catch potential vulnerabilities early in the code review process.

Quick Start

Run the 'security-review-checklist' skill on your codebase to identify potential security issues.

Frequently Asked Questions about security-review-checklist

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

FAQPage Schema
How do I detect security risks in code during the review phase?

To detect security risks in code during the review phase, run static code analysis to identify missing authorization checks, incorrect policy usage, and potential privilege escalation.

What is static code analysis for security vulnerabilities?

Static code analysis for security vulnerabilities is a mechanism that reviews source code to detect validation gaps, incorrect policy usage, and unsafe controller exposure without executing the program.

Can I use this for a security audit to catch missing authorization checks?

Yes, you can use this for a security audit to catch missing authorization checks, validate policy usage, and identify potential privilege escalation risks in software development projects.

What's the best way to identify potential privilege escalation in my codebase?

The best way to identify potential privilege escalation is applying static review rules to scan your codebase, alerting on unsafe controller exposure and incorrect policy usage.

Does static code analysis detect validation gaps in external inputs?

Static code analysis does detect validation gaps in external inputs by checking for explicit authorization and validating the correctness of policy usage throughout the code.