I'm trying to add additional protection for users accessing resources on an isolated network. Is there any way that I can utilize our Palo Alto's to accomplish this scenario?
We do use global protect and user-id mapping already, but as an example I would like John while on his laptop\pc that whenever he access lets call it ServerA over RDP that he has to do some sort of additional step to gain access into that network\destination. Possibly use some sort of multi-factor authentication or something similar?
I'm more so looking to "fort knox" style access to a backend resource the best I can utilizing the Palo Alto's. If it's a little difficult for this subset of end users I am ok with it. I just really want to ensure a user is who they are when they go to access the resource. I do have it working, however it seems to only work for http\https requests, if I initiate a RDP session to the same server the traffic never leaves the laptop. But if I successfully sign into captive portal first and then launch the RDP to the same server then I am able to connect via RDP.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!