- Configuring a new Cylance Endpoint Security tenant
- 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
- Accessing the management console and configuring authentication
- Setting up administrators
- Setting up zones to manage CylancePROTECT Desktop and CylanceOPTICS
- Setting up CylancePROTECT Desktop
- Testing your CylancePROTECT Desktop deployment
- Create and manage a device policy
- 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 and CylanceOPTICS agents
- Setting up CylanceOPTICS
- Managing updates for the CylancePROTECT Desktop and CylanceOPTICS agents
- Best practices for deploying CylancePROTECT Desktop on Windows virtual machines
- Using RMM solutions to install the Cylance agents on devices
- Installing the BlackBerry Connectivity Node
- Linking to your company directory
- Adding users and devices
- Setting up CylancePROTECT Mobile
- 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 Entra ID environment
- Install the CylanceGATEWAY Connector to a Microsoft Entra ID 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 for the CylanceGATEWAY Connector
- Enroll the CylanceGATEWAY Connector with the BlackBerry Infrastructure
- View details for an enrolled CylanceGATEWAY Connector
- Configure the CylanceGATEWAY Connector
- Managing CylanceGATEWAY Connectors
- Manage CylanceGATEWAY Connectors
- Update a CylanceGATEWAY Connector
- UDP connectivity test responses
- 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
- Network Address Translation with CylanceGATEWAY
- Define network services
- Controlling network access
- Configuring network protection
- Searching ACL rules and Network Services
- Using source IP pinning
- Configuring the Gateway service options
- Gateway Service policy parameters
- Configure Gateway service options
- Specifying how devices activated with an EMM solution use the CylanceGATEWAY tunnel
- Specify which apps use CylanceGATEWAY on iOS devices
- Specify which apps use CylanceGATEWAY on iOS devices in a Microsoft Intune environment
- Specify CylanceGATEWAY options on Android Enterprise devices
- Specify CylanceGATEWAY options on Chromebook devices
- Specify CylanceGATEWAY options on Android Enterprise devices in your Microsoft Intune environment
- Connecting Cylance Endpoint Security to MDM solutions to verify whether devices are managed
- Installing the CylanceGATEWAY agent
- Defining your private network
- Enrolling CylancePROTECT Mobile and CylanceGATEWAY users
- Setting up CylanceAVERT
- Connecting Cylance Endpoint Security to external services
- BlackBerry Docs
- Cylance Endpoint Security
- Cylance Endpoint Security
- 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
agentsYou need to create zones with devices reserved for testing agent updates. You will associate these zones with the Test and Pilot update rules. You can add your own update rules for testing or for production deployment. For more information about creating zones, see Setting up zones to manage CylancePROTECT Desktop and CylanceOPTICS.
- 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.If you do not want to update the agent version on a device, use theDo not updatesetting. You must also make sure that the device is not in another zone with another update rule (including the Production rule) that specifies an update to the agent (auto-update or a specific version). If a device is in a zone with an update rule that specifies an update, it will be updated. If a device is associated with multiple update rules that specifies an update, the agent will be updated according to the rule with the highest rank.
- Select theAuto-Update Linux Drivercheck box to allow the agent to automatically update to the latest driver to support the latestLinuxkernel. The Auto-updateLinuxDriver feature requiresCylancePROTECT Desktopagent version 3.1.1000 or later and the agent driver version 3.1.1000 or later.
- ExpandCylanceOPTICSand select an update option.
- You can select Auto-Update only if you configured theCylancePROTECT Desktopagent to use Auto-Update.
- Automatic updates are not currently supported for theCylanceOPTICSagent forLinux.
- 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 are not in a zone with an update rule.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. The Production update rule is applied to devices that aren't in any zone with an update rule, and devices in zones where none of the rules have a specified an update to the agent.
- 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
- If memory protection, script control, and/or device control are enabled in the device policy, a reboot of the device following the agent installation or upgrade is recommended, but not strictly required. A reboot will ensure that any new policy settings have taken full effect.