- 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
UDP connectivity test responses
The following examples show the outputs that might be displayed when you verify the UDP path between the
CylanceGATEWAY Connector
and the BlackBerry Infrastructure
. In the following examples,
- "Endpoint" is the IP address and port of the udp-connectivity-test that is being tested.
- "Client Address:Port" is the external IP address and port of theCylanceGATEWAY Connectoras seen by theBlackBerry Infrastructure.
- "Server" is theBlackBerry Infrastructure.
Example: UDP traffic is successfully sent and received
In this example, the UDP traffic is successfully sent and receive between the connector in your private network and the
BlackBerry Infrastructure
.
Initiating discovery request Starting connectivity test using endpoint=<IP address>:<port> Sent hello message with id='62f6bf9e-741c-4f22-9907-2725789aa318' to <IP address>:<port> Waiting for server hello Received server hello with id='62f6bf9e-741c-4f22-9907-2725789aa318' from <IP address>:<port> Sent ack message with id='62f6bf9e-741c-4f22-9907-2725789aa318' to <IP address>:<port> Report: Client Address:Port = <IP address>:<port> Packet Size = 1500 Fragmented = false RTT = 3ms
Example: The outbound UDP traffic is blocked.
In this example, the UDP connectivity test client was able to send the client hello, but the
BlackBerry Infrastructure
did not receive the response within the timeout period.
Initiating discovery request Starting connectivity test using endpoint=<IP address>:<port> Sent hello message with id='2dca5fcf-3f9a-46c3-a158-911a851f94a7' to <IP address>:<port> Waiting for server hello Error: Timeout on receiving server hello Getting test report from server Error: The server did not receive our hello message. Is outbound UDP blocked? Starting connectivity test using endpoint=<IP address>:<port> Sent hello message with id='40fe1e15-b2c0-4607-9880-7be08ec505ac' to <IP address>:<port> Waiting for server hello Error: Timeout on receiving server hello Getting test report from server Error: The server did not receive our hello message. Is outbound UDP blocked? Error: No endpoints to test
Example: The inbound UDP traffic is blocked.
In this example, the UDP connectivity test client sent the UDP connectivity test client hello and the
BlackBerry Infrastructure
received it and replied, but the test client did not receive the response within the timeout period.
Initiating discovery request Starting connectivity test using endpoint=<IP address>:<port> Sent hello message with id='973e0d45-71f0-427b-be08-9e5f16d03349' to <IP address>:<port> Waiting for server hello Error: Timeout on receiving server hello Getting test report from server Error: The server sent a response that was not received. Is inbound UDP blocked? Starting connectivity test using endpoint=99.83.155.194:58255 Sent hello message with id='2fc6d3f8-43c2-4707-bc77-e85168c2596e' to <IP address>:<port> Waiting for server hello Error: Timeout on receiving server hello Getting test report from server Error: The server sent a response that was not received. Is inbound UDP blocked? Error: No endpoints to test