Fortinet FortiGuard Outbreak provides key information about on-going cybersecurity attacks with significant ramifications affecting numerous companies, organizations, and industries. This connector facilitates automated operations to fetch Indicators of Compromise (IOCs) of outbreak alert.
This document provides information about the Fortinet FortiGuard Outbreak Connector, which facilitates automated interactions, with a Fortinet FortiGuard Outbreak server using FortiSOAR™ playbooks. Add the Fortinet FortiGuard Outbreak Connector as a step in FortiSOAR™ playbooks and perform automated operations with Fortinet FortiGuard Outbreak.
Connector Version: 1.0.1
FortiSOAR™ Version Tested on: 7.4.3-3294
Authored By: Fortinet
Certified: Yes
Following enhancements have been made to the Fortinet FortiGuard Outbreak connector in version 1.0.1:
requests-pkcs12 version which was being used. Upgraded the package version to a compatible OpenSSL version.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-fortiguard-outbreak
For the procedure to configure a connector, click here
In FortiSOAR™, on the Connectors page, click the Fortinet FortiGuard Outbreak 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 Name | URL of the FortiGuard Threat Intelligence API server to which you will connect and perform automated operations. |
| 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 |
|---|---|---|
| List Outbreak Alert Tags | Retrieves a list of outbreak alert tags from FortiGuard | list_outbreak_alert_tags Investigation |
| Get Outbreak Alert IOCs | Retrieves a list of outbreak alert IOCs from FortiGuard based on the tag name that you have specified. | get_outbreak_alert_iocs Investigation |
None.
The output contains the following populated JSON schema:
[
{
"tag": ""
}
]
| Parameter | Description |
|---|---|
| Outbreak Alert Tag Name | Specify the tag name of the outbreak alert to retrieve its associated IOCs from FortiGuard server. |
The output contains the following populated JSON schema:
[
{
"ioc": "",
"type": "",
"active": ""
}
]
The Sample - Fortinet FortiGuard Outbreak - 1.0.1 playbook collection comes bundled with the Fortinet FortiGuard Outbreak 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 FortiGuard Outbreak 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.
Fortinet FortiGuard Outbreak provides key information about on-going cybersecurity attacks with significant ramifications affecting numerous companies, organizations, and industries. This connector facilitates automated operations to fetch Indicators of Compromise (IOCs) of outbreak alert.
This document provides information about the Fortinet FortiGuard Outbreak Connector, which facilitates automated interactions, with a Fortinet FortiGuard Outbreak server using FortiSOAR™ playbooks. Add the Fortinet FortiGuard Outbreak Connector as a step in FortiSOAR™ playbooks and perform automated operations with Fortinet FortiGuard Outbreak.
Connector Version: 1.0.1
FortiSOAR™ Version Tested on: 7.4.3-3294
Authored By: Fortinet
Certified: Yes
Following enhancements have been made to the Fortinet FortiGuard Outbreak connector in version 1.0.1:
requests-pkcs12 version which was being used. Upgraded the package version to a compatible OpenSSL version.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-fortiguard-outbreak
For the procedure to configure a connector, click here
In FortiSOAR™, on the Connectors page, click the Fortinet FortiGuard Outbreak 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 Name | URL of the FortiGuard Threat Intelligence API server to which you will connect and perform automated operations. |
| 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 |
|---|---|---|
| List Outbreak Alert Tags | Retrieves a list of outbreak alert tags from FortiGuard | list_outbreak_alert_tags Investigation |
| Get Outbreak Alert IOCs | Retrieves a list of outbreak alert IOCs from FortiGuard based on the tag name that you have specified. | get_outbreak_alert_iocs Investigation |
None.
The output contains the following populated JSON schema:
[
{
"tag": ""
}
]
| Parameter | Description |
|---|---|
| Outbreak Alert Tag Name | Specify the tag name of the outbreak alert to retrieve its associated IOCs from FortiGuard server. |
The output contains the following populated JSON schema:
[
{
"ioc": "",
"type": "",
"active": ""
}
]
The Sample - Fortinet FortiGuard Outbreak - 1.0.1 playbook collection comes bundled with the Fortinet FortiGuard Outbreak 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 FortiGuard Outbreak 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.