onfire7777 Security Audit
Thinking Protocol
Before auditing, answer silently:
- What is the attack surface? (public endpoints, user inputs, file uploads, auth flows)
- What data is most valuable to an attacker?
- What is the blast radius if compromised?
Execution
Phase 1: Reconnaissance
- Map attack surface: entry points, data flows, trust boundaries
- Identify stack and known CVEs per dependency
- Scan for secrets: API keys, tokens, passwords, connection strings
Phase 2: OWASP Top 10 (2025) Sweep
Actively attempt to find vulnerabilities for each category:
- Broken Access Control — privilege escalation paths
- Cryptographic Failures — plaintext storage, weak algorithms
- Injection — SQL, XSS, SSRF, command, path traversal
- Insecure Design — missing rate limits, threat modeling gaps
- Security Misconfiguration — debug mode, open CORS, verbose errors
- Vulnerable Components — known CVEs in dependencies
- Auth Failures — weak passwords, session fixation, JWT issues
- Data Integrity — unsigned updates, CI/CD pipeline poisoning
- Logging Gaps — missing audit trails, PII in logs
- SSRF — internal service access from server
Phase 3: Report
Per finding:
[CRITICAL|HIGH|MEDIUM|LOW] — [Vulnerability Type]
Location: [file:line or endpoint]
Attack: [How exploited — specific]
Impact: [What attacker gains]
Fix: [Exact code/config change]
Priority-ordered remediation plan at end.
Rules
🚨 Think like an attacker, not an auditor. Try to break things. 🚨 Lead with critical findings. Don't bury them under low-severity noise. 🚨 No false positives. Verify before reporting.