- 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
macOS installation parameters
CylancePROTECT Desktopagent can be installed using command line options in the terminal. The examples below use the .pkg installer. If you are using the .dmg installer, change the file extension in the command. Before you begin, ensure that the target endpoints meet system requirements.
The installation token is required when you install the agent. You can find it in the management console by clicking
Settings > Application.
This parameter hides the system tray at startup.
1 or 2
1: This value only allows local administrators to make changes to the registry and services.
2: This value only allows the system administrator to make changes to the registry and services.
If no value is specified, the default value is 2.
0, 1, 2, or 3
0: This value indicates that only error messages are logged.
1:This value indicates that error and warning messages are logged.
2: This value indicates that error, warning, and information messages are logged.
3: This value enables verbose logging, where all messages are logged. Note that verbose log file sizes can grow very large.
BlackBerryrecommends turning on verbose logging during troubleshooting and then changing it back to 2 when troubleshooting is complete.
If no value is specified, the default value is 2.
This parameter requires agent version 1380 or later.
Use this parameter to add devices to an existing zone, or to a zone that you want to create. If the zone does not exist, the zone is created using the name you type.
You cannot use tabs, carriage returns, newlines, equal signs, whitespace or other invisible characters in the zone name.
This parameter requires agent version 1470 or later.
This adds proxy server settings to the device’s registry. You can find the proxy server information in the agent log file.