Requirements for GCP Sensor Deployment

USM Anywhere deploys the Google Cloud Platform (GCP) Sensor through the Google Virtual Private Cloud (VPC) and requires at a minimum the following specifications.

VPC Minimum 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) 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.

Sensor Ports and Connectivity (Outbound Ports)
Type Ports Endpoints Purpose
TCP 443 Communication with AT&T Cybersecurity for initial setup and future updates of the sensor.
TCP 443 Ongoing communication with AT&T Alien Labs™ Open Threat Exchange® (OTX™).
TCP 443

Ongoing communication with OTX to retrieve vulnerability scores. Connecting to is not required but highly recommended.

OTX uses the AWS Cloudfront services. Refer to the AWS IP address ranges page when you deploy a new sensor. This page contains the current IP address ranges for the service and instructions on how to filter the addresses.

TCP 443

Your USM Anywhere subdomain

Your USM Anywhere subdomain (for AT&T TDR for Gov)

Ongoing communication with USM Anywhere.
SSL/TCP 7100

Your USM Anywhere subdomain

Your USM Anywhere subdomain (for AT&T TDR for Gov)

Ongoing communication with USM Anywhere.
UDP 53 DNS Servers (Google Default) Ongoing communication with USM Anywhere.
UDP 123

Sync with NTP services.
TCP 22 and 443 (for AT&T TDR for Gov)

SSH Program to securely log into another computer over a network, execute commands in a remote machine, and 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.

TCP 443

Allows resolution of IP addresses for geolocation services.

It is only necessary to allow list the GeoIP address that corresponds to the region where your USMA instance is hosted.

Sensor Ports and Connectivity (Inbound Ports)
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).
WSMANS 5987 Inbound WBEM WS-Management HTTP over Secure Sockets Layer/Transport Layer Security (SSL/TLS) (NXLog).
TLS/TCP (RFC 3164) 6514 USM Anywhere collects 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.
TCP 9000 Inbound communication used internally for HTTP sensor traffic.
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 Allowlisting

Your sensor is connected to a USM Anywhere instance deployed in one of the Amazon Web Services (AWS) endpoint regions based on your location. If you need to configure your firewall to allow communication between the sensor and the USM Anywhere instance, refer to the following table with the reserved IP address ranges for each region.

Important: The Update Server and the AlienVault Agent always use the range no matter where your USM Anywhere is deployed. The AT&T TDR for Gov Update Server uses the range.

The regional IP ranges listed in this table are limited to the Control Nodes (subdomain). You must also meet all requirements provided in the Sensor Ports and Connectivity (Outbound Ports) table.
AWS Regions Where USM Anywhere Instance Is Available
Code Name Reserved Static IP Address Ranges
ap-northeast-1 Asia Pacific (Tokyo)

ap-south-1 Asia Pacific (Mumbai)

ap-southeast-1 Asia Pacific (Singapore)

ap-southeast-2 Asia Pacific (Sydney)

ca-central-1 Canada (Central)

eu-central-1 Europe (Frankfurt)

eu-west-1 Europe (Ireland)

eu-west-2 Europe (London)

me-central-1 Middle East (UAE)

sa-east-1 South America (São Paulo)

us-east-1 US East (N. Virginia)

us-west-2 US West (Oregon)

us-gov-west-1 AWS GovCloud (US-West)

Installation Prerequisites

Before you install the GCP Sensor, make sure you have the prerequisites available in the following table.

Installation Prerequisites
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.