Quick Testing Mode

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
• Read existing wiki notes first (list_notes(category="wiki") then get_note(note_id=...)) to avoid remapping from scratch
• Run a fast static triage on changed files first (semgrep, then targeted sg queries)
• Run at least one lightweight AST pass (sg or Tree-sitter) so structural mapping is not skipped
• Keep AST commands tightly scoped to changed or high-risk paths; avoid broad repository-wide pattern dumps
• Run quick secret and dependency checks (gitleaks, trufflehog, trivy fs) scoped to changed areas when possible
• 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
• Before completion, update the shared repo wiki with what changed and what needs dynamic follow-up

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:

1. Authentication bypass - login flaws, session issues, token weaknesses
2. Broken access control - IDOR, privilege escalation, missing authorization
3. Remote code execution - command injection, deserialization, SSTI
4. SQL injection - authentication endpoints, search, filters
5. SSRF - URL parameters, webhooks, integrations
6. Exposed secrets - hardcoded credentials, API keys, config files

Skip for quick scans:

• Exhaustive subdomain enumeration