USM Anywhere runs in either an Amazon Virtual Private Cloud (VPC) or in the classic mode of Amazon Elastic Compute Cloud (Amazon EC2).
|t2.large / m3.large instance||t2. large instance in a virtual private cloud (VPC) or an m3. large in EC2-Classic|
|12-GB EBS volume||Provides short-term storage for your data as it is processed. Recommended volume: 12-GB elastic block store (EBS).|
|Internet connection to the USM Anywhere secure cloud||Review the Sensor Ports and Connectivity for more information|
Important: If you download and deploy the t2 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 instance in EC2-Classic to a t2 instance type.
Application Service Dependencies
With the CloudFormation Template provided by AlienVault, 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.
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.
Note: Initial deployment of a USM Anywhere Sensor requires that you open egress/outbound ports and protocols in the firewall for communication with USM Anywhere and AlienVault cloud resources. After the initial sensor setup, you do not need to open any external inbound ports because the USM Anywhere Sensor receives no inbound connections from outside the firewall.
Communication from the Sensor to the USM Anywhere environment, and from AlienVault for initial setup of the Sensor
Important: Both ingress and egress are required for the initial setup of the Sensor. After the Sensor is connected, you can close all ingress for this port.
|TCP||443||update.alienvault.cloud||Communication with AlienVault for initial setup and future updates of the Sensor|
|TCP||443||reputation.alienvault.com||Ongoing communication with Open Threat Exchange®|
|TCP||443||your USM Anywhere subdomain
|Ongoing communication with USM Anywhere|
|SSL / TCP||7100||your USM Anywhere subdomain
|Ongoing communication with USM Anywhere|
|Synch with NTP services in the AlienVault cloud|
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 Amazon Web Services 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 S3 or CloudWatch).
USM Anywhere normally gives systems explicit access to the AWS API.
We also recommend that you configure outbound connectivity for port 22 and 443 to prod-usm-saas-tractorbeam.alienvault.cloud to support 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 SCP. communications with the USM Anywhere Remote Support server. For more information about remote technical support through the USM Anywhere Sensor console, see Troubleshooting and Remote Sensor Support.
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.
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.
Before you install the AWS sensor, make sure you have the following prerequisites available.
|AWS CloudFormation template provided by AlienVault||
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).