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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About Goran_A
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- LIVEcommunity
- About Goran_A
10-27-2020
1Post
0Likes
0Solutions
Oct 27, 2020Last Visited
User
Activity
User
Profile
Latest posts by Goran_A
| Subject | Views | Posted |
|---|---|---|
| 1123 | 09-30-2020 07:13 PM |
User Badges
Community Statistics
| Member Since | 03-25-2020 09:12 PM |
| Date Last Visited | 10-27-2020 08:52 PM |
| Posts | 1 |
09-30-2020
07:13 PM
Hi all, must be someone had similar thoughts too, we have a customer who'd like to secure outgoing traffic, by specifying not only applications, but also restrict destination FQDN-s and/or IP ranges. Issue with Microsoft is that their FQDN-s, and moreover IP public ranges, change monthly. I was just wandering if there is a smart way to address this issue? Is there any feature in roadmap, possibly getting a pre-defined range for Microsoft, that gets dynamically updated, just like country IP ranges? Thanks, Alex
... View more
LEGAL NOTICES
Copyright 2007 - 2022 - Palo Alto Networks