WAF Made Easy
summary
A reproducible method claims deployment of 30 WAFs in under one quarter using a build‑tune‑support pipeline: plan with an implementation guide, cold‑build virtual WAFs (snapshots before changes), use DNS‑based traffic interception and host‑file redirection for tuning, run daily tuning meetings until alerts drop, then flip to block on a bridge call and hold one week of hypercare. Architecture notes: management on an internal VLAN, restrict web servers to WAF IPs, consider TLS offload to a packet aggregator and parent/child policies for feature differences.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:23Presentation Agenda
- 0:51What is a WAF?
- 3:45Build, Tune, & Support
- 4:31Biggest Challenges
- 6:33Team WAF
- 7:23Team Application
- 8:53Build Phase: Architecture
- 10:22Build Phase: Plan Design
- 12:00Build Phase: Cold Build
- 12:48Build Phase: Put inline
- 14:45Tune Phase: Initial Tuning
- 16:26Tune Phase: Enter Blocking mode
- 17:51Support Phase: Business as Normal
- 18:31On Premises: Considerations
- 20:14Cloud: Considerations
- 21:51Cloud: Single Containers
- 22:35Cloud: Multiple Containers
- 23:09One Policy to Rule Them all?
- 25:37Policy Push Questions
- 27:19WAF "Apply" Slide
- 28:34I would love to continue the conversation
related talks
43mMaking WAF Mainstream: From Static Defenses to... (Roy Weisfeld, Surya Pentakota)
27mSecuring Applications and Managing WAFs at a large scale
33mWAFs FTW! A modern devops approach to security testing your WAF
42mDon’t use a WAF, and when you should, anyway.
46mIt is rough without a WAF
41mAutoScaling Web Application Security in the Cloud
16mAutomating AWS WAF: Pioneering future security
15mBuilding a secure perimeter with AWS WAF