Introduction to AI & Machine Learning - w/InsiderPhD @Bugcrowd

Uploaded August 2020 | Updated September 2026, 6 hours ago

We're often told that AI will or is changing cybersecurity, but what is AI anyway? This talk will teach you the basics of machine learning and data science, how to get started and what problems machine learning can and can't solve. If you've never done any AI before but you'd love to augment your existing practice with data, this is the talk for you.

Katie is a bug bounty hunter, educational YouTube and some how is finding the time to finish her PhD in Cyber Security and Machine Learning. A former data scientist turned cyber security person, who's been bug hunting since June 2019.

Recorded at #Levelup0x07 22 Aug, 2020.
Presented by Bugcrowd.
Follow Katie: twitter.com/InsiderPhd
Katie's YouTube: youtube.com/user/RapidBug
Sign up on Bugcrowd: bugcrowd.com
Join the conversation: discord.gg/TWr3Brs
Follow Bugcrowd: twittter.com/Bugcrowd

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