- Cylance Endpoint Security requirements
- Requirements: Cylance console
- Requirements: CylancePROTECT Desktop
- Requirements: CylanceOPTICS
- Requirements: CylancePERSONA Desktop
- Requirements: CylancePROTECT Mobile app
- Requirements: BlackBerry Connectivity Node
- Requirements: CylanceGATEWAY Connector
- Requirements: CylanceGATEWAY agents
- Cylance Endpoint Security network requirements
- Cylance Endpoint Security proxy requirements
- 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
- Prerequisites to install CylanceGATEWAY Connector to a Microsoft Azure environment
- Install the CylanceGATEWAY Connector to a Hyper-V 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
- Configure the CylanceGATEWAY Connector
- Managing 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
- 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
- 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 manually (Ubuntu and SUSE)
- Load and unload the kernel drivers
- Verify whether the kernel drivers are loaded
- Linux logging
- Re-register a Linux agent
- Start or stop the agent service on Linux
- Planning upgrades for older CylancePROTECT Desktop Linux agents
- Updating the Linux driver
- Require users to provide a password to remove the CylancePROTECT Desktop agent
- Setting up CylancePROTECT Mobile
- Setting up CylanceOPTICS
- Setting up CylancePERSONA Desktop
- Setting up CylanceGATEWAY
- Integrating Cylance Endpoint Security with Microsoft Intune to respond to mobile threats
- Managing 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
- Appendix: Best practices for deploying CylancePROTECT Desktop on Windows virtual machines
Appendix: Best practices for deploying CylancePROTECT Desktop on Windows virtual machines
CylancePROTECT Desktop
on Windows
virtual machinesYou can use
CylancePROTECT Desktop
to protect both physical and virtual machines. This section details the best practices for deploying the CylancePROTECT Desktop
agent on Windows
based virtual desktop infrastructure (VDI) workstations.CylancePROTECT Desktop
works well as a guest OS component because it is not IOPS or memory intensive on a per-guest basis. The preparation and deployment of the CylancePROTECT Desktop
agent in a virtual environment is similar to deployment on a physical computer. The deployment steps and best practices in this section will ensure that the agent performs efficiently in a virtual environment with fewer allocated resources and will help you to produce a gold image with no unsafe or abnormal files. After the gold image is thoroughly vetted, you can clone production VDI images from it.