- 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
Memory event fields
The following information displays in the Events List:
Memory Event | Description |
---|---|
Acknowledged | Acknowledging an event means it has been reviewed. |
Action | This is the action taken on the event. |
Device Name | This is the name of the device. |
File Path | This is the path to the file that triggered the memory event. |
Hash | This is the SHA256 hash information for the event. |
Reported On | This is the date and time the event was first discovered in your organization. |
Process ID | This is the ID of the process that caused the memory event. |
Type | This is the exploit type. |
Username | This is the user that was logged in to the device when the memory event occurred. |