Hacking Your Resumé - w/Ricki Burke (@cybersecricki) @Bugcrowd

Uploaded May 2020 | Updated September 2026, 54 minutes ago

One of the most frequent questions for infosec newbies, how do you hack into the industry? Ricki is a noteworthy infosec recruiter from Melbourne, Australia. He will be sharing his best tips on how to create a resume that stands out from the crowd, and some pro career tips to give you the best chances of landing your dream role in infosec.

Bio:
The infosec recruiter - Ricki (@cybersecricki) is founder of CyberSec People, where the team support fast-growing organisations around the world in hiring in-demand cybersecurity talent.

Ricki is heavily involved in the security community by attending and presenting at various cons, hosting the Hacking Into Security podcast, a mentoring program and more.

Recorded at #levelup0x06 9 May, 2020.
Presented by Bugcrowd.
Join the conversation https://discord.levelup.sh.
Follow Ricki: twitter.com/@cybersecricki

Hacking Your Resumé - w/Ricki Burke (@cybersecricki)

Introduction to AI & Machine Learning - w/InsiderPhD

Why I ❤️ Offensive Work and Why I 💔 Offensive Work - w/Thomas Dullien (@halvarflake)

$What are WebSockets? Unlike standard HTTP where every request needs a response, WebSockets create a persistent, bi-directional communication channel. Once opened, data flows freely in both directions without the heavy overhead of HTTP headers. Its the backbone of real-time chat apps, live gaming, and trading platforms. ⚙️ How it works: The magic starts with a standard HTTP handshake. The client sends a GET request with the headers Connection: Upgrade and Upgrade: websocket. If the server agrees, it responds with an HTTP 101 Switching Protocols status code. The connection stays open, and the protocol shifts from http:// to ws:// (or wss:// if encrypted via TLS). 🤝 💰 Why its a bug bounty goldmine: Devs often authenticate the initial handshake but forget to authorize the actual messages being passed back and forth. Opening windows for bug hunters. Traditional WAFs struggle to inspect persistent binary or custom-framed WS traffic. It’s essentially a dark tunnel straight to the backend logic, serving as a WAF bypass. 🏁 Top vulnerabilities: 1️⃣ CSWSH (Cross-Site WebSocket Hijacking): If the server relies solely on cookies for the handshake and ignores the Origin header, attackers can trick a victims browser into opening a WS connection and stealing their data. 2️⃣ IDOR & Unauth Access: Sending API commands (like {user_id: 1337, action: delete}) via WS without session validation. 3️⃣ Injection (XSS/SQLi): Dropping blind payloads into the WS stream that execute on an internal admin dashboard. 🛠️ Toolkit: You cant hack what you cant see. Here’s the toolkit to enhance your hunting: 👇 1. Burp Suite: The WebSockets History tab and Repeater are your best friends. Intercept, modify, and drop frames. 2. STEWS: A lethal tool for automated WS endpoint discovery and vulnerability fingerprinting. 3. Wscat: Perfect for quick, lightweight CLI testing and raw connection probing. 🔖 Save this for later and bag those P1s.$

Bugcrowds VRT: with Katie Paxton-Fear and Codingo

Bugcrowd Security Flash - The Kaseya REvil Attack Explained

How a Hacker Uses the Bugcrowd Platform with Brandon Reynolds

Bugcrowd Security Flash: The HackLore Project

Frontier AI teams are leveling up their models with Bugcrowd’s new RLE