Anomali Match
Anomali Enterprise Pack.#
This Integration is part of theUse Anomali Match to search indicators and enrich domains.
#
Configure Anomali Match on Cortex XSOAR- Navigate to Settings > Integrations > Servers & Services.
- Search for Anomali Enterprise.
- Click Add instance to create and configure a new integration instance.
Parameter | Description | Required |
---|---|---|
url | Server URL (e.g., https://www.test.com\) | True |
credentials | Username | True |
insecure | Trust any certificate (not secure) | False |
proxy | Use system proxy settings | False |
- Click Test to validate the URLs, token, and connection.
#
CommandsYou can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.
#
anomali-enterprise-retro-forensic-searchInitiates a forensic search of the indicators.
#
Base Commandanomali-enterprise-retro-forensic-search
#
InputArgument Name | Description | Required |
---|---|---|
from | The time the indicators first appeared, in the format: <number> <time unit>, e.g., 1 hour, 30 minutes. Default is 1 day ago. | Optional |
to | The time the indicators last appeared, in the format: <number> <time unit>, e.g., 1 hour, 30 minutes. Default is now. | Optional |
indicators | A comma-separated list of indicators to search. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
AnomaliEnterprise.ForensicSearch.job_id | String | The job ID of the search. |
AnomaliEnterprise.ForensicSearch.status | String | The status of the search. |
#
Command Example!anomali-enterprise-retro-forensic-search indicators=1.1.1.1 from="1 month"
#
Context Example#
Human Readable Output#
Forensic search started:
job_id status job1271604409989806 in progress
#
anomali-enterprise-retro-forensic-search-resultsRetrieves the forensic search results.
#
Base Commandanomali-enterprise-retro-forensic-search-results
#
InputArgument Name | Description | Required |
---|---|---|
job_id | The forensic search job ID. | Required |
limit | Limit the stream results to return. Default is 20. | Optional |
verbose | Whether to print the stream results to the War Room. Default is "true". | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
AnomaliEnterprise.ForensicSearch.job_id | String | The job ID of the search. |
AnomaliEnterprise.ForensicSearch.status | String | The status of the search. |
AnomaliEnterprise.ForensicSearch.scannedEvents | Number | The number of scanned events. |
AnomaliEnterprise.ForensicSearch.processedFiles | Number | The number of processed files. |
AnomaliEnterprise.ForensicSearch.result_file_name | String | The matched file name. |
AnomaliEnterprise.ForensicSearch.totalMatches | Number | The number of total matches. |
AnomaliEnterprise.ForensicSearch.complete | Bool | Whether the search was complete. |
AnomaliEnterprise.ForensicSearch.category | String | The search category. |
AnomaliEnterprise.ForensicSearch.streamResults | Unknown | The stream results for the search. |
#
Command Example!anomali-enterprise-retro-forensic-search-results job_id=job1251604409794526
#
Context Example#
Human Readable Output#
Forensic search metadata:
status job_id category totalFiles scannedEvents completed job1251604409794526 forensic_api_result 1 361295
#
Forensic search results:
count event.dest event.src event_time 1 1.1.1.1 1.1.1.1 2020-10-14T09:10:00.000+0000
#
anomali-enterprise-dga-domain-statusThe search domains Domain Generation Algorithm (DGA).
#
Base Commandanomali-enterprise-dga-domain-status
#
InputArgument Name | Description | Required |
---|---|---|
domains | A comma-separated list of domains to search. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
AnomaliEnterprise.DGA.domain | String | The domain that was checked. |
AnomaliEnterprise.DGA.malware_family | String | The malware family associated with the domain. |
AnomaliEnterprise.DGA.domain | Number | The probability of the domain being malicious. |
#
Command Example!anomali-enterprise-dga-domain-status domains=amazon.com
#
Context Example#
Human Readable Output#
Domains DGA:
domain probability amazon.com 0
#
domainThe search domains Domain Generation Algorithm (DGA). Includes DBotScore and domain information. There is no distinction between benign to unknown domains in Anomali Enterprise. The Domain reputation is calculated per the product documentation. if malware family exists and prob > 0.6 the reputation is Malicious, if malware family exists and prob < 0.6 the reputation is Suspicious, else, the reputation is Unknown.
#
Base Commanddomain
#
InputArgument Name | Description | Required |
---|---|---|
domain | A comma-separated list of domains to search. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
AnomaliEnterprise.DGA.domain | String | The domain that was checked. |
AnomaliEnterprise.DGA.malware_family | String | The malware family associated with the domain. |
AnomaliEnterprise.DGA.domain | Number | The probability of the domain being malicious. |
DBotScore.Indicator | String | The indicator that was tested. |
DBotScore.Type | String | The indicator type. |
DBotScore.Vendor | String | The vendor used to calculate the score. |
DBotScore.Score | Number | The actual score. |
Domain.Name | String | The domain name. For example, "google.com". |
Domain.Malicious.Vendor | String | The vendor that reported that the domain is malicious. |
Domain.Malicious.Description | String | A description of the malicious domain. |
#
Command Example!domain domain=google.com
#
Context Example#
Human Readable Output#
Domains DGA:
domain probability google.com 0