- Cylance Endpoint Security requirements
- Requirements: Cylance console
- Requirements: CylancePROTECT Desktop
- Requirements: CylanceOPTICS
- Requirements: CylancePROTECT Mobile app
- Requirements: BlackBerry Connectivity Node
- Requirements: CylanceGATEWAY Connector
- Requirements: CylanceGATEWAY agents
- Requirements: CylanceAVERT
- Cylance Endpoint Security network requirements
- Cylance Endpoint Security proxy requirements
- Logging in to the management console
- Installing the BlackBerry Connectivity Node
- Linking to your company directory
- Setting up administrators
- Adding users and devices
- Enrolling CylancePROTECT Mobile and CylanceGATEWAY users
- Setting up zones to manage CylancePROTECT Desktop and CylanceOPTICS
- Setting up CylancePROTECT Desktop
- Testing your CylancePROTECT Desktop deployment
- Using device policies to manage CylancePROTECT Desktop devices
- Installing the CylancePROTECT Desktop agent for Windows
- Installing the CylancePROTECT Desktop agent for macOS
- Installing the CylancePROTECT Desktop agent for Linux
- Require users to provide a password to remove the CylancePROTECT Desktop agent
- Setting up CylancePROTECT Mobile
- Setting up CylanceOPTICS
- Setting up CylanceGATEWAY
- Defining your private network
- Setting up the CylanceGATEWAY Connector
- Install the CylanceGATEWAY Connector to a vSphere environment
- Install the CylanceGATEWAY Connector to an ESXi environment
- Prerequisites to install CylanceGATEWAY Connector to a Microsoft Entra ID environment
- Install the CylanceGATEWAY Connector to a Microsoft Entra ID environment
- Install the CylanceGATEWAY Connector to a Hyper-V environment
- Install the CylanceGATEWAY Connector to an AWS environment
- Configure the CylanceGATEWAY Connector in the VM environment
- Access the CylanceGATEWAY Connector using OpenSSH
- Configure your firewall for the CylanceGATEWAY Connector
- Enroll the CylanceGATEWAY Connector with the BlackBerry Infrastructure
- View details for an enrolled CylanceGATEWAY Connector
- Configure the CylanceGATEWAY Connector
- Managing CylanceGATEWAY Connectors
- Manage CylanceGATEWAY Connectors
- Update a CylanceGATEWAY Connector
- UDP connectivity test responses
- Specify your private network
- Specify your private DNS
- Specify your DNS suffixes
- Specify private CylanceGATEWAY agent IP ranges
- Bring your own IP addresses (BYOIP)
- Setting up the CylanceGATEWAY Connector
- Network Address Translation with CylanceGATEWAY
- Define network services
- Controlling network access
- Configuring network protection
- Searching ACL rules and Network Services
- Using source IP pinning
- Configuring the Gateway service options
- Gateway Service policy parameters
- Configure Gateway service options
- Specifying how devices activated with an EMM solution use the CylanceGATEWAY tunnel
- Specify which apps use CylanceGATEWAY on iOS devices
- Specify which apps use CylanceGATEWAY on iOS devices in a Microsoft Intune environment
- Specify CylanceGATEWAY options on Android Enterprise devices
- Specify CylanceGATEWAY options on Chromebook devices
- Specify CylanceGATEWAY options on Android Enterprise devices in your Microsoft Intune environment
- Connecting Cylance Endpoint Security to MDM solutions to verify whether devices are managed
- Installing the CylanceGATEWAY agent
- Defining your private network
- Setting up CylanceAVERT
- Managing updates for the CylancePROTECT Desktop and CylanceOPTICS agents
- Connecting Cylance Endpoint Security to external services
- Appendix: Best practices for deploying CylancePROTECT Desktop on Windows virtual machines
Update a CylanceGATEWAY Connector
CylanceGATEWAY Connector
You can check whether an update for the
CylanceGATEWAY Connector
or update for the virtual machine OS is available.Verify the version of the
CylanceGATEWAY Connector
that is installed in the Cylance Endpoint Security
management console in Settings > Network > Private Network > Gateway Connectors. - Checkor themyAccountCylance Endpoint SecurityRelease Notes to see whether a new version of theCylanceGATEWAY Connectorsoftware is available and perform one of the following actions:
- If newCylanceGATEWAY Connectorsoftware is available, complete step 2 for your environment.
- If no newCylanceGATEWAY Connectorsoftware update is available, check for aLinuxOS update.
- Complete one of the following tasks:EnvironmentStepsUpdate theCylanceGATEWAY Connectorversion 2.9 or later.Use the DEB file to update the connector instance and to retain your configurations.
- Indownload the DEB version of the connector.myAccount
- Copy the DEB package to the connector that you want to upgrade. If SSH is enabled, you can use SCP to copy the DEB package from any host with SSH access to the connector. For instructions, see Access the CylanceGATEWAY Connector using OpenSSH. Otherwise, you can use SCP on the connector to copy the DEB package from any SSH-enabled host that can be reached by the connector.
- In the Unix console, typesudo apt install <.path>/cylance-gateway-connector-<version>.debFor example,sudo apt install /home/admin/cylance-gateway-connector-2.10.0.938.deb
- PressEnter.
Update theCylanceGATEWAY Connectorversion 2.8 or earlier or perform a complete reinstallation.Create a new instance of the connector for your environment. For instructions, see Setting up the CylanceGATEWAY Connector. - For anyCylanceGATEWAY ConnectorshowingReboot required to apply OS updates and security fixesin theStatuscolumn, restart the virtual machine to finish installing the OS update.
If the
CylanceGATEWAY Connector
is enrolled, but its tunnel is not connected to the BlackBerry Infrastructure
, you can initiate a connectivity test to verify whether the UDP packets that are sent from your private network have been received by the BlackBerry Infrastructure
and UDP packets that are sent from the BlackBerry Infrastructure
are received by your private network. At the login prompt of your environment (for example, vSphere
), type /var/lib/cylance-gateway/bin/udp-connectivity-test
. Press Enter
. You can run this command in any shell (for example, csh and bash). For more information about the connectivity results, see UDP connectivity test responses.