- 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
- Testing your CylancePROTECT Desktop deployment
Testing your CylancePROTECT Desktop deployment
CylancePROTECT Desktop
deploymentBefore you deploy the
CylancePROTECT Desktop
agent to your organization, you should test how it behaves with other applications in a test environment so that you can make sure that the applications that are used in your organization are allowed to run and working as expected. For example, if you discover that the agent blocks some applications such as custom-built apps or scripts from running or running properly, you can configure exclusions in your environment to allow them to do so.When you want to test the agent, install it on test systems that include applications that are used in your organization to make sure that it accurately represents the environment that you expect users to be using.
To test the agent, you do the following.
- Create test policies
- Create test zones
The testing process includes creating test device policies and test zones. Device policies contain the settings for the agent and tell it what to do when it encounters a threat. Zones help you group your systems by geographical location, business unit, operating system, or other group properties. Zone rules help automatically assign systems to a zone based on the criteria you set (for example, operating system, IP address range, and other criteria). You should test policies and zones to familiarize yourself with these features and to help you plan how to use these features in your organization.