Scenarios for using Threat Intelligence Exchange

Prev Next

Consider these basic use case scenarios for using the TIE services to block and allow files to run in your environment and to import reputations.

  • Immediately block a file — The Trellix Threat Intelligence Administrator uses TIE services to investigate about files with unknown reputations in the environment. Instead of sending the file information to Trellix for analysis, the administrator promptly blocks the file. Subsequently, the administrator utilizes TIE to determine the file's potential threat level and the number of systems that have executed it.

  • Allow a custom file to run — A company regularly uses a file in its operations, which by default is categorized as suspicious or malicious, such as a custom file. Instead of sending the file information to Trellix for analysis and getting an updated DAT file, the administrator proactively modifies the file's reputation to trusted, enabling uninterrupted execution without any warnings or prompts.

  • Import known reputations — A company manages multiple files, such as trusted, regularly used, and disallowed files. Leveraging the pre-established reputations, the administrator imports a file list directly into the TIE services database, enabling immediate use of these reputations without any additional steps.

  • See additional information about a file — For any file or certificate with unknown reputation, the Threat Intelligence Exchange server allows the network administrator to inspect its details. The administrator can see several details about the file, such as the file's parent process, company and version information, hash information, and the systems that ran the file. The administrator can also see more detailed information about the file with VirusTotal, a free online scanning service for viruses, malware, and URLs.

  • See additional information about a file — The TIE services allow the network administrator to investigate details for files or certificates with an unknown reputation. The administrator gains visibility into various aspects of the file, including its parent process, company and version information, hash details, and the systems that have executed the file.