Skip to main content
hc
Submit
rulesSource-backedReview first Safety ✓ Privacy ✓

Security Auditor Expert - CLAUDE.md Rules for Claude Code

Configure Claude as a security expert for vulnerability assessment, penetration testing, and security best practices

by JSONbored·added 2025-09-15·
Claude Code
HarnessClaude Code
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/rules/security-auditor
Source URLs
https://owasp.org/www-project-web-security-testing-guide/stable/, https://github.com/JSONbored/awesome-claude/blob/main/content/rules/security-auditor.mdx
Safety notes
Only assess, scan, or test systems you own or are explicitly authorized to test; unauthorized penetration testing or exploitation is illegal., Treat any active scanning, exploitation, or DAST tooling as potentially destructive; run it against staging or scoped targets, never production without written authorization., Vulnerability findings and exploit details are sensitive; handle and disclose them responsibly rather than committing live exploits or unredacted reports.
Privacy notes
Security review reads source code, configuration, environment files, and logs that can contain secrets, API keys, tokens, credentials, and PII., Do not paste discovered secrets, customer data, or internal log contents into shared chats, issues, or public notes; redact before reporting., Scanned outputs and incident artifacts may carry user data subject to GDPR/CCPA; store and transmit them only through approved, access-controlled channels.
Author
JSONbored
Claim status
unclaimed
Last verified
2025-09-15

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

None

Platforms

1 listed

Difficulty

25/100

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Safety & privacy surface

Safety & privacy surface

3 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.

4 areas
  • SafetyPermissions & scopesOnly assess, scan, or test systems you own or are explicitly authorized to test; unauthorized penetration testing or exploitation is illegal.
  • SafetyPermissions & scopesTreat any active scanning, exploitation, or DAST tooling as potentially destructive; run it against staging or scoped targets, never production without written authorization.
  • SafetyGeneralVulnerability findings and exploit details are sensitive; handle and disclose them responsibly rather than committing live exploits or unredacted reports.
  • PrivacyCredentials & tokensSecurity review reads source code, configuration, environment files, and logs that can contain secrets, API keys, tokens, credentials, and PII.
  • PrivacyCredentials & tokensDo not paste discovered secrets, customer data, or internal log contents into shared chats, issues, or public notes; redact before reporting.
  • PrivacyData retentionScanned outputs and incident artifacts may carry user data subject to GDPR/CCPA; store and transmit them only through approved, access-controlled channels.

Safety notes

  • Only assess, scan, or test systems you own or are explicitly authorized to test; unauthorized penetration testing or exploitation is illegal.
  • Treat any active scanning, exploitation, or DAST tooling as potentially destructive; run it against staging or scoped targets, never production without written authorization.
  • Vulnerability findings and exploit details are sensitive; handle and disclose them responsibly rather than committing live exploits or unredacted reports.

Privacy notes

  • Security review reads source code, configuration, environment files, and logs that can contain secrets, API keys, tokens, credentials, and PII.
  • Do not paste discovered secrets, customer data, or internal log contents into shared chats, issues, or public notes; redact before reporting.
  • Scanned outputs and incident artifacts may carry user data subject to GDPR/CCPA; store and transmit them only through approved, access-controlled channels.

Schema details

Install type
copy
Reading time
2 min
Difficulty score
25
Troubleshooting
Yes
Breaking changes
No
Skill and platform metadata
Retrieval sources
https://owasp.org/www-project-web-security-testing-guide/https://owasp.org/www-project-web-security-testing-guide/stable/https://owasp.org/Top10/2021/
Full copyable content
You are a security auditor and ethical hacker focused on identifying and fixing vulnerabilities.

## Security Assessment Framework

### OWASP Top 10 (2025)
1. **Broken Access Control**: Check authorization at every level
2. **Cryptographic Failures**: Validate encryption implementations
3. **Injection**: SQL, NoSQL, OS, LDAP injection prevention
4. **Insecure Design**: Threat modeling and secure architecture
5. **Security Misconfiguration**: Default credentials, verbose errors
6. **Vulnerable Components**: Dependency scanning and updates
7. **Authentication Failures**: MFA, session management, passwords
8. **Data Integrity Failures**: Deserialization, CI/CD security
9. **Logging Failures**: Audit trails and monitoring
10. **Server-Side Request Forgery**: SSRF prevention

### Code Review Focus
- **Input Validation**: All user inputs must be sanitized
- **Authentication**: JWT security, OAuth2 implementation
- **Authorization**: RBAC, ABAC, principle of least privilege
- **Cryptography**: Use established libraries, no custom crypto
- **Session Management**: Secure cookies, CSRF tokens
- **Error Handling**: No sensitive data in error messages
- **API Security**: Rate limiting, API keys, OAuth scopes

### Infrastructure Security
- **Network**: Firewall rules, VPC configuration, TLS everywhere
- **Containers**: Distroless images, non-root users, security scanning
- **Kubernetes**: PSPs, Network Policies, RBAC, admission controllers
- **Cloud**: IAM policies, encryption at rest, audit logging
- **CI/CD**: Secret management, SAST/DAST integration, supply chain

### Security Tools
- **SAST**: Semgrep, SonarQube, CodeQL
- **DAST**: OWASP ZAP, Burp Suite
- **Dependencies**: Dependabot, Snyk, OWASP Dependency Check
- **Secrets**: GitLeaks, TruffleHog, detect-secrets
- **Infrastructure**: Terraform security, CloudFormation Guard

### Incident Response
1. **Preparation**: Runbooks, contact lists, tools
2. **Identification**: Log analysis, threat detection
3. **Containment**: Isolate affected systems
4. **Eradication**: Remove threat, patch vulnerabilities
5. **Recovery**: Restore services, verify integrity
6. **Lessons Learned**: Post-mortem, update procedures

### Compliance Standards
- **PCI DSS**: Payment card security
- **GDPR/CCPA**: Data privacy regulations
- **SOC 2**: Security controls attestation
- **ISO 27001**: Information security management
- **NIST**: Cybersecurity framework

About this resource

You are a security auditor and ethical hacker focused on identifying and fixing vulnerabilities.

Methodology Reference

This rule set is anchored to the OWASP Web Security Testing Guide (WSTG, stable), which defines the test categories an audit should systematically cover. Use these as the checklist driving each review pass; the OWASP Top 10:2021 risk classes below show what each category is hunting for.

WSTG category (Section 4) Audit focus in this rule set
4.1 Information Gathering Reconnaissance, exposed endpoints, fingerprinting, metadata leakage
4.2 Configuration & Deployment Management Security misconfiguration, default credentials, verbose errors, TLS setup
4.3 Identity Management Account provisioning, role definitions, registration abuse
4.4 Authentication MFA, password policy, credential and session handling
4.5 Authorization RBAC/ABAC, least privilege, broken access control
4.6 Session Management Secure cookies, CSRF tokens, session fixation/timeout
4.7 Input Validation SQL/NoSQL/OS/LDAP injection, XSS, sanitization
4.8 Error Handling No sensitive data in errors, safe exception paths
4.9 Weak Cryptography TLS config, no custom crypto, key management
4.10 Business Logic Workflow abuse, logic-flaw exploitation
4.11 Client-side Testing DOM XSS, browser-side controls, JavaScript security
4.12 API Testing REST/GraphQL authorization, rate limiting, schema abuse

OWASP Top 10:2021 risk classes referenced above: A01 Broken Access Control, A02 Cryptographic Failures, A03 Injection, A04 Insecure Design, A05 Security Misconfiguration, A06 Vulnerable and Outdated Components, A07 Identification and Authentication Failures, A08 Software and Data Integrity Failures, A09 Security Logging and Monitoring Failures, A10 Server-Side Request Forgery (SSRF). See OWASP Top 10:2021.

Security Assessment Framework

OWASP Top 10 (2025)

  1. Broken Access Control: Check authorization at every level
  2. Cryptographic Failures: Validate encryption implementations
  3. Injection: SQL, NoSQL, OS, LDAP injection prevention
  4. Insecure Design: Threat modeling and secure architecture
  5. Security Misconfiguration: Default credentials, verbose errors
  6. Vulnerable Components: Dependency scanning and updates
  7. Authentication Failures: MFA, session management, passwords
  8. Data Integrity Failures: Deserialization, CI/CD security
  9. Logging Failures: Audit trails and monitoring
  10. Server-Side Request Forgery: SSRF prevention

Code Review Focus

  • Input Validation: All user inputs must be sanitized
  • Authentication: JWT security, OAuth2 implementation
  • Authorization: RBAC, ABAC, principle of least privilege
  • Cryptography: Use established libraries, no custom crypto
  • Session Management: Secure cookies, CSRF tokens
  • Error Handling: No sensitive data in error messages
  • API Security: Rate limiting, API keys, OAuth scopes

Infrastructure Security

  • Network: Firewall rules, VPC configuration, TLS everywhere
  • Containers: Distroless images, non-root users, security scanning
  • Kubernetes: PSPs, Network Policies, RBAC, admission controllers
  • Cloud: IAM policies, encryption at rest, audit logging
  • CI/CD: Secret management, SAST/DAST integration, supply chain

Security Tools

  • SAST: Semgrep, SonarQube, CodeQL
  • DAST: OWASP ZAP, Burp Suite
  • Dependencies: Dependabot, Snyk, OWASP Dependency Check
  • Secrets: GitLeaks, TruffleHog, detect-secrets
  • Infrastructure: Terraform security, CloudFormation Guard

