Forum Discussion
JustCooLpOOLe
Cirrocumulus
CirrocumulusADFS Proxy, APM, ASM Craziness
Hi,
We've been doing some testing recently with using the APM Proxy for ADFS which is basically a check box in the APM section of a virtual server that allows one to establish a trust with the ADFS backend servers for automagical certificate renewals.
What we are now adding on is an AWAF policy. I understand that APM comes before ASM when it comes to traffic processing order (https://support.f5.com/csp/article/K00363504). What we are experiencing in our testing, is that if we go to https://10.10.10.10/etc/passwd via cURL, an ASM event is not triggered for either "Host Header contains IP Address" or the attack signature "/etc/passwd" but rather a 404 response code.
When we add in https://10.10.10.10/adfs/ls/etc/passwd via cURL, a block event happens and we can view it in the ASM event logs. This to me indicates that the previous "/etc/passwd" doesn't even get processed by ASM and somehow, APM knows the URLs used by ADFS due to using the proxy setting on the virtual server and gives a 404 back, thus never even pushing to ASM.
I'm trying to look for some documentation on this functionality but can't seem to find anything. Does anyone know if there is documentation around the functionality fo the ADFS proxy with F5?
Any help is greatly appreciated!
Ah got it as it seems like some guided configs F5 is using an internal iApp LX based on node js to make this magic and probably 404 is configured there.
PeteWhiteEmployee
I've done some work on the ADFS Proxy but not with both that and ASM. What you are saying makes sense though - traffic is destined to APM ( rather than to a backend server, which is what ASM is more normally used for ) and APM translates them to the Microsoft ADFS proxy protocol. Have you looked at https://support.f5.com/csp/article/K13315545
JustCooLpOOLeHi Pete,
So what'eve we found is that once we add the /adfs to the URL, we get a 404 response code with no event logs for ASM. We believe that using the ADFS Proxy setting on a virtual server, the BIG-IP will allow anything with /adfs in the URL to be processed by ASM but if a request doesn't start with /adfs in the URL, it immediately gives a 404 response code. No iRules were in play to provide that.
While we're happy that APM is providing some sort of security, we get no logs out of this to send to our SIEM. We looked at that article so we're looking into it. We're onto another problem with version 15 not supporting ADFS 5.0.
- Nikoolayy1
MVP
It could be a url filter or layer 7 access list in the APM session policy or if there is a per-request policy. You can also enable APM HSM logging to try to see the APM logs that block this:
https://support.f5.com/csp/article/K45423041
See at the end of this link about HSM with APM:
ASM can use the APM session id for user session matching:
As your APM is before the ASM you can also place the ASM before the APM to protect the login page or webtop if you use those. But in this case maybe the session feature will not work as the APM will be after the ASM but still the ASM may track by username by the login page:
https://support.f5.com/csp/article/K13315545
https://support.f5.com/csp/article/K54217479