Zscaler SSE Connectivity-as-a-Service

feature summary the new service capability facilitates resilient connectivity from nile service blocks to zscaler internet access (zia) service pops for customer selected segments this enables customers to enhance security posture and protect users, devices (it/iot/ot), and applications from internet based threats the connectivity as a service is fully automated with minimal configuration and elmiinates the operational burden of setting up and maintaining the service connectivity it also helps customers ensure uniform security policies across remote and on premise users enabling sse connectivity customers interested in forwarding nile service block traffic to zscaler zia first configure their zscaler account credentails this is necessary for enabling nsb to fully automate the discovery of the closest zscaler zen pops, provisioning of resilient secure connectivity to zscaler, and monitoring of the connectivity service, all without any further configuration the connectivity service is designed with resiliency built in, ensuring automated service recovery in the event of a failure the first step is configuring the zscaler account credentials so a secure connection to zscaler's apis can be established this can be done by going to global settings > integrations > setup integration with thrid party solutions > sse here you name the integration connector and identify zscaler as the provider as well as enter other account parameters as shown below once the zscaler account credentials are added, a test of the api can be performed using the test option, prior to saving the account configuration once zscaler api access is configured, customers can configure security policies that can selectively forward traffic from any network segment from the nile service block directly to the zscaler zia service this is accomplshed by going to global settings > access engine > create rule > create exteranl rule from there, administrators can select any segment for which traffic should be forwarded to zia, select all internet bound traffic, and then configure the forwarding behavior in the event that the zscaler zia service becomes unavailable finally, the administrator can specify whether this rule should be active or inactive when activated, any flows orginated from the identified segment(s) will be forwarded over the secured ipsec tunnel to zscaler zia resiliency in the connectivity as a service is automatically configured to automate recovery in the event of connectivity failure or service unavailability when completed, the forwarding rule shows up in the list of external rules and can be edited or deleted the edit action will open up a screen where the rule can be updated, as well as an option to view rule log to view the rules log, select the view rule log option and a view of a fitlered rule log will appear