Minimum data collection requirements for detection failures, clean failures, and false positives
Technical Articles ID:
KB91459
Last Modified: 6/13/2022
Environment
Endpoint Security (ENS) Threat Prevention 10.x
Management for Optimized Virtual Environments AntiVirus Agentless (MOVE AV Agentless) 4.x
MOVE AntiVirus Multi-Platform (MOVE AV Multi-Platform) 4.x
MVISION Endpoint
VirusScan Enterprise (VSE) 8.x
Summary
This article provides the minimum data collection requirements to engage Technical Support or Trellix Labs for the following types of issues.
Contents
Click to expand the section you want to view:
Description: There's an active infection in the environment and the product doesn't detect the malware samples. You're requesting coverage for this threat.
What was the initial entry point — email or URL? Provide details, if available.
Where was the sample found on the system? Provide the file path, registry location, and any other relevant information.
Why is the file suspected as malware? What suspicious behaviors were seen?
How many systems is this detection failure impacting? Be as accurate as possible.
How many of the systems are production servers, and what are their purposes?
Are there any other noteworthy considerations for the impacted systems?
Description: You're requesting coverage for sample hashes sourced via internal or external sourcing. Hash list escalations are considered informational, because they have no customer impact. This request type is treated as a lower Severity.
Requirements: Provide the following information:
Why are the hashes suspected as malware? What suspicious behaviors are associated with the hashes?
Provide the source of the hashes. Was the file coming from internal threat hunting, third-party intelligence sharing, or a blog? Provide relevant information, including a link to or copy of the report if available.
IMPORTANT: Don't submit multiple families of malware under the same request. Each individual variant requires a separate Service Request with its own citation to a source for the indicated hashes. The samples must be available to be sourced for us to review and add coverage. If a sample is unable to be sourced, you must submit a sample. To submit a sample, follow the instructions provided in KB68030 - Submit samples to Labs for suspected malware detection failure.
Description: When the product triggers a detection, but doesn't remove some components of the malware.
Example 1: ENS detects and deletes the malicious file, but registry entries (such as service entries or run keys) are left behind.
Example 2: ENS triggers a !memdetection. This detection indicates that there's a detection found in a process in memory. But, the file spawning the infected process isn't detected.
Requirements: Provide the following information:
Submit the detected sample from the Quarantine. The default quarantine location for ENS and VSE is C:\Quarantine.
Is it an internal application or third-party software? If third-party software, who is the vendor and what's the application name and version?
Provide a detailed description of the file and how it's being used.
Provide the installer, source, or a download URL (if available).
What's the "Threat Name" found in ePO or on the product console for this detection?
Where was the sample found on the system? Provide the file path, registry location, and any other relevant information (not mandatory to provide if you share the logs or ePO threat event).
How many systems is this false positive impacting? Be as accurate as possible.
Are there any other noteworthy considerations for the impacted systems?
Submit the relevant scan logs showing the detections.
Description: An application, or components of this application, are being detected as a potentially unwanted program. Or, it's not being detected and this detection is suspected to be incorrect.
Is the file part of an active infection in the environment?
What was the initial entry point — email, URL, or installer? Provide details if available.
Where was the sample found on the system? Provide the file path, registry location, and any other relevant information.
Was the file suspected as a potentially unwanted program? If the sample is a potentially unwanted program, provide the full installation package or download location for the program.
Why is the file suspected as a potentially unwanted program? What behaviors were seen?
Was it an internal application or third-party software? If third-party software, who is the vendor and what's the application name and version?
Provide a detailed description of the file and how it's being used.
Provide the installer, source, or a download URL if available. Typically, we need the full installation package to fully vet whether an application violates our potentially unwanted program policy.
What's the "Threat Name" found in ePO or on the product console for this detection?
Where was the sample found on the system? Provide the file path, registry location, and any other relevant information.
Submit the relevant scan logs showing the detections.
IMPORTANT: If an application violates the potentially unwanted program policy, Trellix Labs adds a detection for the application. If a potentially unwanted program detection is added and you use the application, add a potentially unwanted program exclusion to prevent detection for the application. For instructions to enable potentially unwanted program detection, and to set an exclusion, see the Product Guide.
