The FortiNDR is a leading-edge product which utilizes machine learning technology for malware detection, intrusion detection and network anomalies.. This connector provides action to submits file samples for analysis and potentially fetches scan verdicts
This document provides information about the Fortinet FortiNDR Connector, which facilitates automated interactions, with a Fortinet FortiNDR server using FortiSOAR™ playbooks. Add the Fortinet FortiNDR Connector as a step in FortiSOAR™ playbooks and perform automated operations with Fortinet FortiNDR.
Connector Version: 1.3.0
FortiSOAR™ Version Tested on: 7.5.0-4015
Fortinet FortiNDR Version Tested on: 7.4.1
Authored By: Fortinet
Certified: Yes
Following enhancements have been made to the Fortinet FortiNDR Connector in version 1.3.0:
Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.
You can also use the yum command as a root user to install the connector:
yum install cyops-connector-fortinet-fortiai
For the procedure to configure a connector, click here
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:
| Parameter | Description |
|---|---|
| Server URL | URL of the FortiNDR server to which you will connect and perform automated operations. |
| API Key | API key that is configured for your account for using the FortiNDR server. |
| Verify SSL | Specifies whether the SSL certificate for the server is to be verified. By default, this option is set to True. |
The following automated operations can be included in playbooks and you can also use the annotations to access operations:
| Function | Description | Annotation and Category |
|---|---|---|
| Submit File | Submits a file for analysis to Fortinet FortiNDR from FortiSOAR™'s Attachments module; i.e. based on the attachment IRI or file IRI that you have specified in the corresponding playbook step. | submit_file Investigation |
| Get File Verdict Result | Retrieves the results of the file verdict result from the FortiNDR server based on the MD5, SID, File ID, SHA1, or SHA256 values you have specified for that file | get_file_verdict_results Investigation |
| Get Events | Retrieves detailed list of events based on the IP hostname, event type, and other input parameters that you have specified. | get_events Investigation |
| Parameter | Description |
|---|---|
| File IRI/Attachment ID | Select the method using which to submit the file present in FortiSOAR™ for analysis to FortiNDR. You can choose from following options:
The supported file types are 32-bit and 64-bit executable files, which apply to all the Portable Executables (PE) files, any text-based files, such as HTML, VBA, VBS, JS, BAT, SH, PHP, XML, etc., power shell scripts, archive formats like .tar, .gz, .tar.gz, .tgz, .zip, .bz2, .rar, office documents, or PDF files. The maximum file size supported is 200 MB. |
| Password | (Optional) Specify the password for .zip file. |
The output contains the following populated JSON schema:
{
"result": {
"submit_id": ""
},
"status": ""
}
| Parameter | Description |
|---|---|
| Get Result By | Specify the value based on which you want to retrieve the results of the file verdict from FortiNDR. You can choose from the following options:
|
The output contains the following populated JSON schema:
Output schema when you choose "Get Result By" as "SID(Submission ID)":
{
"results": {
"fileids": [],
"total_fileids": ""
}
}
This is the default output schema:
{
"results": {
"file_id": "",
"virus_name": "",
"md5": "",
"sha1": "",
"sha256": "",
"file_size": "",
"source": "",
"severity": "",
"category": "",
"create_date": "",
"confidence": "",
"file_type": "",
"victim_ip": "",
"attacker_ip": "",
"victim_port": "",
"attacker_port": "",
"engine_version": "",
"kdb_version": "",
"tmfc": "",
"pbit": "",
"detected_by_ai_only": "",
"family": "",
"file_name": "",
"parent_fname": "",
"tfc": ""
}
}
| Parameter | Description |
|---|---|
| IP or Hostname or MAC | Select an option to get anomaly events. You can choose from following options:
|
| Event Type | Specify the anomaly event type. You can choose from the following options:
|
| Start Time | Specify the start time of events to filter the results. |
| End Time | Specify the end time of events to filter the results. |
| Offset | Specify the number of records to skip from the results returned by this operation. This parameter is useful if you want to get a subset of records. For example, to skip the first 10 records, specify 10 in this field. By default, this is set to 0. |
| Size | Specify the maximum number of results that this operation should return per page. By default, this is set to 500. |
The output contains the following populated JSON schema:
{
"results": [
{
"event_time": "",
"source_ip": "",
"source_port": "",
"destination_ip": "",
"destination_port": "",
"severity": "",
"attack_name": ""
}
]
}
The Sample - Fortinet FortiNDR - 1.3.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.
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 connector upgrade and delete.
The FortiNDR is a leading-edge product which utilizes machine learning technology for malware detection, intrusion detection and network anomalies.. This connector provides action to submits file samples for analysis and potentially fetches scan verdicts
This document provides information about the Fortinet FortiNDR Connector, which facilitates automated interactions, with a Fortinet FortiNDR server using FortiSOAR™ playbooks. Add the Fortinet FortiNDR Connector as a step in FortiSOAR™ playbooks and perform automated operations with Fortinet FortiNDR.
Connector Version: 1.3.0
FortiSOAR™ Version Tested on: 7.5.0-4015
Fortinet FortiNDR Version Tested on: 7.4.1
Authored By: Fortinet
Certified: Yes
Following enhancements have been made to the Fortinet FortiNDR Connector in version 1.3.0:
Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.
You can also use the yum command as a root user to install the connector:
yum install cyops-connector-fortinet-fortiai
For the procedure to configure a connector, click here
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:
| Parameter | Description |
|---|---|
| Server URL | URL of the FortiNDR server to which you will connect and perform automated operations. |
| API Key | API key that is configured for your account for using the FortiNDR server. |
| Verify SSL | Specifies whether the SSL certificate for the server is to be verified. By default, this option is set to True. |
The following automated operations can be included in playbooks and you can also use the annotations to access operations:
| Function | Description | Annotation and Category |
|---|---|---|
| Submit File | Submits a file for analysis to Fortinet FortiNDR from FortiSOAR™'s Attachments module; i.e. based on the attachment IRI or file IRI that you have specified in the corresponding playbook step. | submit_file Investigation |
| Get File Verdict Result | Retrieves the results of the file verdict result from the FortiNDR server based on the MD5, SID, File ID, SHA1, or SHA256 values you have specified for that file | get_file_verdict_results Investigation |
| Get Events | Retrieves detailed list of events based on the IP hostname, event type, and other input parameters that you have specified. | get_events Investigation |
| Parameter | Description |
|---|---|
| File IRI/Attachment ID | Select the method using which to submit the file present in FortiSOAR™ for analysis to FortiNDR. You can choose from following options:
The supported file types are 32-bit and 64-bit executable files, which apply to all the Portable Executables (PE) files, any text-based files, such as HTML, VBA, VBS, JS, BAT, SH, PHP, XML, etc., power shell scripts, archive formats like .tar, .gz, .tar.gz, .tgz, .zip, .bz2, .rar, office documents, or PDF files. The maximum file size supported is 200 MB. |
| Password | (Optional) Specify the password for .zip file. |
The output contains the following populated JSON schema:
{
"result": {
"submit_id": ""
},
"status": ""
}
| Parameter | Description |
|---|---|
| Get Result By | Specify the value based on which you want to retrieve the results of the file verdict from FortiNDR. You can choose from the following options:
|
The output contains the following populated JSON schema:
Output schema when you choose "Get Result By" as "SID(Submission ID)":
{
"results": {
"fileids": [],
"total_fileids": ""
}
}
This is the default output schema:
{
"results": {
"file_id": "",
"virus_name": "",
"md5": "",
"sha1": "",
"sha256": "",
"file_size": "",
"source": "",
"severity": "",
"category": "",
"create_date": "",
"confidence": "",
"file_type": "",
"victim_ip": "",
"attacker_ip": "",
"victim_port": "",
"attacker_port": "",
"engine_version": "",
"kdb_version": "",
"tmfc": "",
"pbit": "",
"detected_by_ai_only": "",
"family": "",
"file_name": "",
"parent_fname": "",
"tfc": ""
}
}
| Parameter | Description |
|---|---|
| IP or Hostname or MAC | Select an option to get anomaly events. You can choose from following options:
|
| Event Type | Specify the anomaly event type. You can choose from the following options:
|
| Start Time | Specify the start time of events to filter the results. |
| End Time | Specify the end time of events to filter the results. |
| Offset | Specify the number of records to skip from the results returned by this operation. This parameter is useful if you want to get a subset of records. For example, to skip the first 10 records, specify 10 in this field. By default, this is set to 0. |
| Size | Specify the maximum number of results that this operation should return per page. By default, this is set to 500. |
The output contains the following populated JSON schema:
{
"results": [
{
"event_time": "",
"source_ip": "",
"source_port": "",
"destination_ip": "",
"destination_port": "",
"severity": "",
"attack_name": ""
}
]
}
The Sample - Fortinet FortiNDR - 1.3.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.
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 connector upgrade and delete.