Forum Discussion
IT_Support_-_EC
Nimbostratus
Jul 12, 2015[BIG-IP 4000s] Failed to protect Crosse-Site Request Forgery
Dear F5 Team,
Our team did PoC of Cross-Site Request Forgery but it seemed
that WAF cannot protect this attack. Our team said
"For the CSRF protection, F5 will generate its own Javascript t...
boneyard
MVP
Jul 14, 2015i would personally, certainly in a PoC, enable all three options in the blocking section for CSRF.
i checked in my lab, get the same situation with the comment on the script blocks but it works fine.
where exactly is the token expected where i doesn't show? remember there are cases where it isn't added specially in dynamically generated code.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects