Trellix McAfee Advanced Threat Defense

LAST UPDATED: OCT 22, 2024

Overview

McAfee Advanced Threat Defense (ATD) enables organizations to detect advanced, evasive malware and convert threat information into immediate action and protection.

D3 SOAR is providing REST operations to function with Trellix McAfee Advanced Threat Defense.

Trellix McAfee Advanced Threat Defense is available for use in:

D3 SOAR	V12.7.83.0+
Category	Threat Intelligence
Deployment Options	Option I, Option III

Connection

To connect to Trellix McAfee Advanced Threat Defense from D3 SOAR, please follow this part to collect the required information below:

Parameter	Description	Example
Server URL (domain level)	The domain level URL of the Trellix McAfee Advanced Threat Defense server.	1.2.3.4
Username	The username for authentication.	admin
Password	The password for authentication.	Password

Configuring D3 SOAR to Work with Trellix McAfee Advanced Threat Defense

Log in to D3 SOAR.
Find the Trellix McAfee Advanced Threat Defense integration.
1. Navigate to Configuration on the top header menu.
2. Click on the Integration icon on the left sidebar.
3. Type Trellix McAfee Advanced Threat Defense in the search box to find the integration, then click it to select it.
4. Click + New Connection, on the right side of the Connections section. A new connection window will appear.
Configure the following fields to create a connection to Trellix McAfee Advanced Threat Defense.
1. Connection Name: The desired name for the connection.
2. Site: Specifies the site to use the integration connection. Use the drop-down menu to select the site. The Share to Internal Sites option enables all sites defined as internal sites to use the connection. Selecting a specific site will only enable that site to use the connection.
3. Recipient site for events from connections Shared to Internal Sites: This field appears if you selected Share to Internal Sites for Site to let you select the internal site to deploy the integration connection.
4. Agent Name (Optional): Specifies the proxy agent required to build the connection. Use the dropdown menu to select the proxy agent from a list of previously configured proxy agents.
5. Description (Optional): Add your desired description for the connection.
6. Tenant (Optional): When configuring the connection from a master tenant site, you have the option to choose the specific tenant sites you want to share the connection with. Once you enable this setting, you can filter and select the desired tenant sites from the dropdowns to share the connection.
7. Configure User Permissions: Defines which users have access to the connection.
8. Active: Check the tick box to ensure the connection is available for use.
9. System: This section contains the parameters defined specifically for the integration. These parameters must be configured to create the integration connection.
  1. Input the domain level Server URL.
  2. Input the Username.
  3. Input the Password.
10. Enable Password Vault: An optional feature that allows users to take the stored credentials from their own password vault. Please refer to the password vault connection guide if needed.
Test the connection.
1. Click Test Connection to verify the account credentials and network connection. If the Test Connection Passed alert window appears, the test connection is successful. You will see Passed with a green checkmark appear beside the Test Connection button. If the test connection fails, please check your connection parameters and try again.
2. Click OK to close the alert window.
3. Click + Add to create and add the configured connection.

Commands

Trellix McAfee Advanced Threat Defense includes the following executable commands for users to set up schedules or create playbook workflows. With the Test Command, you can execute these commands independently for playbook troubleshooting.

Integration API Note

For more information about the Trellix McAfee Advanced Threat Defense API, please refer to the Trellix McAfee Advanced Threat Defense API reference.

READER NOTE

Certain permissions are required for each command. Please refer to the Permission Requirements and Configuring Trellix McAfee Advanced Threat Defense to Work with D3 SOAR for details.

Submit Files

Submits files to the sandbox in McAfee ATD.

Input

Input Parameter	Required/Optional	Description	Example
Files	Required	The name of the sample file.	[ { "FileName": "write.exe", "FileSize": 11264, "FileContentType": "application/exe", "FileContent": "TV******A//8AAA=" } ]
VM Profile List	Optional	The profile number of the utilized VM. There are four acceptable values to specify the submit type: 0 — Regular file upload: Upload a file directly for analysis. 1 — URL submission: Submit a URL link for processing inside the analyzer VM. 2 — Submit file with URL: Upload a file along with a corresponding URL for analysis. 3 — URL Download: Download a file from the provided URL and then subject it to analysis within the VM.	1
File Source	Optional	The file source of the file to send. The options for file sources are: Incident Attachment File: A file that has been manually uploaded during an incident. Playbook File: The output file generated from a previous playbook task. Artifact File: An ingested artifact from an event.	Playbook File

