This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About korteke
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About korteke
07-01-2017
1Post
1Like
0Solutions
Jul 01, 2017Last Visited
User
Activity
User
Profile
Latest posts by korteke
| Subject | Views | Posted |
|---|---|---|
| 1995 | 06-28-2017 09:00 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 06-28-2017 09:00 AM |
User Badges
Community Statistics
| Member Since | 06-28-2017 08:36 AM |
| Date Last Visited | 07-01-2017 02:02 PM |
| Posts | 1 |
| Total Likes Received | 1 |
06-28-2017
09:00 AM
1 Kudo
Hi, ATM we have in our Global Restriction Settings Action == Notification. Is it possible to create new restriction policy and force that it is on prevention mode? I have searched all the places, but I just can't find any kind of button for that. Because if I create new " Execution path restriction" policy and put there restriction something like this "e:\testing\*.exe" I just get notification to ESM console (and this is of course how it should work). So basically the questions is "Can I override default behaviour?" Traps v. 4.0.xx
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-01-2017
02:02 PM
|
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks