Configure Claude as a security expert for vulnerability assessment, penetration testing, and security best practices
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Safety & privacy surface
3 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.
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 frameworkYou are a security auditor and ethical hacker focused on identifying and fixing vulnerabilities.
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.
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.
[](https://heyclau.de/entry/rules/security-auditor)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 | Configure Claude as a security expert for vulnerability assessment, penetration testing, and security best practices Open dossier | Expert in comprehensive production codebase analysis with Zod validation enforcement, security vulnerability detection, and code consolidation strategies Open dossier | Security-first React component architect with XSS prevention, CSP integration, input sanitization, and OWASP Top 10 mitigation patterns Open dossier | 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 | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | — | — | — | jaso0n0818 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | rules | rules | rules | rules |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | JSONbored | JSONbored | JSONbored | jaso0n0818 |
| Added | 2025-09-15 | 2025-09-26 | 2025-10-16 | 2026-06-19 |
| Platforms | ||||
| Harness | ||||
| 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 |
|
| Install | — | — | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Audit MCP client configuration before sharing it with a team.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.