File-scoring service protocols Skip Navigation
  1. BlackBerry Docs
  2. Cylance OEM Engine
  3. OEM Engine Developer guide
  4. File-scoring service protocols

File-scoring service protocols

The
Cylance OEM Engine
 file-scoring service (
Cylance
TcpService) provides a method to score individual files and archives. The file-scoring service supports three protocols:
  • The legacy Infinity Daemon Protocol (IDP), also known as the
    Cylance
    TcpService Protocol, is the proprietary binary protocol supported by TcpShim, InfinityTcpService, and
    Cylance
    TcpService.
    To use the service with this protocol, a TCP connection must be established with the server. The service can be configured to listen on any valid TCP port number (1024 - 65535). Port 9002 is the default port in InfinityDaemonClient, samplescored, samplescore, and ttmstatic. The port used by the service can be customized using the configuration file or the
    p
     or
    --port
     command-line option.
  • A REST-based API called the
    Cylance
     Engine RESTful API (CERA), based on standard HTTP and HTTPS connections using JSON for both requests and responses. This protocol was introduced in
    OEM Engine
     v0.11 and is supported by
    Cylance
    TcpService only. Note that this is only available under
    Microsoft .NET
     5.0 or later (v0.11) or
    Microsoft .NET
     6.0 or later (v1.0 and later); it is not available for
    Mono
    .
  • An Internet Content Adaptation Protocol (ICAP) service, based on the ICAP protocol (rfc3507). The service is situated between an ICAP client and the file-scoring service using the CERA. For documentation, see the ICAP service package that is downloaded separately.
The protocols serve as a bridge between client code and
Cylance OEM Engine
 activities, acting as a generic service, providing the infrastructure to process files and hand the results back to the client.