- 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
- Configuring a new Cylance Endpoint Security tenant
- 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 and CylanceOPTICS agents
- 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
- Appendix: Using RMM solutions to install the Cylance agents on devices
- BlackBerry Docs
- Cylance Endpoint Security
- Setup
- Cylance Endpoint Security Setup Guide
- Setting up CylanceGATEWAY
- Connecting Cylance Endpoint Security to MDM solutions to verify whether devices are managed
Connecting Cylance Endpoint Security to MDM solutions to verify whether devices are managed
Cylance Endpoint Security
to MDM solutions to verify whether devices are managedYou can connect
Cylance Endpoint Security
to BlackBerry UEM
or Microsoft Intune
so that Cylance Endpoint Security
can verify whether iOS
and Android
devices are managed. Cylance Endpoint Security
can also verify whether Windows
devices are Intune managed.After you establish the connection to
UEM
, you configure the iOS
and Android
devices, users, and groups that the integration applies to. For UEM
, you ensure users are activated with a supported activation type and manage the distribution of the CylancePROTECT Mobile
app using the user and group management features available in the UEM
management console. Note that all
BlackBerry UEM
managed devices that you want to use this feature must have the CylancePROTECT Mobile
app deployed from the BlackBerry UEM
instance. For
Intune
integration, when you connect Cylance Endpoint Security
to Intune
, you create app configuration policies that define the device types and Intune user groups that the integration applies to. Note that all Intune managed devices that you want to use this feature must be included in an app configuration policy in the Cylance
console through Assests > User Groups. In the
Cylance
console, you create and assign the Gateway Service policy that allows Gateway to run only if the device is managed by BlackBerry UEM
or Intune
. When the user tries to access a network destination on an MDM-managed device, if the destination is allowed the network traffic is sent through the secure tunnel. To connect
Cylance Endpoint Security
to BlackBerry UEM
, perform the following actions.Step | Action |
---|---|
Review the prerequisites. | |
Link to your company directory.
| |
Install and configure the BlackBerry Connectivity Node .
| |
To connect
Cylance Endpoint Security
to Intune
, perform the following actions:Step | Action |
---|---|
Review the prerequisites. | |