- Overview
- CylanceON-PREM architecture
- Steps to get Start with CylanceON-PREM
- Requirements: CylanceON-PREM
- Configuring the CylanceON-PREM virtual appliance
- Configuring the console
- Log in to CylanceON-PREM
- Administrative dashboard
- Filter lists
- Export lists
- Policies
- Setting up the CylancePROTECT agent
- Adding the CA certificate to endpoints
- Installing the CylancePROTECT Desktop agent for Windows
- Installing the CylancePROTECT Desktop agent for macOS
- Installing the CylancePROTECT Desktop agent for Linux
- Manually update the Linux driver
- Upgrading the CylancePROTECT Desktop agents
- Using virtual machines
- Device management
- Threat management
- Global lists
- Administration
- Managing users
- Managing roles
- Update profile information
- Audit logs
- Managing Certificates
- Setting up email notifications
- Settings
- Upgrade CylanceON-PREM
- Reboot the virtual appliance
- Configure session timeout
- Update CylanceON-PREM SSL certificate version 1.3.1 and later
- Update CylanceON-PREM SSL certificate version 1.2.2.1 and earlier
- Change the certificate cipher mode
- Enable maintenance mode
- Change network settings
- Check an IP address
- Change the log level
- Download logs
- Configure syslog/SIEM settings
- Update database connection settings
- Configure active directory
- Configure identity provider settings
- Using certificate-based authentication
- Add a banner to the login screen
- Applications
- CylanceON-PREM API
- Troubleshooting
- Agent not communicating with CylanceON-PREM
- Web browser reports insecure webpage
- Unable to connect to external database
- Configure static IP using the OVF tool
- Remote server 404 error in log files
- Log in with a local administrator account
- Online Certificate Status Protocol issues
- A user is not receiving email notifications
- Before you contact support
- BlackBerry Docs
- CylanceON-PREM
- Cylance ONPREM Administration Guide
- Setting up the CylancePROTECT agent
- Using virtual machines
Using virtual machines
Below are some recommendations for using the
CylancePROTECT Desktop
Agent on a virtual machine image. For best practices, see Best practices for deploying CylancePROTECT Desktop
on Windows virtual machines.- For non-persistent VDI environments, you can use Agent 1490 or higher and an installation parameter to instruct the Agent during installation that will be running in a pool of cloned images. This will enable the Agent to recognize each clone as a unique endpoint and persist their identification when they refresh.
- Some virtual machine software has security settings that conflict withCylancePROTECT Desktop’s Memory Protection feature. This conflict may result in an unresponsive virtual machine. If this happens, you should either disable the Memory Protection feature or use different virtual machine software.