Output

Raw Data

The primary response data from the API request.

SAMPLE DATA

JSON

[
    {
        "Summary": {
            "MISversion": "4.6.0.21",
            "SUMversion": "4.6.0.21",
            "DETversion": "4.6.2.190704",
            "OSversion": "win2k16p0x64",
            "JSONversion": "1.003",
            "SubmitterName": "admin",
            "SubmitterType": "STAND_ALONE",
            "TaskId": "*****",
            "JobId": "*****",
            "hasDynamicAnalysis": "true",
            "Subject": {
                "Name": "write.exe",
                "Type": "PE32+ executable (GUI) x86-64",
                "FileType": "0",
                "md5": "*****",
                "sha-1": "*****",
                "sha-256": "*****",
                "size": "11264",
                "Timestamp": "2020-02-18 09:16:04",
                "parent_archive": "Not Available"
            },
            "Environment": [
                "Microsoft Windows Server 2016Standard Edition (build 14393, version 10.0.14393), 64-bit",
                "Internet Explorer version: 11.0.14393.0",
                "Microsoft Office version: 2016",
                "PDF Reader version: DC",
                "No Flash player installed",
                "Flash player plugin version: 18.0.0.203"
            ],
            "Data": {
                "analysis_seconds": "45",
                "sandbox_analysis": "180",
                "compiled_with": "Not Available"
            },
            "Bait": "Baitexe activated but not infected",
            "Properties": {
                "signature": "Unsigned",
                "publisher": "Not Available",
                "company": "Microsoft Corporation",
                "description": "Windows Write",
                "product_name": "MicrosoftÂ® WindowsÂ® Operating System",
                "version_info": "10.0.18362.1",
                "file_version": "10.0.18362.1 (WinBuild.160101.0800)",
                "machine_type": "Microsoft Corporation",
                "binary_version": "10.0.18362.1",
                "strong_name": "Not Available",
                "original_name": "write",
                "internal_name": "write",
                "copyright": "Â© Microsoft Corporation. All rights reserved.",
                "comments": "Not Available"
            },
            "Selectors": [
                {
                    "Engine": "Gateway Anti-Malware",
                    "MalwareName": "---",
                    "Severity": "0"
                },
                {
                    "Engine": "GTI File Reputation",
                    "MalwareName": "---",
                    "Severity": "-1"
                },
                {
                    "Engine": "Anti-Malware",
                    "MalwareName": "---",
                    "Severity": "0"
                },
                {
                    "Engine": "Sandbox",
                    "MalwareName": "---",
                    "Severity": "0"
                }
            ],
            "Verdict": {
                "Severity": "-1",
                "Description": "Sample is clean according to the GTI's File Reputation",
                "Verdict": "Clean"
            },
            "ATDml_Prediction": [
                {
                    "ATDml_Verdict": "Unknown",
                    "ATDml_factor": "0.00"
                }
            ],
            "Files": [
                {
                    "Processes": [
                        {
                            "RelType": "1",
                            "Name": "write.exe",
                            "Sha256": "*****"
                        }
                    ],
                    "Md5": "*****",
                    "Sha1": "*****",
                    "Sha256": "*****",
                    "Name": "write.exe",
                    "FileType": "0"
                },
                {
                    "Processes": [
                        {
                            "RelType": "512",
                            "Name": "write.exe",
                            "Sha256": "*****"
                        }
                    ],
                    "Md5": "",
                    "Sha1": "",
                    "Sha256": "",
                    "Name": "wordpad.exe",
                    "FileType": "0"
                }
            ],
            "Process": [
                {
                    "Name": "write.exe",
                    "Reason": "loaded by MATD Analyzer",
                    "Severity": "1"
                },
                {
                    "Name": "wordpad.exe",
                    "Reason": "executed by write.exe",
                    "Severity": "0"
                }
            ],
            "Stats": [
                {
                    "ID": "0",
                    "Category": "Persistence, Installation Boot Survival ",
                    "Severity": "0"
                },
                {
                    "ID": "1",
                    "Category": "Hiding, Camouflage, Stealthiness, Detection and Removal Protection ",
                    "Severity": "0"
                },
                {
                    "ID": "2",
                    "Category": "Security Solution / Mechanism bypass, termination and removal, Anti Debugging, VM Detection ",
                    "Severity": "0"
                },
                {
                    "ID": "3",
                    "Category": "Spreading ",
                    "Severity": "0"
                },
                {
                    "ID": "4",
                    "Category": "Exploiting, Shellcode ",
                    "Severity": "0"
                },
                {
                    "ID": "5",
                    "Category": "Networking ",
                    "Severity": "0"
                },
                {
                    "ID": "6",
                    "Category": "Data spying, Sniffing, Keylogging, Ebanking Fraud ",
                    "Severity": "0"
                }
            ],
            "Behavior": [
                "Identified as --- by Gateway Anti-Malware",
                "Identified as --- by GTI File Reputation",
                "Identified as --- by Anti-Malware",
                "Executed active content by Windows shell application"
            ],
            "Mitre": [
                {
                    "Techniques": "Execution through API",
                    "Tactics": "Execution",
                    "Rules": [
                        {
                            "Description": "Executed active content by Windows shell application",
                            "Severity": "1"
                        }
                    ]
                }
            ],
            "Processes": [
                {
                    "Name": "write.exe",
                    "Process Operations": [
                        {
                            "Process Created": [
                                "c:/program files/windows nt/accessories/wordpad.exe, c:/program files/windows nt/accessories/wordpad.exe "
                            ],
                            "Process Opened": [
                                "Shell command: , WORDPAD.EXE"
                            ],
                            "Process killed": [
                                "Ended itself and all of its threads"
                            ],
                            "Other": [
                                "Enabled an application to supersede the top-level exception handler"
                            ]
                        }
                    ]
                }
            ]
        },
        "filename": "write.exe",
        "riskscore": " "
    }
]

