Cymon is the largest open tracker of malware, phishing, botnets, spam, and more.
This document provides information about the Cymon connector, which facilitates automated interactions with Cymon using FortiSOAR™ playbooks. Add the Cymon connector as a step in FortiSOAR™ playbooks and perform automated operations, such as retrieving information about domains, IP addresses, or file hashes from the Cymon v1 API.
Connector Version: 1.0.0
Authored By: Fortinet
Certified: No
All connectors provided by FortiSOAR™ are delivered using a FortiSOAR™ repository. Therefore, you must set up your FortiSOAR™ repository and use the yum command to install connectors:
yum install cyops-connector-cymon
For the detailed procedure to install a connector, click here
For the procedure to configure a connector, click here
In FortiSOAR™, on the connectors page, select the Cymon connector and click Configure to configure the following parameters:
Parameter | Description |
---|---|
Server URL | Server address of Cymon. |
API Key | Valid API key to access the Cymon APIs. |
Verify SSL | Specifies whether the SSL certificate for the server is to be verified or not. By default, this option is set as True. |
The following automated operations can be included in playbooks, and you can also use the annotations to access operations from FortiSOAR™ release 4.10.0 and onwards:
Function | Description | Annotation and Category |
---|---|---|
IP Address Lookup | Fetch details about an IP address from Cymon. | lookup_ip Investigation |
Look Up Domain | Fetch details about a Domain from Cymon. | lookup_domain Investigation |
Lookup File Hash | Look up details about a file hash in Cymon. | lookup_hash Investigation |
Parameter | Description |
---|---|
IP Address | Specify the IP address for which you want to retrieve information. |
The output contains the following populated JSON schema:
{
"sources": [],
"domains": {
"count": "",
"next": "",
"previous": "",
"results": []
},
"created": "",
"addr": "",
"urls": {
"count": "",
"next": "",
"previous": "",
"results": []
},
"events": {
"count": "",
"next": "",
"previous": "",
"results": []
},
"updated": ""
}
Parameter | Description |
---|---|
Domain | Specify the Domain for which you want to retrieve information. |
The output contains the following populated JSON schema:
{
"sources": [],
"created": "",
"urls": [],
"name": "",
"updated": "",
"ips": []
}
Parameter | Description |
---|---|
Filehash | Specify the filehash for which you want to retrieve information. |
The output contains the following populated JSON schema:
{
"result": {},
"request_status": ""
}
The Sample - Cymon - 1.0.0
playbook collection comes bundled with the Cymon 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 Cymon 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.
Cymon is the largest open tracker of malware, phishing, botnets, spam, and more.
This document provides information about the Cymon connector, which facilitates automated interactions with Cymon using FortiSOAR™ playbooks. Add the Cymon connector as a step in FortiSOAR™ playbooks and perform automated operations, such as retrieving information about domains, IP addresses, or file hashes from the Cymon v1 API.
Connector Version: 1.0.0
Authored By: Fortinet
Certified: No
All connectors provided by FortiSOAR™ are delivered using a FortiSOAR™ repository. Therefore, you must set up your FortiSOAR™ repository and use the yum command to install connectors:
yum install cyops-connector-cymon
For the detailed procedure to install a connector, click here
For the procedure to configure a connector, click here
In FortiSOAR™, on the connectors page, select the Cymon connector and click Configure to configure the following parameters:
Parameter | Description |
---|---|
Server URL | Server address of Cymon. |
API Key | Valid API key to access the Cymon APIs. |
Verify SSL | Specifies whether the SSL certificate for the server is to be verified or not. By default, this option is set as True. |
The following automated operations can be included in playbooks, and you can also use the annotations to access operations from FortiSOAR™ release 4.10.0 and onwards:
Function | Description | Annotation and Category |
---|---|---|
IP Address Lookup | Fetch details about an IP address from Cymon. | lookup_ip Investigation |
Look Up Domain | Fetch details about a Domain from Cymon. | lookup_domain Investigation |
Lookup File Hash | Look up details about a file hash in Cymon. | lookup_hash Investigation |
Parameter | Description |
---|---|
IP Address | Specify the IP address for which you want to retrieve information. |
The output contains the following populated JSON schema:
{
"sources": [],
"domains": {
"count": "",
"next": "",
"previous": "",
"results": []
},
"created": "",
"addr": "",
"urls": {
"count": "",
"next": "",
"previous": "",
"results": []
},
"events": {
"count": "",
"next": "",
"previous": "",
"results": []
},
"updated": ""
}
Parameter | Description |
---|---|
Domain | Specify the Domain for which you want to retrieve information. |
The output contains the following populated JSON schema:
{
"sources": [],
"created": "",
"urls": [],
"name": "",
"updated": "",
"ips": []
}
Parameter | Description |
---|---|
Filehash | Specify the filehash for which you want to retrieve information. |
The output contains the following populated JSON schema:
{
"result": {},
"request_status": ""
}
The Sample - Cymon - 1.0.0
playbook collection comes bundled with the Cymon 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 Cymon 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.