Frequently Asked Questions
This page contains a list of questions frequently asked about Automation.
Q: Where is Automation hosted?
A: The Automation components of Cisco XDR are hosted in Amazon Web Services. The AWS region depends on which instance of Cisco XDR you are using. For more information about AWS regions and Cisco XDR privacy, please visit the Cisco Trust Portal and view the Cisco XDR Privacy Data Sheet.
Q: Can you provide a list of source IPs for Automation nodes?
A: The source IP addresses (outbound) used by Automation are:
| Region | Source IP Addresses |
|---|---|
|
Asia Pacific, Japan, China (APJC) |
13.230.182.244, 18.181.14.110, 35.72.117.19 |
|
Europe (EU) |
3.251.20.134, 52.48.136.126, 63.33.97.243 |
|
North America (NAM) |
18.213.248.192, 54.166.136.151, 54.211.175.37 |
Q: How do I connect Automation to my on-premises devices?
A: You can use the Automation Remote to integrate on-premises resources into your workflows. See the Remotes Help topic for more information.
Q: What Python modules are available?
A: See Python Activities for a list of Python scripts that are supported in Automation.
Q: Can I install custom Python modules?
A: No. Python scripts in Automation run inside a container that cannot be customized.
Q: How do I make a workflow appear in the Cisco XDR ribbon or product pivot menus?
A: Create the workflow using the Pivot Menu Workflow template, which adds the workflow to the pivot menu of any observable in Cisco XDR matching the type(s) you selected. See the Create a Workflow Help topic for more information.
Q: How long are workflow execution logs kept?
A: Workflow execution logs (runs) are kept for 90 days, the default data retention period. You can purchase additional retention periods of 180 or 365 days. Data for atomic and sub-workflows is retained for 30 days. For more information about data retention, please visit the Cisco Trust Portal and view Section 6 of the Cisco XDR Privacy Data Sheet.
Q: What if I see the upstream connect error or disconnect/reset before headers. reset reason: connection termination error message?
A: Clear your cache and cookies, and try again. This is a known issue.