USM Anywhere deploys the Google Cloud Platform (GCP) Sensor through the Google virtual private cloud (VPC) and requires at a minimum the specifications below:
|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 USM Anywhere secure cloud||Review the Sensor Ports and Connectivity for more information.|
Important: Because the needs of a sensor differs 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 will vary.
Depending on your environment, you may need to deploy additional sensors to ensure that all events are processed.
Application Service Dependencies
With the 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.
For USM Anywhere Sensor deployment in the Google Cloud Platform (GCP), the 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.
|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 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
|Ongoing communication with USM Anywhere.|
|SSL / TCP||7100||your USM Anywhere subdomain
|Ongoing communication with USM Anywhere.|
|UDP||53||DNS Servers (Google Default)||Ongoing communication with USM Anywhere.|
|Sync with network time protocol (NTP) services in the AT&T Cybersecurity Secure Cloud.|
|TCP||22 and 443||prod-usm-saas-tractorbeam.alienvault.cloud||
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.
|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).|
The USM Anywhere Sensor uses the following GCP services:
- Google Compute Engine
- Google Cloud Pub/Sub
Before you install the GCP Sensor, make sure you have the following prerequisites available:
|Cloud Deployment Manager template provided by AT&T Cybersecurity||
The 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 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 Deployment Manager.|