USM Anywhere deploys the through the Google Virtual Private Cloud (VPC) and requires at a minimum the following specifications.
| Requirement | Description |
|---|---|
| n1-standard-2 instance | A standard instance with 2 vCPUs and 7.5 GB of memory. |
|
Zonal SSD persistent disk 50GB |
Persistent disk storage offers reliable network storage that your instances can access like physical disks. A 50GB volume is designated as the default size for optimal performance. |
| Internet connection to the AT&T Cybersecurity Secure Cloud | See Sensor Ports and Connectivity for more information. |
Note: USM Anywhere does not support deploying a GCP Sensor on a shared VPC network.
Important: Because the needs of a sensor differ based on the varying demands of different deployment environments and the complexity of events being processed, the number of events per second (EPS) throughput a sensor can process varies.
Depending on your environment, you may need to deploy additional sensors to ensure that all events are processed.
Application Service Dependencies
With the Google Cloud Deployment Manager Template provided by AT&T Cybersecurity, you can automatically deploy a USM Anywhere Sensor as a service into your environment. Review the following lists for information about the inbound and outbound IP addresses, ports, and services used by USM Anywhere.
Sensor Ports and Connectivity
For USM Anywhere Sensor deployment in the Google Cloud Platform (GCP), the Google Cloud Deployment Manager template automatically creates the firewall rules needed for network connectivity between the instances within the virtual private Cloud (VPC).
Note: The required firewall rules are outlined below.
The following tables list the inbound and outbound ports.
| Type | Ports | Endpoints | Purpose |
|---|---|---|---|
| TCP | 443 | update.alienvault.cloud | Communication with AT&T Cybersecurity for initial setup and future updates of the sensor. |
| TCP | 443 | reputation.alienvault.com | Ongoing communication with AT&T Alien Labs™ Open Threat Exchange® (OTX™). |
| TCP | 443 | otx.alienvault.com | Ongoing communication with OTX to retrieve vulnerability scores. Connecting to otx.alienvault.com is not required but highly recommended. |
| TCP | 443 |
your USM Anywhere subdomain your USM Anywhere subdomain |
Ongoing communication with USM Anywhere. |
| SSL / TCP | 7100 |
your USM Anywhere subdomain your USM Anywhere subdomain |
Ongoing communication with USM Anywhere. |
| UDP | 53 | DNS Servers (Google Default) | Ongoing communication with USM Anywhere. |
| TCP | 22 and 443 |
prod-usm-saas-tractorbeam.alienvault.cloud, prod-gov-usm-saas-tractorbeam.gov.alienvault.us (for AT&T TDR for Gov) |
SSHProgram to securely log into another computer over a network, to execute commands in a remote machine, and to move files from one machine to another through Secure Copy (SCP). communications with the USM Anywhere remote support server. See Troubleshooting and Remote Sensor Support for more information about remote technical support through the USM Anywhere Sensor console. |
| Type | Ports | Purpose |
|---|---|---|
| SSH | 22 | Inbound method for secure remote login from a computer to USM Anywhere. |
| HTTP | 80 | Inbound communication for HTTP traffic. |
| UDP (RFC 3164) | 514 | USM Anywhere collects data through syslog over UDP on port 514 by default. |
| TCP (RFC 3164) | 601 | Inbound communication for reliable syslog service. USM Anywhere collects data through syslog over TCP on port 601 by default. |
| TCP (RFC 5424) | 602 | USM Anywhere collects data through syslog over TCP on port 602 by default. |
| Traffic Mirroring | 4789 | Inbound communication for virtual extensible local area network (VXLAN). |
| TLS/TCP (RFC 3164) | 6514 | USM Anywhere collects Transport Layer Security (TLS)-encrypted data through syslog over TCP on port 6514 by default. |
| TLS (RFC 5424) | 6515 | USM Anywhere collects data through syslog over TLS on port 6515 by default. |
| Graylog | 12201 | Inbound communication for Graylog Extended Log Format (GELF). |
Google Cloud Services
The USM Anywhere Sensor uses the following GCP services:
- Google Stackdriver
- Google Compute Engine
- Google Cloud Pub/Sub
USM Anywhere IP Addresses for Whitelisting
| Code | Name | Reserved Static IP Address Blocks |
|---|---|---|
| ap-northeast-1 | Asia Pacific (Tokyo) | 18.177.156.144/28 |
| ap-south-1 | Asia Pacific (Mumbai) | 3.7.161.32/28 |
| ap-southeast-2 | Asia Pacific (Sydney) | 3.25.47.48/28 |
| ca-central-1 | Canada (Central) | 3.96.2.80/28 |
| eu-central-1 | Europe (Frankfurt) | 18.156.18.32/28 |
| eu-west-1 | Europe (Ireland) | 3.250.207.0/28 |
| eu-west-2 | Europe (London) | 18.130.91.160/28 |
| sa-east-1 | South America (São Paulo) | 18.230.160.128/28 |
| us-east-1 | US East (N. Virginia) | 3.235.189.112/28 |
| us-west-2 | US West (Oregon) | 44.234.73.192/28 |
| us-gov-west-1 | AWS GovCloud (US-West) | 3.32.190.224/28 |
Installation Prerequisites
Before you install the GCP Sensor, make sure you have the prerequisites available in the following table.
| Prerequisites | Description |
|---|---|
| Cloud Deployment Manager template provided by AT&T Cybersecurity |
The Cloud Deployment Manager template automatically creates all required GCP resources for deployment, including an instance, volume, and firewall rules for use by the USM Anywhere Sensor instance. |
| Privileged user account on GCP | To deploy the Cloud Deployment Manager template, you must have a privileged user account in GCP with Compute Engine permissions, permission to create and edit service accounts, as well as write permission to the Cloud Deployment Manager. |
Feedback