Simplified Prisma Access Private App Connectivity
Learn how Prisma Access simplified private app connectivity using an anchor service
connection.
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
To solve this issue, Prisma Access has enhanced its 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 day zero setup
- Deterministic 1 Gbps bandwidth from a given SC-CAN to the data center or
headquarters location where the private app is located
