Skip Navigation
  1. BlackBerry Docs
  2. Cylance Endpoint Security
  3. Cylance User API guide
  4. Global list API
  5. Add safe script entry

Add safe script entry

Add a SHA256 of the script file content. If the script file runs on the device whose content matches the added SHA256, it will not be analyzed and no event will be generated for it.  As part of adding the hash, the API allows the caller to add information about it, including:
  • The filename path that the caller wants to associate with this hash.
  • The reason why the hash is being added.
The file path and reason are optional and don't have to be unique. The system does not use filename or reason in determining if the script should be excluded from any control. The SHA256 hash must be unique for each tenant.
Service endpoint
/globallists/v2/script/whitelist
Optional query string parameters
—
Example
https://protectapi.cylance.com/ globallists/v2/script/whitelist
Method
HTTP/1.1 POST
Request headers
  • Accept: application/json
  • Authorization: Bearer
    JWT Token returned by Auth API
     with the globallist:Create scope encoded

Request

Body payload example:
{
    "sha256": "5A56B16953451FFA1C79F2397DB92475E440D430E4B6FB6E188E5E9DBFC9DDE4",
    "file_path" : "/FileFolder1/FileFolder2",
    "description" : ""I am adding this whitelist because this script file is safe and should not be blocked."
},

Response

Please see the Response status codes for more information.

Request json schema

Field Name
Description
fileSHA256
The script file that matches the hash will be allowed to execute regardless of the other script controls that have been configured for the tenant. If another exclusion exists with the same value for fileSHA256, an error is returned.
filePath
The file path that is used to describe the hash. This is an optional value.
description
The description or reason of the safe list entry. This is a required field with a limit of 65 characters.