For customers migrating from another tool or platform, you can reference our documentation for uninstalling Alert Logic Endpoint Protection or Sophos Endpoint Security.
Resource Requirements
*Minimum required for installation. VMs might require more memory per your installation configuration.
Requirement | Windows Instance | Linux Instance |
|---|---|---|
CPU | 2 Cores | 1 Core |
RAM | 2GB | 1GB* |
Disk Space | 3GB | 3GB |
Bandwidth | Estimated 50-100Kb per minute, based on the logs generated in your system. | |
Cronie | For Amazon Linux 2023 only | |
TLS 1.2 is required to install the Armor Anywhere Agent 3.0.
For more information on TLS 1.2, please visit Microsoft's documentation.
Operating System Compatibility
Operating System | Supported Version for 64-bit Environments Only | AWS Graviton |
|---|---|---|
CentOS |
|
|
Red Hat Enterprise Linux (RHEL) |
|
|
Ubuntu |
|
|
Amazon Linux |
|
|
Oracle Linux |
| |
SUSE Linux Enterprise Server |
| |
Windows |
Installing the Armor Anywhere agent for Windows requires Powershell v.3 or higher. | |
Debian |
| |
Alma |
| |
Rocky |
| |
MacOS |
|
For Windows users, in order to run the install script, you will need to ensure your execution policy allows for the execution of scripts.
You can check by executing the following command in Powershell
Get-ExecutionPolicy -List
If the ExecutionPolicy is set to AllSigned or RemoteSigned for LocalMachine, let's UnBlock it for the script installation by adding the UnBlock command to the installation one-liner
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest https://agent.armor.com/latest/armor_agent.ps1 -outfile armor_agent.ps1 ; Unblock-File -Path .\armor_agent.ps1 ; .\armor_agent.ps1 -license 1AAAA-AAAAA-AAAAA-AAAAA-AAAAA -region us-west
Linux Kernels Compatibility
This document lists the specific Linux kernels supported for each Linux Operating System and Architecture:
Trend Deep Security 20.0 Supported Linux Kernels
Browser Support
The Armor Management Portal (AMP) supports the current version of the following browsers:
Chrome
Firefox
Internet Explorer
Safari
Armor cannot guarantee that previous browser versions will be supported.
Firewall Rules
This topic only applies to Armor Agent for Servers (Armor Anywhere) users.
The following ports will need to be opened for each server registered with Armor.
Armor Agent Services
Traffic | Service | Port | Destination |
|---|---|---|---|
Outbound | Armor Agent |
|
|
Outbound* | Malware Protection, FIM, IDS |
|
DNS resolves these URLs:
|
Outbound (for Rackspace users) | Malware Protection, FIM, IDS |
|
DNS resolves these URLs:
|
Outbound | Vulnerability Scanning |
|
|
Outbound | Log Management (Filebeat / Winlogbeat) |
|
|
*for Armor Direct or Armor Partner customers
For Log Relay, the following additional ports will need to be opened for each server registered with Armor.
Log Relay Services
Traffic | Service | Port | Destination |
|---|---|---|---|
Inbound | Log Relay (Logstash) |
|
|
Outbound | Log Relay (Armor's logging service (ELK)) |
|
|
To verify connectivity to an Armor service endpoint, use the telnet command.
The following example tests connectivity to api.armor.com over 443/tcp:
telnet 75.2.84.73 443
For Windows systems without the telnet feature installed, you can also use PowerShell:
new-object System.Net.Sockets.TcpClient('75.2.84.73', 443)
Remove Anti-Virus Software
If you intend to use the Anti-Virus module, you must remove any previously installed anti-virus software, such as Trend Micro, SentinelOne, McAfee, etc.
Afterwards, you must reboot your system.
After you install the agent, Armor recommends that you test the connection for each configured firewall rule.