Cloud Exchange System Requirements

The Netskope CE platform needs access to GitHub, Docker Hub, a Netskope tenant, partner’s platforms, and the other 3rd-party platforms that you wish to integrate with. Do evaluate network configurations, like HTTP Proxy setup, Firewall rules, etc., to ensure the connectivity is available.

Here is the list of Public URLs that CE needs. While the setup script will check for all of these, it will not successfully complete installing CE unless these requirements are met. Firewalls, web proxies, gateways, and routers must be configured to allow CE to communicate with multiple services as described below.

For fetching third party plugins, confirm the system has access to:

For fetching alerts and events from Netskope tenant, confirm the system has access to:

For pulling docker images from Docker Hub (connectivity to additional hosts may be required since the docker images will be behind a CDN), confirm the system has access to:

If you are behind an HTTP or HTTPS proxy server, for example in corporate settings, you need to add the proxy configuration in the Docker systemd service file. Refer to https://docs.docker.com/config/daemon/systemd/#httphttps-proxy for details.

Refer to Required Network Connectivity for 3rd-Party Plugins for additional network connectivity requirements based on the plugins.

For extracting web transaction event streaming logs, confirm connectivity to us-west1-pubsublite.googleapis.com (for US customers) and europe-west3-pubsublite.googleapis.com (for EU customers). Alternatively, ensure Cloud Exchange can access *.googleapis.com (wildcard).

To provide analytics details, like version of the Cloud exchange and plugins to the Netskope team for the better performance, confirm connectivity to https://reporting.netskope.tech/.

For connectivity to Cloud Exchange, ensure that the administrator can access the command line interface for Cloud Exchange via SSH (port 22)

For browser and API-based connectivity to Cloud Exchange, ensure users have access to Cloud Exchange via port 80 or 443 (by default) or via any alternative, non-standard port (recommended) configured during the setup.

The user running the setup script should have at least the following permissions:

Below are the prerequisites required for setting up Cloud Exchange on Linux distributions other than Red Hat.

Podman is a prerequisite to installing the Cloud Exchange platform on Red Hat Enterprise Linux (RHEL). Ensure these commands are available:

This section provides recommendations and guidance for selecting the memory/storage/CPU based on the expected volume. Factors include:

This table shows recommendations for standard deployments:

This table shows the maximum number of indicators supported by the Threat Exchange module.

This table shows the number of alerts and events pulled and ingested at one destination by Log shipper module.

This table shows the number of alerts and events pulled and ingested on one destination by Log shipper module for WebTx.

This table shows the number of credits used by the Cloud Exchange modules and the WebTx plugins.

Above Average Load Design Assumptions

Your numbers may differ.