Do You Need a WAF in Front of Keycloak?
A WAF in front of Keycloak buys you four things Keycloak cannot do for itself: it absorbs volumetric floods that would otherwise fill your network link, it rate-limits by IP address and path, it fences the admin paths to networks you name, and it scores clients that are not real browsers. It does not reduce what a single login costs your CPU, it cannot see a campaign spread thinly across thousands of addresses, and it cannot write a rule about which OAuth client or grant type a request is using, because on the token endpoint both of those live in the request body. So the honest answer to "do I need a WAF" is: if your login page is public, yes, and it covers about half of what you need. The other half is Keycloak configuration that no edge device can do for you.