Penetration Testing & Red Teaming for Healthcare
summary
Claims a real red‑team engagement inside a European hospital where attackers use USB drop and network plugging to get an IP, run port scans and sniffing, and find cross‑site scripting plus a slow HTTP DoS that knocks out a remote access portal. Reports one username/password recovered after brute forcing and monitoring that never raised alerts. Describes tooling (scanners, sniffers, DoS scripts), scope controls (NDA/waiver/whitelisting), and that findings provoke remediation requests and a follow‑up retest.
AI-written summary · about
chapters (23)
- 0:00Penetration testing & red teaming intro
- 1:07Agenda & speaker intro
- 2:14Speaker background
- 3:19Disclaimer & purpose
- 4:04Cybersecurity terms
- 6:35Penetration testing basics
- 8:23Types of penetration tests
- 10:10Red teaming objectives
- 13:03Pre-test preparation
- 15:07Blackbox vs graybox vs whitebox
- 16:57Network, web, cloud testing
- 18:00Scheduling & access
- 20:55Legal approvals & NDAs
- 23:26Formal approval importance
- 24:07Penetration tester’s day
- 27:21Cryptography testing approach
- 28:50Vuln management vs pentesting
- 29:55Red vs blue vs purple teaming
- 32:02Healthcare compliance & infra
- 33:49Red teaming case study
- 40:54Becoming a red teamer
- 42:19Cybersecurity learning tips
- 44:50Q&A on access controls
related talks
19mPenetration Testing
54mHacked in hours: Red team assessments unveiling vulnerabilities
13mFreedom of Security
12mIntroduction To Red Team Tooling And Opsec
42mRed vs. Bank: Surviving a Three Year Red Team
51mOrion's Quest: Modern Pentesting
34mPurple Team Strategies for Application Security
51mHacker’s Perspective on Your Infrastructure: Lessons from the Field