Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Get Started
- News & Events
- Collaboration
- Education Services
- Technologies
- Next-Generation Firewall
- GlobalProtect
- Threat Prevention Services
- Endpoint Protection
- SSL Decryption
- 5G
- IoT Security
- Prisma SD-WAN
Network Security
- Prisma Access
- Prisma SaaS
- Prisma Cloud
- CN-Series
- VM-Series:
- Alibaba
- AWS
- GCP
- Azure
Cloud Security
- Cortex XDR
- Cortex XSOAR
- Cortex Data Lake
Security Operations
- Resources
- COVID-19 Response Center
- LIVEcommunity
- ›
- About Goran_A
About Goran_A
Announcements
Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
10-27-2020
1Post
0Likes
0Solutions
Oct 27, 2020Last Visited
User
Activity
User
Profile
Latest posts by Goran_A
| Subject | Views | Posted |
|---|---|---|
| 359 | 09-30-2020 07:13 PM |
User Badges
Public Statistics
| Date Registered | 03-25-2020 09:12 PM |
| Date Last Visited | 10-27-2020 08:52 PM |
| Total Messages Posted | 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
Latest Blogs
Latest Posts
Copyright 2007 - 2021 - Palo Alto Networks