Context Data

The data extracted from Raw Data converted into JSON format. Context Data may be identical to Raw Data in some cases.

D3 customizes the context data by extracting "fileName", "md5", "sha1", "sha256" and "risklevel" fields from the returned API results.

It is recommended to refer to the Raw Data instead of Context Data, since it contains the complete API response data. D3 will deprecate Context Data in the future, and playbook tasks using Context Data will be replaced with Raw Data.

SAMPLE DATA

CODE

[
    {
        "fileName": "write.exe",
        "md5": "*****",
        "sha1": "*****",
        "sha256": "*****",
        "riskLevel": "none"
    }
]

Key Fields

Common cyber security indicators such as unique IDs, file hash values, CVE numbers, IP addresses, etc., will be extracted from Raw Data as Key Fields.
The system stores these key fields in the path $.[playbookTask].outputData. You can use these key-value pairs as data points for playbook task inputs.

SAMPLE DATA

CODE

{
    "fileName": [
        "write.exe"
    ],
    "md5": [
        "****"
    ],
    "sha1": [
        "*****"
    ],
    "sha256": [
        "*****"
    ],
    "riskLevel": [
        "none"
    ]
}

Return Data

Indicates one of the possible command execution states: Successful, Partially Successful, or Failed.

The Partially Successful state only occurs when a command’s input accepts an array of items (e.g. an array of IP addresses) and one or more items within the array return an error from the API request.

The Failed state can be triggered by any of the following errors:

A connection issue with the integration

The API returned an error message

No response from the API

You can view more details about an error in the Error tab.

Return Data can be passed down directly to a subsequent command or used to create conditional tasks in playbooks.

SAMPLE DATA

CODE

Successful

Result

Provides a brief summary of outputs in an HTML formatted table.

SAMPLE DATA

CODE

No Sample Data

Error Handling

If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help you locate the root cause of a command failure.

Parts in Error	Description	Example
Failure Indicator	Indicates the command failure that happened at a specific input and/or API call.	Submit Files failed.
Status Code	The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Trellix McAfee Advanced Threat Defense portal. Refer to the HTTP Status Code Registry for details.	Status Code: 400.
Message	The raw data or captured key error message from the integration API server about the API request failure.	Message: One or more errors occurred.

Error Sample Data

Submit Files failed.

Status Code: 400.

Message: One or more errors occurred.