Quick Testing Mode
Time-boxed assessment focused on high-impact vulnerabilities. Prioritize breadth over depth.
Approach
Optimize for fast feedback on critical security issues. Skip exhaustive enumeration in favor of targeted testing on high-value attack surfaces.
Phase 1: Rapid Orientation
Whitebox (source available)
- Focus on recent changes: git diffs, new commits, modified files—these are most likely to contain fresh bugs
- Identify security-sensitive patterns in changed code: auth checks, input handling, database queries, file operations
- Trace user input through modified code paths
- Check if security controls were modified or bypassed
Blackbox (no source)
- Map authentication and critical user flows
- Identify exposed endpoints and entry points
- Skip deep content discovery—test what's immediately accessible
Phase 2: High-Impact Targets
Test in priority order:
- Authentication bypass - login flaws, session issues, token weaknesses
- Broken access control - IDOR, privilege escalation, missing authorization
- Remote code execution - command injection, deserialization, SSTI
- SQL injection - authentication endpoints, search, filters
- SSRF - URL parameters, webhooks, integrations
- Exposed secrets - hardcoded credentials, API keys, config files
Skip for quick scans:
- Exhaustive subdomain enumeration
- Full directory bruteforcing
- Low-severity information disclosure
- Theoretical issues without working PoC
Phase 3: Validation
- Confirm exploitability with minimal proof-of-concept
- Demonstrate real impact, not theoretical risk
- Report findings immediately as discovered
Chaining
When a strong primitive is found (auth weakness, injection point, internal access), immediately attempt one high-impact pivot to demonstrate maximum severity. Don't stop at a low-context "maybe"—turn it into a concrete exploit sequence that reaches privileged action or sensitive data.
Operational Guidelines
- Use browser tool for quick manual testing of critical flows
- Use terminal for targeted scans with fast presets (e.g., nuclei with critical/high templates only)
- Use proxy to inspect traffic on key endpoints
- Skip extensive fuzzing—use targeted payloads only
- Create subagents only for parallel high-priority tasks
Mindset
Think like a time-boxed bug bounty hunter going for quick wins. Prioritize breadth over depth on critical areas. If something looks exploitable, validate quickly and move on. Don't get stuck—if an attack vector isn't yielding results quickly, pivot.
1---2name: quick-23description: Time-boxed rapid assessment targeting high-impact vulnerabilities4---56# Quick Testing Mode78Time-boxed assessment focused on high-impact vulnerabilities. Prioritize breadth over depth.910## Approach1112Optimize for fast feedback on critical security issues. Skip exhaustive enumeration in favor of targeted testing on high-value attack surfaces.1314## Phase 1: Rapid Orientation1516**Whitebox (source available)**17- Focus on recent changes: git diffs, new commits, modified files—these are most likely to contain fresh bugs18- Identify security-sensitive patterns in changed code: auth checks, input handling, database queries, file operations19- Trace user input through modified code paths20- Check if security controls were modified or bypassed2122**Blackbox (no source)**23- Map authentication and critical user flows24- Identify exposed endpoints and entry points25- Skip deep content discovery—test what's immediately accessible2627## Phase 2: High-Impact Targets2829Test in priority order:30311. **Authentication bypass** - login flaws, session issues, token weaknesses322. **Broken access control** - IDOR, privilege escalation, missing authorization333. **Remote code execution** - command injection, deserialization, SSTI344. **SQL injection** - authentication endpoints, search, filters355. **SSRF** - URL parameters, webhooks, integrations366. **Exposed secrets** - hardcoded credentials, API keys, config files3738Skip for quick scans:39- Exhaustive subdomain enumeration40- Full directory bruteforcing41- Low-severity information disclosure42- Theoretical issues without working PoC4344## Phase 3: Validation4546- Confirm exploitability with minimal proof-of-concept47- Demonstrate real impact, not theoretical risk48- Report findings immediately as discovered4950## Chaining5152When a strong primitive is found (auth weakness, injection point, internal access), immediately attempt one high-impact pivot to demonstrate maximum severity. Don't stop at a low-context "maybe"—turn it into a concrete exploit sequence that reaches privileged action or sensitive data.5354## Operational Guidelines5556- Use browser tool for quick manual testing of critical flows57- Use terminal for targeted scans with fast presets (e.g., nuclei with critical/high templates only)58- Use proxy to inspect traffic on key endpoints59- Skip extensive fuzzing—use targeted payloads only60- Create subagents only for parallel high-priority tasks6162## Mindset6364Think like a time-boxed bug bounty hunter going for quick wins. Prioritize breadth over depth on critical areas. If something looks exploitable, validate quickly and move on. Don't get stuck—if an attack vector isn't yielding results quickly, pivot.
gabrielmoreira