mcpField
S
security-auditor

security-auditor

github.com/zhaono1Security851.1k installsUpdated 9w ago
Repository

About security-auditor

security-auditor is a skill for code review and application security checks, organizing audit guidance around the OWASP Top 10 and security practices. It includes scripts for audits and secret scanning, and treats the Top 10 as an awareness taxonomy rather than proof of complete coverage.

Key features

  1. 01Review risks using OWASP Top 10
  2. 02Inspect code, configuration, and dependencies
  3. 03Cover authentication, authorization, and injection
  4. 04Check error handling and security logging
  5. 05Provide audit and secret-scanning scripts

Use cases

  1. 01Review application code for security weaknesses
  2. 02Check deployment settings and dependency risks
  3. 03Scan project files for secrets
  4. 04Organize audit findings with a security checklist

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/zhaono1/agent-playbook --skill security-auditor

After installing, type/security-auditorin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
references/
checklist.md
owasp.md
remediation.md
scripts/
find_secrets.py
security_audit.py

Details

From the project README

Security Auditor

Expert in identifying security vulnerabilities following OWASP Top 10 and security best practices.

When This Skill Activates

Activates when you:

  • Request a security audit
  • Mention "security" or "vulnerability"
  • Need security review
  • Ask about OWASP

OWASP Top 10:2025 Coverage

Use the current OWASP Top 10 as an awareness taxonomy, not as proof of complete security coverage. For verifiable application controls, map findings to the current OWASP ASVS or the project's required standard.

A01: Broken Access Control
  • Verify authentication and object/function-level authorization on every sensitive path.
  • Test tenant boundaries, IDOR/BOLA, role changes, and server-side URL fetch controls.
  • SSRF is included in this 2025 category; validate destinations, schemes, redirects, and network egress.
A02: Security Misconfiguration
  • Inspect debug flags, CORS, security headers, default accounts, cloud/IaC policy, and error exposure.
  • Compare runtime configuration with hardened environment-specific defaults.
A03: Software Supply Chain Failures
  • Review lockfiles, provenance, build workflows, mutable CI dependencies, update policy, and dependency risk.
  • Distinguish a vulnerable package from compromised build or distribution infrastructure.
A04: Cryptographic Failures
  • Check secret storage, transport encryption, key lifecycle, random generation, algorithms, and data-at-rest requirements.
  • Flag hardcoded credentials, weak hashes, insecure modes, and missing certificate verification.
A05: Injection
  • Trace untrusted data into SQL/NoSQL, shell, template, LDAP, expression, and browser execution sinks.
  • Prefer parameterization and safe APIs; test encoding at the actual output context.
A06: Insecure Design
  • Threat-model trust boundaries, abuse cases, rate limits, high-risk workflows, and failure recovery.
  • Verify the design prevents unsafe states rather than relying only on downstream validation.
A07: Authentication Failures
  • Review credential handling, MFA where risk warrants it, reset/recovery flows, session rotation, expiry, and brute-force defenses.
A08: Software or Data Integrity Failures
  • Verify signatures, trusted update channels, deserialization boundaries, artifact integrity, and protection from unauthorized data changes.
A09: Security Logging and Alerting Failures
  • Check that security-relevant events are logged without secrets, protected from tampering, monitored, and connected to actionable alerts.
A10: Mishandling of Exceptional Conditions
  • Exercise malformed input, resource exhaustion, timeouts, partial failures, concurrency, and dependency outages.
  • Look for fail-open behavior, swallowed errors, unsafe retries, inconsistent state, and missing rollback or reconciliation.

Security Audit Checklist

Code Review
  • No hardcoded secrets
  • Input validation on all inputs
  • Output encoding for XSS prevention
  • Parameterized queries for SQL
  • Proper error handling
  • Authentication on protected routes
  • Authorization checks
  • Rate limiting on public APIs
Configuration
  • Debug mode off
  • HTTPS enforced
  • CORS configured correctly
  • Security headers set
  • Environment variables for secrets
  • Database not exposed
Dependencies
  • No known vulnerabilities
  • Dependencies up to date
  • Unused dependencies removed

Scripts

Run security audit:

python3 scripts/security_audit.py --name <service-name> --output security-audit.md

Check for secrets:

python3 scripts/find_secrets.py .

References

  • references/owasp.md - OWASP Top 10 details
  • references/checklist.md - Security audit checklist
  • references/remediation.md - Vulnerability remediation guide

Comments

Markdown supported