r/Information_Security • u/Life-Hour217 • 10m ago
How do you handle WAF inspection when the app layer payload is fully encrypted (app-level or end-to-end encryption on top of TLS)?
Looking for some real-world experience from security and platform teams and folks.
We're seeing more dev teams encrypt the entire application-layer payload (request and response bodies, in web as well as in APIs) beyond standard TLS. The WAF terminates TLS, but what it sees is an opaque blob, so signature rules, SQLi/XSS detection, and schema validation have nothing to inspect when it comes to the request and response body part!
For those who've dealt with this:
Do you allow it, restrict it, or push back on it?
Where do you inspect: decrypt at the gateway or reverse proxy, share keys with the WAF, or decrypt inside the app and inspect after?
What compensating controls do you rely on (API gateway validation, RASP, behavioral and rate analysis, strict schema enforcement, runtime monitoring)?
How do you handle the tension with dev teams who see this as a privacy or security feature?
Interested in what's actually working in production, and what didn't. Thanks!