CylanceHYBRID considerations
CylanceHYBRID
considerationsItem | Description |
|---|---|
CylanceHYBRID local user account password | Currently there is no mechanism to reset or recover the password unless you have configured CylanceHYBRID to use Microsoft Active
Directory . If Active
Directory is not configured, losing a password will require reinstalling CylanceHYBRID . If Active
Directory is configured, an authorized CylanceHYBRID user using their corporate credentials can log in and change the CylanceHYBRID local user account password. See Change the local user account password for more information. |
Communicate through another CylanceHYBRID application | A CylanceHYBRID application cannot communicate to or through another CylanceHYBRID application. |
Static IP address | CylanceHYBRID does not support Cylance console static IP addresses. |
Cylance API | The Cylance API cannot be used to modify the CylanceHYBRID application. |
Cylance console | A CylanceHYBRID application appears on the Cylance console, but currently cannot be managed from the console. |
Devices connected to CylanceHYBRID | Devices configured to communicate with a CylanceHYBRID must be able to communicate with the DNS host name you created for CylanceHYBRID over TCP port 443. After a device is registered with the console, removing a device, like taking a laptop home, results in the device being offline. In offline mode, agents will continue to function as designed, using the last policy update received while the device was online. |
Virtualization high availability | If your virtualization application has a high availability feature, you should use it to provide failure protection against hardware and operating system outages for your CylanceHYBRID environment. For example, see VMware 's article here. |