- 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
- Add CylancePROTECT Mobile app and CylanceGATEWAY users
- Adding user groups
- Add an authenticator
- Manage authentication policies for your tenant
- Create an authentication policy
- Assign policies to administrators, users, and groups
- 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
- Manage a device policy
- File action
- Memory Protection
- Protection settings
- Application control
- Agent settings
- Script control
- Device control
- 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
- Defining your private network
- Define network services
- Controlling network access
- Searching ACL rules and Network Services
- Using source IP pinning
- Configure CylanceGATEWAY service options
- Configuring threat detection and response settings
- 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
Application control is an optional setting that allows users to restrict any changes to executables on the device. Only applications that are on the device before application control is enabled are allowed to execute. Trying to add new applications or changing an existing application on the device will be denied.
The main objectives of application control are:
- Deny execution of executable files from remote or external drives.
- Deny creation of new executables on the local drive. See Using the Linux agent with application control for differences in the Linux agent.
- Deny changes to existing files on the local drive.
- Application control is typically used for fixed function devices that are not changed after setup (example: point-of-sale machines).
- Application control is available for Windows and Linux systems. Application control is not supported by the macOS agent.
- TheCylancePROTECT DesktopandCylanceOPTICSagent update process is disabled when application control is enabled.
- Trying to remove theCylancePROTECT DesktoporCylanceOPTICSagent will fail when application control is enabled.
- It is not recommended to runCylanceOPTICSon systems using application control. When application control is enabled,CylanceOPTICSwill not function properly due to the restrictive nature of application control.
To view application control activity, users can sign in to the console and click any device that is in a device policy with application control enabled. The Device Details page lists all actions relevant to application control under the Threats & Activities section.
- For Linux operating systems, application control uses the inventory system and only files in the inventory can execute. application control for Linux does not prevent a file from being created but does prevent inventoried files from being modified.
- If application control is enabled, functionality forCylanceOPTICSwill fail.
When you enable application control, the following recommended settings will be automatically applied:
To change any of these settings, go to the specified tab and clear the selected option.
Temporarily disables application control (when set to open) to allow editing and running new applications or to perform updates. This includes updating the agent. After performing the necessary changes, clear the Change Window check box to set it to closed.
Using the Change Window retains any changes made to the application control settings. Turning application control OFF and then back ON resets the Application Control settings back to default.
Folder Exclusions (Including Subfolders)
Specifies an absolute path to allow application changes and additions to the specified folders while application control is enabled (requires agent 1410 and higher).