AllowedFileDetails

Details of the file allowed in the data center.

JSON Example

{
    "file_name": [
        "string"
    ],
    "sha256": "string",
    "sha1": "string",
    "md5": "string",
    "verdict": "string",
    "score": 0,
    "number_of_hits": 0,
    "last_inspected": 0
}

array of string

file_name

Optional

Name of the file. This is an array because a file is uniquely identified by the hash but name is a string that is user customizable. File Name will be UNKNOWN in case the file is not inspected in the data center.

string

sha256

Optional

sha256 hash of the file.

string

sha1

Optional

sha1 hash of the file

string

md5

Optional

md5 hash of the file.

Verdict

verdict

Optional

This property describes the behavior of the file at runtime. Meanings are described below BENIGN: This is a benign file with no malicious code TRUSTED: This is a TRUSTED file based on the behaviour of the file HIGHLY_TRUSTED: This is a file from a highly trusted source like for e.g microsft published the file SUSPICIOUS: This file contains suspicious code and on execution can turn out to be malware MALICIOUS: This file is a malicious file containing malware or bad code that can harm the system UNKNOWN: Either this file behavior is UNKNOWN at this point in time or there is some error in file anlaysis pipeline and verdict could not be concluded. UNINSPECTED: This file is marked as allowlisted and hence the verdict is UNINSPECTED.

Possible values are : BENIGN, TRUSTED, HIGHLY_TRUSTED, SUSPICIOUS, MALICIOUS, UNKNOWN, UNINSPECTED,

integer

score

Optional

Score of the file in the range from 0 to 100 for known verdicts. Score -1 indicates the verdict is UNINSPECTED because file is allowlisted. Any score outside the range of -1 to 100 will mean that verdict is UNKNOWN.

integer

number_of_hits

Optional

Number of times this file was inspected in the data center. This count will be 0 in case the file is not inspected in the data center.

EpochMsTimestamp

last_inspected

Optional

Timestamp in milliseconds since epoch