Fortinet FortiNDR v1.2.0

About the connector

FortiNDR is a leading-edge product that utilizes machine learning technology for malware detection, intrusion detection, and network anomalies.

This document provides information about the Fortinet FortiNDR connector, which facilitates automated interactions with your FortiNDR server using FortiSOAR™ playbooks. Add the Fortinet FortiNDR connector, as a step in FortiSOAR™ playbooks and perform automated operations such as submitting file samples for Express Malware Analysis and potentially fetching scan verdicts.

Version information

Connector Version: 1.2.0

FortiSOAR™ Version Tested on: 6.4.4-3164

FortiNDR Version tested on: v7.0.0 build0006 (Beta)

Authored By: Fortinet

Certified: Yes

Release Notes for version 1.2.0

Following enhancements have been made in the Fortinet FortiNDR connector in version 1.2.0:

• Renamed connector from 'Fortinet FortAI' to 'Fortinet FortiNDR'.

Installing the connector

Use the Connector Store to install the connector. For the detailed procedure to install a connector, click here.
You can also use the following yum command as a root user to install connectors from an SSH session:

yum install cyops-connector-fortinet-fortiai

Prerequisites to configuring the connector

• You must have the URL of the Fortinet FortiNDR server to which you will connect and perform automated operations and the API key configured for your account for using that server.
• The FortiSOAR™ server should have outbound connectivity to port 443 on the Fortinet FortiNDR server.

Permissions Required

To perform actions using the Fortinet FortiNDR connector and perform the automated operations, users' admin profile should be assigned read-write access to FortiNDR.

Configuring the connector

For the procedure to configure a connector, click here.

Configuration parameters

In FortiSOAR™, on the Connectors page, click the Fortinet FortiNDR connector row (if you are in the Grid view on the Connectors page), and in the Configurations tab enter the required configuration details:

Actions supported by the connector

The following automated operations can be included in playbooks, and you can also use the annotations to access operations:

operation: Submit File

Input parameters

Note: If the "Submit File" action is run on an agent machine, then a dummy filename is sent during submission instead of the exact file name due to some product issue.

The output contains the following populated JSON schema:
{
"result": {
"submit_id": ""
},
"status": ""
}

operation: Get File Verdict Result

Input parameters

Output

The output contains the following populated JSON schema if 'Get Result By' is retrieved using the 'SID(Submission ID)' option:
{
"results": {
"fileids": [],
"total_fileids": ""
}
}

The output contains the following populated JSON schema if 'Get Result By' is retrieved using the 'File ID', 'MD5', or 'SHA512' option:
{
"results": {
"file_id": "",
"virus_name": "",
"md5": "",
"sha512": "",
"file_size": "",
"source": "",
"severity": "",
"category": "",
"create_date": "",
"confidence": "",
"file_type": "",
"victim_ip": "",
"attacker_ip": "",
"victim_port": "",
"attacker_port": "",
"engine_version": "",
"kdb_version": "",
"tmfc": "",
"pbit": ""
}
}

Included playbooks

The Sample - Fortinet FortiNDR - 1.2.0 playbook collection comes bundled with the Fortinet FortiNDR connector. These playbooks contain steps using which you can perform all supported actions. You can see bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Fortinet FortiNDR connector.

• Get File Verdict Result
• Submit File

Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during the connector upgrade and delete.