Use this guide to review external connections that are required for certain Secure Network Analytics features to operate expeditiously. These external connections can be domains or endpoints. Domains are names used for identifying resources on the internet, usually websites or services; and endpoints are actual devices or nodes that communicate across a network. Since the focus for this guide is web services, these are shown as URLs. The table lists the external connection URLs in alphabetical order.
| External Connection URL | Purpose |
|---|---|
| https:// |
Used by Secure Network Analytics for telemetry data exchange with Secure Cloud Analytics services. |
| https: |
Required by Cisco for data transit to Amazon Web Services (AWS) for the Asia Pacific, Japan, and China (APJC) region. Used when forwarding alerts to Cisco XDR and also for customer service metrics. |
| https:// |
Required by Cisco for data transit to Amazon Web Services (AWS) for the Europe (EU) region. Used when forwarding alerts to Cisco XDR and also for customer service metrics. |
| https:// |
Required by Cisco for data transit to Amazon Web Services (AWS) for the United States (US) region. Used when forwarding alerts to Cisco XDR and also for customer service/success metrics. |
| https:// |
Used by Secure Network Analytics for the Direct Software Downloads feature. |
| https: |
Required for the sending and collection of customer success metrics |
| https: |
Required for the sending and collection of customer success metrics |
| https: |
Required for the sending and collection of customer success metrics |
| https:// |
Required by Threat Feed, which is used for Secure Network Analytics alerts and observations, when Analytics is enabled. |
| https:// |
Used by Secure Network Analytics for the Direct Software Downloads feature. |
| https:// |
Required by Threat Feed, which is used for Secure Network Analytics alerts and observations, when Analytics is enabled. |
| https:// |
Required by Threat Feed, which is used for Secure Network Analytics alerts and observations, when Analytics is enabled. |
| https:// |
Required by Secure Network Analytics Threat Intelligence Feed, which is used for Secure Network Analytics alarms and security events. This requires the Secure Network Analytics Threat Intelligence Feed license. |
| https: |
Required for the sending and collection of customer success metrics |
| https:// |
Allows for accessing MITRE information for alerts when Analytics is enabled. |
| https:// |
Allows for accessing MITRE information for alerts when Analytics is enabled. |
| https:// |
Allows access to MITRE information for alerts when Analytics is enabled. |
| https:// |
Required Threat Feed, which is used for Secure Network Analytics alerts and observations, when Analytics is enabled. |
| https:// |
Required Threat Feed, which is used for Secure Network Analytics alerts and observations, when Analytics is enabled. |
| https:// |
Required by Cisco for data transit to Amazon Web Services (AWS) for the Asia Pacific, Japan, and China (APJC) region. Used when forwarding alerts to Cisco XDR and also for customer service metrics. |
| https:// |
Required by Cisco for data transit to Amazon Web Services (AWS) for the Europe (EU) region. Used when forwarding alerts to Cisco XDR and also for customer service metrics. |
| https:// |
Required by Cisco for data transit to Amazon Web Services (AWS) for the United States (US) region. Used when forwarding alerts to Cisco XDR and also for customer service metrics. |
| https:// |
Used to access Cisco Smart Software Licensing. Refer to the Smart Licensing Guide for details. Alternative offline licensing is available, if preferred. Refer to the Release Notes for details. |
| https:// |
Used by Secure Network Analytics for the Direct Software Downloads feature. |
| https:// |
Used by Secure Network Analytics for the Direct Software Downloads feature. |
| https:// |
Required for the Cisco domain, which is used for Smart Licensing, cloud proxy, and firewall connection tests. |
To further assess how and why specific domain and endpoint connections are used, see:
SSE endpoints are used for data transit to Amazon Web Services (AWS), by Cisco for your service metrics, and when forwarding alerts to Cisco XDR. They vary based on Region and Hosts. Endpoints are discovered dynamically using a Service Discovery mechanism provided by the SSE Connector. When publishing detections to Cisco XDR, Secure Network Analytics attempts to discover a service titled "xdr-data-platform" and its API endpoint "Events."
Depending on the region in production environments, these are the hosts:
US
EU
APJC
The Direct Software Downloads feature uses these connections:
To use this new feature to download software and patch update files directly to your Update Manager, make sure you've registered using your cisco.com user ID (CCOID).

For more information about Direct Software Downloads, contact Cisco Support.
The MITRE ATT&CK® Framework is a publicly available knowledge base of adversary tactics and techniques based on real-world observations. When you've enabled Analytics within Secure Network Analytics, MITRE tactics and techniques assist with cybersecurity threat intelligence, detection, and response.

The following connections allow Secure Network Analytics to access MITRE information for alerts:
The Cisco Secure Network Analytics Threat Feed (formerly Stealthwatch Threat Intelligence Feed) provides data from the global Threat Feed about threats to your network. The feed updates frequently and includes IP addresses, port numbers, protocols, host names, and URLs known to be used for malicious activity. The following host groups are included in the feed: command-and-control servers, bogons, and Tors.
To enable Threat Feed in Central Management, follow the instructions in the Help.
1. Log in to your primary Manager.
2. Select Configure > Global > Central Management.
3. Select the (Help) icon and then Help.
4. Select Appliance Configuration > Threat Feed.

For more information about Threat Feed, refer to the System Configuration Guide.
For technical support:
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Oct-2025
|
Initial Release |