This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
About nnayak2
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About nnayak2
07-26-2021
8Posts
0Likes
1Solution
Jul 26, 2021Last Visited
User
Activity
User
Profile
Latest posts by nnayak2
| Subject | Views | Posted |
|---|---|---|
| 2352 | 03-27-2015 10:09 AM | |
| 2354 | 03-26-2015 06:02 PM | |
| 8125 | 03-26-2015 05:49 PM |
User Badges
Community Statistics
| Member Since | 08-29-2014 11:45 AM |
| Date Last Visited | 07-26-2021 08:39 PM |
| Posts | 8 |
03-27-2015
10:09 AM
1. You can do this for a admin user from AD, as you can mention the source user as well as the source ip-address in the same security policy which I mentioned in my previous update. Here are the requirements for it - user identification needs to be enabled on untrust interface - AD needs to have the mapping of public ip-address and the user so that firewall can poll that information and map it to the security policy There can be some drawbacks too: - Firewall will try to talk to AD to resolve a name for any public ip-address coming on untrust interface. This is will be a very high process intensive and can also have lot of system logs of failed attempts 2. Firewall might not map a local admin user and its ip-address for access to the firewall itself. This can be a feature request which can be discussed with your account/sales team.
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-26-2021
08:39 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks