I did see the bandwidth was increased to 500Mbps, but wasn't aware that you could bundle them. Is that 500Mbps shared with multiple remote sites or each site gets 500Mbps? For example, in 1 state, I have 3 different physical locations, would those 3 locations be setup as remote networks and each of them gets 500Mbps or would those 3 share the 500?
the 500mb is assigned to the location and shared among all connected RN, so if one RN is using up 400Mbps, the others are left with 100Mbps
What about the scenario where the service connection is a site that also has users that require internet access? For example, I have a site with 1GB internet that would be considered a SC, since that's where internal resources would be. However, that same location also has roughly 200 users that would need access to the internet. In this scenario, would I have my HA pair of FWs be the service connection for Prisma but the users would have to egress locally, since the SC can't be used for internet access? If so, can I use the same 1GB link for both, or would it require a dedicated circuit for the SC?
A service connection does not allow access to the internet, so in the case of a hybrid site, you would have the SC connect your datacenter services, and either a local breakout for internet, or a second RN ipsec tunnel for internet connectivity. as long as you control your routing, both tunnels can live side by side
How would you segregate those additional zones? Behind the scenes the zones are only mapped to trust and untrust. So if TRUST1 and TRUST2 are mapped to Trusted zone it wouldn't make any difference if you used TRUST1, TRUST2 or even both as source zone for example.
those zones will only be used for logging and reporting purposes, but for enforcement you'll need to rely on User-ID and source/destination subnets. As all the RN and MU sit inside the 'trust' zone, any rule that translates to "from trust to trust allow" would allow all these to connect to eachother, so for your own sanity and visibility, refrain from creating more trust zones as they boil down to the same 'trust' at the security rule level. (for logging each RN automatically gets it's own source zone assigned, that is named exactly like the ipsec tunnel)
... View more