Updating theCloud Services plugininPrisma Accessdoes not disrupt existing traffic flows because the upgrade process is designed to beseamless and transparent. Prisma Access ensures high availability by maintainingactive sessions and policieswhile applying the update in the background. This allows ongoing connections to continue without interruptions, minimizing impact on user experience.

After configuringdomain-based split tunnelingforzoom.us, the expected behavior can be confirmed by checking therouting table on the client machine. If split tunneling is correctly configured, the traffic forzoom.usshould be routedoutsidethe GlobalProtect VPN tunnel, while other traffic follows the tunnel path. Reviewing the routing table ensures thatonly the intended traffic is excluded from the tunnel, confirming that the split tunnel configuration is working as expected.

When onboarding a discovered application forZTNA Connector, configuring aTCP pingallows Prisma Access to accurately report the application'savailability.TCP ping(also known as aTCP connection check) verifies whether the application's service port isopen and responsive, ensuring that the application is reachable before allowing user connections. This method is more reliable thanICMP ping, as many cloud and SaaS applicationsblock ICMP trafficfor security reasons.

TheCloud Dynamic User Groupcapability inCloud Identity Engineenables the creation ofSecurity policiesthat useEntra ID (formerly Azure AD) attributesfor user identification. This allows PrismaAccess to dynamically applyuser-based security rulesbased onreal-time Entra ID attributes, ensuring that access policies adapt to user changes such asgroup membership, device compliance, or role updates.

Strata Copilotenhances the capabilities ofPrisma Access security teamsby providingAI-powered insights and recommendationsto help resolve security issues efficiently. It analyzessecurity events, misconfigurations, and alertsand offerscontextual guidancewithrecommended next stepsfor troubleshooting and improving security posture. This assists teams inquickly identifying and addressing security challengeswithout requiring deep manual investigation.

When implementingAI Access Security,tagsare applied toGenerative AI applicationsto classify them assanctioned, tolerated, or unsanctioned. This allows organizations to enforcepolicy-based access controlover AI tools, ensuring that onlyapproved applicationsare accessible while restricting or monitoring usage ofuntrusted or high-risk AI platforms. This classification helps security teamsmanage AI-related risks and complianceeffectively.

SincePhase 1 of the IPSec tunnel is establishedbutPhase 2 traffic is not being received, theTunnel logsinStrata Logging Serviceshould be reviewed.Tunnel logsprovide visibility into IPSec tunnel establishment,Phase 2 negotiation, and any errors or dropped packets related to encrypted traffic. This will help identify whetherESP (Encapsulating Security Payload) traffic is being blocked, mismatched security associations (SAs) exist, or if there are other issues with Prisma Access responding to Phase 2-encrypted packets.

TheBGP peernot coming up despite anestablished IPSec tunnelindicates a potentialBGP configuration issue.

Secret– IfMD5 authenticationis configured for BGP, both Prisma Access and theCustomer Premises Equipment (CPE)must have thesame secret (authentication key). A mismatch will prevent BGP from establishing a session.

Peer AS Number– TheAutonomous System (AS) numberof the BGP peer must match what is expected on both sides of the connection. If the AS number is incorrect, the BGP session will fail to establish.

By verifying these elements, the engineer can troubleshoot and establish a successfulBGP peering sessionover theIPSec tunnel.

InPrisma Access, configuring anotification profileallows engineers to receive alerts when IPSec tunnels experience downtime or instability. By definingspecific conditions for remote network IPSec tunnels, the notification profile ensures that the engineer is proactively informed abouttunnel failures, flapping, or degraded performance. This approach enables timely troubleshooting and minimizes disruptions for users relying on the IPSec tunnels.

For complete data visibility inPrisma Access (Managed by Panorama),log forwarding profilesmust be applied toall security policiesto ensure that traffic logs are correctly sent toStrata Logging Service. If log forwarding is missing or misconfigured, some traffic data may not appear in theApplication Command Center (ACC), leading to incomplete insights. Verifying and correctly assigning log forwarding ensures that all relevant network activity is captured and available for analysis.

In Prisma Access's default routing mode, the service connections establish BGP sessions with the customer premises equipment (CPE) in the data centers. To ensure traffic destined for mobile users in a specific region (e.g., North America) traverses the service connection in that same region, you need to control the route advertisements.

Filtering out the mobile user pool prefixes from the other region on each service connection achieves this by:

Preventing the data center in one region from learning the specific mobile user prefixes of the other region.For example, the North American service connection would filter out the mobile user pool prefixes allocated to European users.

Ensuring that when a data center needs to send traffic to a mobile user, it will only see and use the route advertised by the service connection in the appropriate geographical region.This forces the traffic to enter the Prisma Access infrastructure through the intended regional service connection.

Let's analyze why the other options are incorrect based on official documentation regarding default routing mode:

A. Configure BGP on the customer premises equipment (CPE) to prefer the assigned community string attribute on the mobile user prefixes in its respective Prisma Access region.While BGP communities can be used for influencing routing decisions, in the context ofdefault routing modeand ensuring regional traffic flow, relying solely on the CPE to prefer community strings might not be the most robust or direct method to guarantee traffic traverses the correct regional service connection. The service connection itself needs to control the advertisement of prefixes.

C. Configure BGP on the customer premises equipment (CPE) to prefer the MED attribute on the mobile user prefixes in its respective Prisma Access region.The BGP MED (Multi-Exit Discriminator) attribute is primarily used to influence the path selectionbetweenautonomous systems (AS) or within the same AS at different entry points. In this scenario, where serviceconnections are advertising prefixes, filtering at the source (service connection) is a more direct and reliable way to ensure regional traffic flow than relying on the MED attribute on the CPE.

D. Configure each service connection to prepend the BGP ASN five times for mobile user pool prefixes originating from the other region.BGP AS path prepending is a mechanism to make a path less desirable. While this could influence routing, it doesn't guarantee that traffic will always take the intended regional path. Filtering provides a more definitive control over which routes are advertised and learned.

Therefore, configuring each service connection to filter out the mobile user pool prefixes from the other region in the advertisements to the data center is the verified method to ensure traffic destined for mobile users traverses the service connection in the appropriate region when using Prisma Access in default routing mode.

Updating theCloud Services plugininPrisma Accessdoes not disrupt existing traffic flows because the upgrade process is designed to beseamless and transparent. Prisma Access ensures high availability by maintainingactive sessions and policieswhile applying the update in the background. This allows ongoing connections to continue without interruptions, minimizing impact on user experience.