Link Search Menu Expand Document

Frequently Asked Questions

This page contains a list of frequently asked questions about SecureX orchestration. FAQs for the broader SecureX platform can be found here.


Q: Where is SecureX orchestration hosted?

A: The orchestration components of SecureX are hosted in Amazon Web Services. The AWS region depends on which instance of SecureX you’re using. For more information about AWS regions and SecureX privacy, please visit the Cisco Trust Center

Q: Do you provide a list of source IPs/hostnames for orchestration nodes?

A: Please see the following table for the source IPs used by SecureX orchestration:

Region Source IPs
Asia Pacific (APJC) 18.181.14.110
13.230.182.244
35.72.117.19
Europe (EU) 52.48.136.126
63.33.97.243
3.251.20.134
North America (NAM) 54.166.136.151
18.213.248.192
54.211.175.37

Q: How do I connect to on-premises devices?

A: You can use the SecureX orchestration remote to integrate on-premises resources into your workflows. Check out this page for more information.

Q: What Python modules are available?

A: See the Python Modules page.

Q: Can I install custom Python modules?

A: No. Python scripts in SecureX orchestration run inside a container that can’t be customized.

Q: How do I make a workflow appear in Threat Response/SecureX ribbon/product pivot menus?

A: See the Response Workflows page.

Q: How long are workflow execution logs kept?

A: Workflow execution logs, also known as runs, are kept for 90 days.


Table of contents