USM Anywhere deploys the Amazon Web Services (AWS) Sensor in the Amazon Elastic Compute Cloud (EC2) platform through either the Amazon Virtual Private Cloud (VPC) or the Amazon EC2-Classic flat network.
|m3.large / m5.large instance||An m5.large instance in an Amazon VPC, or an m3.large in the Amazon EC2-Classic network.|
100GB EBS volume
The Amazon Elastic Block Store (EBS) provides short-term storage for your data as it is processed.
A 100GB Amazon EBS 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.
Important: If you download and deploy the m5.large instance, you must launch it into a VPC; this instance type is not supported on the Amazon EC2-Classic platform.
You cannot change the instance type of an existing t2.large or m3.large instance in Amazon EC2-Classic to an m5.large VPC instance. If you need to change instance type, you need to redeploy the sensor.
AWS Deployment Regions
The AWS Sensor will be deployed on one of the following AWS endpoint regions based on your location. The following table lists the code and name of each region. These are the available regions:
|ap-northeast-1||Asia Pacific (Tokyo)|
|ap-northeast-2||Asia Pacific (Seoul)|
|ap-south-1||Asia Pacific (Mumbai)|
|ap-southeast-1||Asia Pacific (Singapore)|
|ap-southeast-2||Asia Pacific (Sydney)|
|sa-east-1||South America (São Paulo)|
|us-east-1||US East (N. Virginia)|
|us-east-2||US East (Ohio)|
|us-west-1||US West (N. California)|
|us-west-2||US West (Oregon)|
Application Service Dependencies
With the AWS CloudFormation Template provided by AT&T Cybersecurity, you can automatically deploy USM Anywhere as a service into your environment. Review the following tables for information about the outbound/inbound IP addresses, ports, and services used by USM Anywhere.
Before you deploy a USM Anywhere Sensor, you must configure your firewallVirtual or physical device designed to defend against unauthorized access to data, resources, or a private network. A firewall’s primary purpose is to create segregation between two or more network resources, blocking undesirable traffic between them. permissions to enable the required connectivity for the new sensor. Initial deployment of a sensor requires that you open egress and outbound ports and protocols in the firewall for communication with USM Anywhere and AT&T Cybersecurity Secure Cloud resources. The sensor receives no inbound connections from outside the firewall.
Note: To launch the USM Anywhere Sensor web user interface (UI) during the initial setup, you need to allow inbound traffic to the sensor IP address through TCP port 80. You can remove access to this port after the sensor successfully connects to USM Anywhere. You do not need to allow inbound traffic to this port from the Internet.
|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.
Important: A USM Anywhere Sensor deployed in AWS might require outbound access to specific AWS resources, based on the sensor app in use. For example, the AWS sensor app must have the ability to connect to the AWS API (port 443). However, the actual API endpoint might be different depending on the service (such as Amazon Simple Storage Service [S3] or Amazon CloudWatch).
USM Anywhere normally gives systems explicit access to the AWS API.
USM Anywhere cannot deploy the AWS Sensor in an AWS GovCloud region.
|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).|
Security Groups in Your AWS VPC
For sensor deployment in an AWS VPC, the AWS CloudFormation template automatically creates the security groups needed for network connectivity between the instances within the VPC. However, this does require that you manually assign the USMServicesSG security group to your hosts to enable access to the UDP port 514 so that the sensor can receive syslog packet transmissions.
See Enabling Connections in an AWS VPC for more detailed information about these security groups.
USM Anywhere uses the following AWS services:
- Amazon CloudWatch
- AWS CloudTrail
- AWS Elastic Load Balancing (ELB)
- Amazon S3
- Amazon EC2
- AWS Identity and Access Management (IAM)
- Amazon GuardDuty
- Amazon Relational Database Service (RDS)
See IAM Roles and Permissions Required by Your AWS Sensor for a full description of the IAM roles and permissions that your AWS Sensor requires for these AWS services.
Note: USM Anywhere uses us-east-1 as a default region in the amazon-aws app. As a result, you might want to verify whether your Sensors are communicating with us-east-1, even if you have never deployed to that region.
Before you install the AWS Sensor, make sure you have the following prerequisites available.
|AWS CloudFormation template provided by AT&T Cybersecurity||
The AWS CloudFormation template automatically creates all required AWS resources for deployment, including an IAM role and instance profile for use by the USM Anywhere Sensor instance.
URLs for these templates are included in the Deploying the AWS Sensor instructions.
|Privileged user account on AWS||To deploy the AWS CloudFormation template, you must have a privileged user account in AWS with permissions to create IAM resources.|
Multiple AWS Accounts or Amazon VPCs
If you have multiple AWS accounts, you must deploy the AWS Sensor in each AWS account that you want to monitor.
Amazon VPC enables you to launch AWS resources into a virtual network that you've defined. A single sensor can monitor an entire AWS account, even when it contains multiple Amazon VPCs.
Note: If you intend to use the USM Anywhere vulnerabilityA known issue or weakness in a system, procedure, internal control, software package, or hardware that could be used to compromise security. scanner with the AWS Sensor, you must allow traffic from the sensor and the target instance you are scanning. You can usually accomplish this by using Amazon VPC peering (see the AWS documentation for more information).