Requirements for Alert Logic Threat Manager for SoftLayer

United States firewall rules

Use the following rules to communicate with the US Data Center.

Appliance inbound

(missing or bad snippet)

Appliance outbound

SourceDestinationProtocolPortDescription
Appliance8.8.4.4TCP/UDP53DNS
Appliance 8.8.8.8TCP/UDP53DNS
Appliance 0.0.0.0/0TCP80Appliance updates
Appliance204.110.218.96/27TCP443Updates
Appliance204.110.219.96/27TCP443Updates
Appliance208.71.209.32/27TCP443Updates
Appliance208.71.209.32/27TCP4138Event transport
Appliance204.110.218.96/27TCP4138Event transport
Appliance204.110.219.96/27TCP4138Event transport
Appliance204.110.219.96/27UDP123NTP, time sync
Appliance208.71.209.32/27UDP123NTP, time sync

Agent outbound

SourceDestinationProtocolPortDescription
Protected host208.71.209.32/27TCP443Agent updates (direct)
Protected host204.110.218.96/27TCP443Agent updates (direct)
Protected host204.110.219.96/27TCP443Agent updates (direct)
Protected hostApplianceTCP443Agent updates (single point egress)
Protected hostApplianceTCP7777Agent data transport (between agent and appliance on local network)

European Union firewall rules

Use the following rules to communicate with the EU Data Center.

Appliance inbound

SourceDestinationProtocolPortDescription
Agent(s) CIDR- network subnet range for the agent(s)ApplianceTCP443Agent updates
Agent(s) CIDR- network subnet range for the agent(s)ApplianceTCP7777Agent data transport (between agent and appliance on local network)
0.0.0.0/0ApplianceTCP80Appliance claim
185.54.124.0/24ApplianceTCP4849Appliance user interface (Web Security Manager)
185.54.124.0/24 ApplianceTCP22Optional and temporary- required for troubleshooting during provisioning only
Port 22 is required for troubleshooting during the provisioning process only. After the provisioning process is complete, you may close the port.

Appliance outbound

SourceDestinationProtocolPortDescription
Appliance185.54.124.0/24TCP443Updates
Appliance185.54.124.0/24TCP4138Event transport
Appliance8.8.8.8TCP/UDP53DNS
Appliance8.8.4.4TCP/UDP53DNS
Appliance0.0.0.0/0TCP80Appliance updates
Appliance185.54.124.0/24UDP123NTP, time sync

Agent outbound

SourceDestinationProtocolPortDescription
Protected hostApplianceTCP7777Agent data transport (between agent and appliance on local network)
Protected host185.54.124.0/24TCP443Agent updates (direct)
Protected hostApplianceTCP443Agent updates (single point egress)

Cloud server size recommendations

Threat Manager runs on select compute instance types in the SoftLayer public cloud. Review the table below for more information:

Instance typeCoresMemory (GB)Throughput - no scanningThroughput - scanning enabled
1x2.0 GHz1130 MbpsSupported, however, may result in degraded threat detection while scans are in progress.
2x2.0 GHz cores22150 MbpsSupported, however, may result in degraded threat detection while scans are in progress.
4x2.0 GHz cores415300 Mbps150 Mbps
8x2.0 GHz cores881 Gbps825 Mbps

Ports settings

Unless you have a firewall in front of the environment, you do not need to set up ports nor create ACL entries for Threat Manager in the SoftLayer environment. Review the United States firewall rules firewall rules.

Regions

A region is a logical data center (one or more physical data centers) that features a low latency, high bandwidth interconnecting network. Regions are designated by the nearest airport code, such as DFW, IAD, ORD, LON, HKG, and SYD.

Location considerations

Appliances and agents must be located in the same region. Only cloud servers and services that are part of the same region can access each other. Services outside the region have no way to identify or connect to services hosted in other regions, unless specific ports are opened for external Internet sources.

If you have cloud servers in multiple regions, create an appliance and agent in each region.

Installation considerations

Image sharing can only occur within the same region. For example, you cannot share an image in the ORD region for later use in the SYD region. If your image is in IAD, and you share this image with another user, that user will only be able to build servers from the image in the IAD region. For installation purposes, Alert Logic maintains a virtual appliance image in each region.

For more information, see SoftLayer Image Templates.

Virtual appliance

The following table describes the basic system requirements to install a Threat Manager virtual appliance:

ComponentsSystem Requirements
CPU 4 virtual CPUs
RAM8 GB
Disk space40 GB minimum
Supported virtual environmentVMware only
Log collection supportN/A
EncryptionTLS Standard (SSL): 1024–2048bit key encryption, 256bit AES bulk encryption

This is the recommended basic configuration for the Threat Manager product when deployed on a virtual appliance. Bandwidth volume directly impacts the ability of the appliance to inspect traffic. Therefore, high traffic environments may require a virtual machine with additional processor and memory resources.

If you want to run scans, consider 8 virtual CPUs (cores) and 16 GB of memory.

Alert Logic agent

The following table describes the basic requirements to install the agent:

ComponentsSystem requirements
Operating systemsFor Windows users:
  • Windows Server 2016
  • Windows 10
  • Windows Server 2003, SP1
  • Windows Server 2008
  • Windows Server 2012
  • Windows Vista
  • Windows 7
  • Windows 8
  • Windows XP SP1

For Linux users:
Debian (.deb)
  • 5.x (lenny)
  • 6.x (squeeze)
  • 7.x (wheezy)
  • 8.x (jessie)

Ubuntu (.deb)
  • 10.x
  • 12.x
  • 14.x
  • 16.x

CentOS (.rpm)
  • 5.x
  • 6.x
  • 7.x

Red Hat Enterprise Linux (.rpm)
  • 5.x
  • 6.x
  • 7.x

SUSE
  • 12.1
  • 12.0
  • 11.4
  • 11.3

Amazon Linux

The Alert Logic agent can be used in AWS Workspaces in conjunction with a supported operating system.

Memory96 MB of available memory
Disk space for agent30 MB of available disk space
Disk space for local cache500 MB of available disk space
Packet accessWinPcap 4.1.2
CPU Utilization1-10% depending on log volume
RAM15 MB minimum
Disk space30 MB minimum
Log collection supportWindows, Flat File
Supported environmentsAgent-only deployments with virtual and physical appliances, VPC, and Public Clouds
EncryptionTLS Standard (SSL): 2048-bit key encryption, 256-bit AES bulk encryption
Log collection frequencyAt minimum, every five minutes logs are collected and sent to Alert Logic Cloud
Host permissionsLocalSystem account has all the necessary permissions by default

The agent requires DNS access to communicate with the Alert Logic server.

Operating systems and browser support

The Alert Logic console supports the current version and the previous major version of the following operating systems and browsers: 

Operating system supportBrowser support
Mac, Linux, and WindowsChrome, Safari, Firefox, Opera, and Internet Explorer

Alert Logic cannot guarantee that other browsers and versions will work with our product.

Related topics