- 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
- Managing updates for the CylancePROTECT Desktop and CylanceOPTICS agents
- Manage updates for the CylancePROTECT Desktop and CylanceOPTICS agents
Manage updates for the CylancePROTECT Desktop and CylanceOPTICS agents
CylancePROTECT Desktop
and CylanceOPTICS
agentsCreate zones with devices reserved for testing agent updates. For more information about creating zones, see Setting up zones to manage CylancePROTECT Desktop and CylanceOPTICS. You will associate these zones with the Test and Pilot update rules. The Production update rule applies to all devices that do not belong to other update rules. You can add your own update rules for testing or for production deployment.
- In the management console, on the menu bar, clickSettings > Update.
- If necessary, create an update rule. For example, you can create a rule for testing agent updates.
- ClickAdd New Rule.
- Type a name for the rule.
- ClickSubmit.
- Click an update rule. For example, clickTest.
- ExpandZonesand select the zones that you want to assign to this update rule.
- ExpandAgentand select an update option.
- Select theAuto-Update Linux Drivercheck box to allow the agent to automatically update to the latest driver to support the latestLinuxkernel.
- ExpandCylanceOPTICSand select an update option.You can select Auto-Update only if you configured theCylancePROTECT Desktopagent to use Auto-Update.
- Repeat steps 2 to 7 for thePilotupdate rule, or a rule that you created for pilot testing.
- Repeat steps 2 to 7 for theProductionupdate rule, or a rule that you created for production. You don’t assign zones to the defaultProductionupdate rule because it applies to all devices that do not have any update rule assigned.If theCylancePROTECT Desktopagent is set to Auto-Update in the Production update rule, the Test and Pilot rules are not available. Update rules that you create are not affected by the configuration of the Production update rule.
- ClickSave.
- If you added update rules, click the arrows next to the rules to set the ranking. Rules at the top of the list take priority over rules lower on the list. The Test, Pilot, and Production rules are always at the bottom of the list and you cannot change their ranking.
- To trigger an update of theCylancePROTECT Desktopagent on a device before the hourly interval, on the device, right-click theCylancePROTECT Desktopicon in the system tray and clickCheck for Updates, restart the Cylance service, or run the following command from the Cylance directory:CylanceUI.exe–update