Updated 12/19/2012 • Originally posted on 19-Dec-2012 by
Straight from the manual, yo:
Source IP-Based Client-Side Integrity Defense
What actually happens when a client is found to be non-human? My guess is that the ASM attempts to sort out what's a "good" connection from what's a "bad" connection, where bad means "script", but I'd like a definitive description.
How does this interact with the 'Operation Mode' settings? Does choosing 'Transparent' override the Prevention Policy settings, limiting the ASM to reporting on the DoS attacks?
If anyone has actually tested the combinations of Operation Mode and Prevention Policy settings, I would love to hear what you found.
Thanks in advance,