Note |
---|
Before you begin, Armor recommends that you pre-installation information, including firewall rules. To learn more, see Armor Anywhere Agent 3.0 Pre-Installation. |
...
Step 1: Locate the Armor Anywhere Agent
- In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure.
- Click Virtual Machines.
- Hover over the plus ( + ) icon, and then click the Anywhere Agent icon.
- If you don't have any agents listed, then click Add an Armor Agent.
- Copy your license key. You will need this information in a later step.
- Select your operating system (Linux or Windows).
...
...
Armor
...
Armor recommends installing the Armor Agent with all Security Services. Documentation on installing the Armor Agent only can be found below.
Step 2: Install the Armor Anywhere Agent
Run the command to install the Armor Anywhere Agent with all Security Services.
...
Info |
---|
The Trend Recommendation Scan is not run upon installation, but is instead scheduled to run 10 minutes after installation and then every 7 days after that. |
...
Step 3: Review the status of the Armor Anywhere agent
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Note |
---|
The State of each Armor Service will show Pending for two-hours after installation. After two hours, the State should accurately reflect the health of the service. |
...
Note |
---|
...
To access troubleshooting documentation for each Armor Security Service, click on the name of the service in the sub-agent health table. |
...
Anchor Installing the Armor Anywhere Agent Only Linux
Installing the Armor Anywhere Agent Only Linux |
...
Installing the Armor Anywhere Agent Only Linux
Installing the Armor Anywhere Agent Only Linux |
...
Installing the Armor Anywhere Agent Only
If you need to install the Armor Agent and Armor Security Services one by one, Armor recommends following the specific order outlined below to utilize the benefits of Recommendation Scans.
...
If you do not want to run Recommendation Scans, please review the full list of CLI commands available here.
Optional Agent Only Step 1: Run the command to install the Armor Anywhere agent only.
...
Tip |
---|
You must replace
Currently, all users will leverage the region: |
Optional Agent Only Step 2: Install Armor Security Services
Note | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Step 1: Install Trend Sub-Agent:
Step 2: Turn On File Integrity Monitoring in "Auto-Apply" Mode (This automatically applies FIM rules identified by Recommendation Scans. You must run a Recommendation Scan to identify the FIM rules that will be auto-applied.)
Step 3: Turn On Intrusion Prevention Service in "Auto-Apply" Mode (This automatically applies IPS rules identified by Recommendation Scans. You must run a Recommendation Scan to identify the IPS rules that will be auto-applied.) Option 1: Detect Mode
Option 2: Prevent Mode
Step 4: Install Malware Protection (Anti-Virus)
Step 5: Install Vulnerability Scanning*
*Vulnerability Scaning is a standalone service not included in the Trend Subagent Step 6: Install Logging*
*Logging is a standalone service not included in the Trend Subagent Step 7: Run a Recommendation Scan (This runs the initial Recommendation Scan to apply the baseline rules for FIM and IPS. Recommendations cannot be applied unless FIM and IPS are turned on and running in auto-apply mode.)
Step 8: Turn On Ongoing Recommendation Scans (This automatically runs Recommendation Scans every 7 days. All FIM and IPS rule changes are automatically applied if you followed Steps 2 and 3.)
|
Step 3: Review the status of the Armor Anywhere agent
...
Note |
---|
The State of each Armor Service will show Pending for two-hours after installation. After two hours, the State should accurately reflect the health of the service. |
...
...
Agent Only Step 3: Same as Step 3 in the Full Installation outline above.
...
Troubleshooting
The Armor Agent uses the BiosUUID to identify the hardware that the agent is running on. This number is tied to your motherboard (in the case of a physical computer) but is also present in a Virtual Machine.
...