Bug Bounty Hunter Demonstrates Caido Workflows for Finding Vulnerabilities
· 1:17:12 · Watch on YouTube ↗
Summary
Bug bounty hunter Aram demonstrates Caido workflows for filtering traffic, analyzing JavaScript, testing WebSockets and organizing findings. He also discusses targeted AI assistance and its limitations.
Key points
- Aram demonstrates custom request and response views that pass selected traffic to other tools or an AI assistant for analysis.
- He uses passive workflows to flag and color requests containing test-account identifiers, creating leads for manual investigation while limiting background noise.
- He advises understanding community workflows before installing them, because resource-intensive passive workflows can process substantial traffic.
- A JavaScript analysis plugin identifies potential secrets, endpoints and other leads; WebSocket replay helps test messages and examine authorization behavior.
- Aram says broad autonomous AI testing did not find bugs in his experience, so he now favors narrowly scoped tasks and manual investigation.
- The resurface plugin tracks test strings that appear later in responses, while screenshot mode can redact tokens and highlight evidence for reports.
Article Details
- Topics
- [04:20] Custom request and response views for bug bounty testing
- [23:02] Passive workflows for identifying and organizing testing leads
- [35:10] Active workflows and external security tools
- [41:18] JavaScript analysis for security testing
- [45:51] WebSocket replay and authorization testing
- [50:00] Focused AI assistance and Shift agents
- [01:02:04] Target-specific plugin development
- [01:08:08] Tracking reflected test strings with resurface
- [01:11:55] Preparing and redacting report screenshots
