- What is the Cylance Engine?
- How the Cylance Engine analyzes a file
- System requirements for the Cylance Engine
- Installing and updating the Cylance Engine
- Install the Cylance Engine on a Linux distribution
- Query the version of your Cylance Engine on a Linux distribution
- Update the version of your Cylance Engine on a Linux distribution
- Remove the Cylance Engine from a Linux distribution
- Install the Cylance Engine on a Windows distribution
- Query the version of your Cylance Engine on a Windows distribution
- Update the version of your Cylance Engine on a Windows distribution
- Remove the Cylance Engine from a Windows distribution
- File-scoring service
- File-scoring service protocols
- Appendix: Cylance Infinity Data Service
- Appendix: Threat indicators
- Appendix: Prometheus monitoring support
- Appendix: CylanceTcpService Protocol
- BlackBerry Docs
- Cylance Engine
- Cylance Engine Integration Guide
- Appendix: CylanceTcpService Protocol
Appendix: CylanceTcpService Protocol
Cylance
TcpService ProtocolThe
Cylance
TcpService Protocol was known previously as the Infinity Daemon Protocol (IDP).All requests begin with a single character (byte) specifying the command to perform. The format of the remainder of the request is command-specific and is described below.
Once the service has finished performing a command, it sends a response to the client and then attempts to receive another command from the connection. The format of the response is also command-specific and is described below.
- All numeric fields are represented in binary. For multiple-byte fields such as 16- and 32-bit integers, the byte order is little-endian.
- String fields are encoded as UTF-8 with no initial byte order mark (BOM) or terminating null character. In general, string fields are preceded by a length field that specifies the size of the string in bytes (not characters).