AlienVault® USM Anywhere™

Requirements for AWS Sensor Deployment

USM Anywhere deploys the AWS Sensor in the Amazon Elastic Compute Cloud (Amazon EC2) platform through either Amazon's Virtual Private Cloud (VPC) or the EC2-Classic flat network.

Requirement Description
m3.large / m5.large instance An m5.large instance in a VPC, or an m3.large in EC2-Classic network.

100GB EBS volume

The Elastic Block Store (EBS) provides short-term storage for your data as it is processed.

A 100GB 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: If you download and deploy the m5.large instance, you must launch it into a virtual private cloud (VPC); this instance type is not supported on the EC2-Classic platform.

You cannot change the instance type of an existing t2.large or m3.large instance in EC2-Classic to a m5.large VPC instance. If you need to change instance type, you need to redeploy the sensor.

Application Service Dependencies

With the CloudFormation Template provided by AT&T Cybersecurity, you can automatically deploy USM Anywhere as a service into your environment. Review the following lists for information about the outbound/inbound IP addresses, ports, and services used by USM Anywhere.

Sensor Ports and Connectivity

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.

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.

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.

Type Ports Inbound/Outbound Endpoints Purpose
TCP 443 Outbound update.alienvault.cloud Communication with AT&T Cybersecurity for initial setup and future updates of the Sensor
TCP 443 Outbound reputation.alienvault.com Ongoing communication with Open Threat Exchange® (OTX)
TCP 443 Outbound your USM Anywhere subdomain
.alienvault.cloud
Ongoing communication with USM Anywhere
SSL / TCP 7100 Outbound/Inbound your USM Anywhere subdomain
.alienvault.cloud
Ongoingand Incoming communication with USM Anywhere
UDP 53 Outbound DNS Servers (Google Default) Ongoing communication with USM Anywhere
UDP 123 Outbound

0.amazon.pool.ntp.org

1.amazon.pool.ntp.org

2.amazon.pool.ntp.org

3.amazon.pool.ntp.org

Synch with network time protocol (NTP) services in the AT&T Cybersecurity Secure Cloud
UDP 123 Outbound

time1.google.com

time2.google.com

time3.google.com

time4.google.com

Synch with network time protocol (NTP) services in the AT&T Cybersecurity Secure Cloud
TCP 22 and 443 Outbound 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 Amazon Web Services (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 S3 or CloudWatch).

USM Anywhere normally gives systems explicit access to the AWS API.

USM Anywhere cannot deploy the AWS sensor in an AWS GovCloud region.

Security Groups in Your VPC

For Sensor deployment in an AWS VPC, the 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.

For more detailed information about these security groups, see Enabling syslog Connections in an AWS VPC.

AWS Services

USM Anywhere uses the following AWS services:

  • AWS CloudWatch
  • AWS CloudTrail
  • Elastic Load Balancing
  • Amazon Simple Storage Service (AWS S3)
  • Amazon EC2
  • AWS Identity and Access Management (IAM)

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 or not your Sensors are communicating with us-east-1, even if you have never deployed to that region.

Installation Prerequisites

Before you install the AWS sensor, make sure you have the following prerequisites available:

Prerequisites Description
AWS CloudFormation template provided by AT&T Cybersecurity

The 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 CloudFormation template, you must have a privileged user account in AWS with permissions to create Identity and Access Management (IAM) resources.

Multiple Accounts or 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 virtual private clouds (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 VPC peering (see the AWS documentation for more information).