Forum Discussion
F5 ASM | count violation
- Dec 15, 2020
Hi Abed AL-R,
You can use session tracking.
https://techdocs.f5.com/en-us/bigip-15-0-0/big-ip-asm-implementations/preventing-session-hijacking-and-tracking-user-sessions.html
Result after X violations in the last Y seconds:
Can this feature "Violation Detection Actions" work with XFF (if xff header is available)?
is it possible to configure in this feature to block xff header client ip and not the source ip ?
because sometimes source ip hides many users behind it
When Trust XFF Header option enabled, it blocks xff header value.
"Beginning in BIG-IP ASM 10.1.0, you can instruct the BIG-IP ASM system to trust the X-Forwarded-For header and use the IP address information in the HTTP header instead of the source IP of the packet if the BIG-IP ASM system is deployed behind an internal or other trusted proxy. You can enable this feature in the Configuration utility by selecting the Trust XFF Header check box in the security policy properties advanced configuration settings."
REF: https://support.f5.com/csp/article/K12264
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com