Simplified Prisma Access Private App Connectivity
Avoid inefficient routing, incorrect transit hops, and SC-CAN bottlenecks with
enhanced Prisma® Access routing decisions.
One way to access a private app is by using a
service connection, also known as a
Service Connection-Corporate Access Node (SC-CAN). It can be difficult to connect to
private apps using service connections because:
- Indeterministic throughput of the private app due to SC-CAN bottlenecks.
- Latency due to incorrect transit hops.
- Operational complexity in deploying SC-CANs.
We enhanced the routing infrastructure, orchestrating additional routes to your
onboarded SC-CANs in the Prisma® Access internal network when required, eliminating
SC-CAN bottlenecks and preventing incorrect transit hops and inefficient
routing.
This design offers the following benefits:
- Routing setup that is easier to deploy.
- Easy initial setup.
- Deterministic 1 Gbps bandwidth from a given SC-CAN to the data center or
headquarters location where the private app is located.
