- Cylance Endpoint Security requirements
- Requirements: Cylance console
- Requirements: CylancePROTECT Desktop
- Requirements: CylanceOPTICS
- Requirements: CylancePERSONA Desktop
- Requirements: BlackBerry Protect app
- Requirements: BlackBerry Connectivity Node
- Requirements: CylanceGATEWAY Connector
- Cylance Endpoint Security network requirements
- Cylance Endpoint Security proxy requirements
- Testing your CylancePROTECT Desktop deployment
- Logging in to the management console
- Setting up the CylanceGATEWAY Connector
- Install the CylanceGATEWAY Connector to a vSphere environment
- Install the CylanceGATEWAY Connector to an ESXi environment
- Configure the CylanceGATEWAY Connector in the vSphere and ESXi environment
- Configure your firewall
- Enroll the CylanceGATEWAY Connector with the BlackBerry Infrastructure
- Configure the CylanceGATEWAY Connector
- Manage CylanceGATEWAY Connectors
- Update a CylanceGATEWAY Connector
- 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, CylanceOPTICS, and CylancePERSONA Desktop devices
- Setting up CylancePROTECT Desktop
- Device policy
- Installing the CylancePROTECT Desktop agent for Windows
- Installing the CylancePROTECT Desktop and CylanceOPTICS agents for Windows
- Installing the CylancePROTECT Desktop agent for macOS
- Installing the CylancePROTECT Desktop agent for Linux
- Linux installation prerequisites
- Linux agent installation package
- Install the RHEL/CentOS agent automatically
- Install the RHEL/CentOS agent manually
- Install the Ubuntu agent manually
- Install the Amazon agent automatically
- Install the Amazon agent manually
- Amazon Linux commands
- Install the SUSE agent automatically
- Install the SUSE agent manually
- Install the Debian agent manually
- Install the Oracle agent automatically
- Install the Oracle agent manually
- Start the UI (Ubuntu and SUSE 12)
- Load the kernel driver
- Verify whether the kernel driver is loaded
- Linux logging
- Re-register a Linux agent
- Start or stop the agent service on Linux
- Planning upgrades for older CylancePROTECT Desktop Linux agents
- Upgrading the Linux driver
- Uninstalling the Linux agent
- Device lifecycle management
- Setting up CylancePROTECT Mobile
- Setting up CylanceOPTICS
- Setting up CylancePERSONA Desktop
- Setting up CylanceGATEWAY
- Integrating Cylance Endpoint Security with MDM solutions to respond to mobile threats
- Manage updates for the CylancePROTECT Desktop, CylanceOPTICS, and CylancePERSONA Desktop agents
- Appendix: Best practices for deploying CylancePROTECT Desktop on Windows virtual machines
- BlackBerry Docs
- Cylance Endpoint Security
- Setup
- Cylance Endpoint Security Setup Guide
- Integrating Cylance Endpoint Security with MDM solutions to respond to mobile threats
Integrating Cylance Endpoint Security with MDM solutions to respond to mobile threats
Cylance Endpoint Security
with MDM solutions to respond to mobile threatsYou can connect
Cylance Endpoint Security
to Microsoft Intune
so that Cylance Endpoint Security
can report the risk level of devices to Intune
. The device risk level is calculated based on the detection of mobile threats by the BlackBerry Protect
app on Intune
managed devices. Intune
can execute mitigation actions based on the device risk level.When you connect
Cylance Endpoint Security
to Intune
, you create app configuration policies that define the device types and Intune
groups that the integration applies to. You create and assign risk assessment policies that map events detected by the BlackBerry Protect
app to the risk level of your choosing (high, medium, or low). When the BlackBerry Protect
app on an Intune
managed device detects a threat (for example, a malicious app or sideloaded app), the risk level that is mapped to that threat is factored into an overall risk level that Cylance Endpoint Security
calculates for the device. Cylance Endpoint Security
reports the device risk level to Intune
, and Intune
carries out the mitigation actions that have been configured for that risk level.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. This feature requires the BlackBerry Protect
app version 2.0.1.1099 or later.