- 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 Azure 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
- Enroll the CylanceGATEWAY Connector with the BlackBerry Infrastructure
- View details for an enrolled CylanceGATEWAY Connector
- Configure the CylanceGATEWAY Connector
- Managing CylanceGATEWAY Connectors
- Update a CylanceGATEWAY Connector
- 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
- Define network services
- Controlling network access
- Configuring network protection
- Searching ACL rules and Network Services
- Using source IP pinning
- Configuring the Gateway service options
- Defining your private network
- Setting up CylanceAVERT
- Installing the CylanceAVERT agent
- Define sensitive content using information protection settings
- Managing information protection policies
- Integrating Cylance Endpoint Security with Microsoft Intune to respond to mobile threats
- Managing updates for the CylancePROTECT Desktop and CylanceOPTICS agents
- Appendix: Best practices for deploying CylancePROTECT Desktop on Windows virtual machines
- BlackBerry Docs
- Cylance Endpoint Security
- Setup
- Cylance Endpoint Security Setup Guide
- Setting up CylanceOPTICS
Setting up CylanceOPTICS
CylanceOPTICS
With
CylanceOPTICS
version 3.0 and later, the CylanceOPTICS
agent sends the device data that it collects to a centralized cloud architecture to be stored in a secure cloud database, rather than storing the data locally on the device. This new architecture makes CylanceOPTICS
cloud-enabled.
To manage this significant change for customers,
BlackBerry
is using the following approach to manage releases of the 3.x agent:
- For customers who have already contactedBlackBerryand had their tenant services migrated toCylanceOPTICS3.x, the latest 3.x version of the agent is available in theCylance Endpoint Securitymanagement console
- For customers who haveCylanceOPTICSagent 2.x and have not had their tenant services migrated toCylanceOPTICS3.x, contact yourBlackBerrySales representative (or use the Contact Sales form) to request the latest 3.x agent and the migration of tenant services to 3.x.
Agent version 2.5.x is still supported, but new features will require the latest 3.x agent. For more information about
CylanceOPTICS
agent 2.5.x, see the 2.5.x Administration Guide and Release Notes.