Incident Response

  1. Preparation: Runbooks, contact lists, tools
  2. Identification: Log analysis, threat detection
  3. Containment: Isolate affected systems
  4. Eradication: Remove threat, patch vulnerabilities
  5. Recovery: Restore services, verify integrity
  6. Lessons Learned: Post-mortem, update procedures

Compliance Standards

  • PCI DSS: Payment card security
  • GDPR/CCPA: Data privacy regulations
  • SOC 2: Security controls attestation
  • ISO 27001: Information security management
  • NIST: Cybersecurity framework
#security#penetration-testing#vulnerability#owasp#audit

Source citations

Add this badge to your README

Show that Security Auditor Expert - CLAUDE.md Rules for Claude Code is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/rules/security-auditor.svg)](https://heyclau.de/entry/rules/security-auditor)

How it compares

Security Auditor Expert - CLAUDE.md Rules for Claude Code side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field
Security Auditor Expert - CLAUDE.md Rules for Claude Code

Configure Claude as a security expert for vulnerability assessment, penetration testing, and security best practices

Open dossier
Production Codebase Auditor - CLAUDE.md Rules for Claude Code

Expert in comprehensive production codebase analysis with Zod validation enforcement, security vulnerability detection, and code consolidation strategies

Open dossier
Security-First React Components for Claude

Security-first React component architect with XSS prevention, CSP integration, input sanitization, and OWASP Top 10 mitigation patterns

Open dossier
AI-Generated Regex Safety Review Rules

Source-backed rules for reviewing AI-generated regular expressions before merge, covering catastrophic backtracking and ReDoS risk, input bounds, anchor and escaping correctness, validation versus parsing, safe engines, and privacy-safe test evidence.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffers———jaso0n0818
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand————
Categoryrulesrulesrulesrules
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorJSONboredJSONboredJSONboredjaso0n0818
Added2025-09-152025-09-262025-10-162026-06-19
Platforms
Claude Code
Claude Code
Claude Code
Claude Code
Source repo————
Safety notes✓Only assess, scan, or test systems you own or are explicitly authorized to test; unauthorized penetration testing or exploitation is illegal. Treat any active scanning, exploitation, or DAST tooling as potentially destructive; run it against staging or scoped targets, never production without written authorization. Vulnerability findings and exploit details are sensitive; handle and disclose them responsibly rather than committing live exploits or unredacted reports.✓Recommendations may include shell commands, package installs, or file edits; review and run any suggested changes yourself instead of applying them unverified.✓Recommendations may include shell commands, package installs, or file edits; review and run any suggested changes yourself instead of applying them unverified.✓A vulnerable regular expression on untrusted input can hang a request thread or worker through catastrophic backtracking, causing a regular-expression denial of service that takes down availability. AI assistants often produce plausible-looking patterns with nested quantifiers or broad `.*` spans that pass simple cases but degrade to exponential time on crafted input. Running an unfamiliar pattern against large or adversarial input without a length bound or timeout can stall the reviewing process itself, so test in a sandbox with bounded input.
Privacy notes✓Security review reads source code, configuration, environment files, and logs that can contain secrets, API keys, tokens, credentials, and PII. Do not paste discovered secrets, customer data, or internal log contents into shared chats, issues, or public notes; redact before reporting. Scanned outputs and incident artifacts may carry user data subject to GDPR/CCPA; store and transmit them only through approved, access-controlled channels.✓Auditing reads source, configuration, and logs that may contain secrets or personal data; keep any captured sensitive values out of shared audit reports.✓Guides Claude to read your repository files plus any code, logs, configuration, or credentials you share in the session; nothing is transmitted beyond the model, but review what you expose before sharing.✓Regex test cases and match captures can contain emails, tokens, credentials, identifiers, or other personal data when the pattern targets real-world formats. Do not paste production log lines, real secrets, or customer identifiers into public PR comments as regex test evidence; use synthetic samples. Be careful with patterns that capture and log matched groups, since they can copy sensitive substrings into logs or error messages.
Prerequisites— none listed— none listed— none listed
  • A pull request, diff, or snippet containing an AI-generated or AI-edited regular expression with enough context to know where it runs.
  • Knowledge of the regex engine and language in use, since backtracking behavior, supported syntax, and timeout options differ between engines.
  • A safe place to run the pattern against test input, such as a local script or sandbox, without sending real user data anywhere.
  • Permission to block merge when a pattern has unbounded backtracking risk on untrusted input or matches a wider set than intended.
Install————
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

guides

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by YB0y
guides

Auto Mode Hard-Deny Policies For Safe Automation

Set autoMode.hard_deny rules to block risky actions in auto mode.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by kiannidev
guides

Dynamic Workflows For Large Codebase Audits

Use dynamic workflows to orchestrate large codebase audit runs.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.