| 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. |
...
- 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).
...
Step 2: Install the Armor Anywhere Agent
Armor recommends installing the Armor Agent with all Security Services. Run the command to install the Armor Anywhere Agent with all 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.)
|
...
| Note |
|---|
To access troubleshooting documentation for each Armor Security Service, click on the name of the service in the sub-agent health table. |
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.
In rare cases, the usual calls to retrieve this identifier fail to return this UUID, which will cause the Armor Agent to fail registration.
Turn on Armor Agent debug logging and try to register again. If the registration fails again, search the log for "Unable to get BiosUUID"
| Code Block | ||
|---|---|---|
| ||
time="2020-07-24T03:06:48-05:00" level=debug msg="Unable to get BiosUUID"
time="2020-07-24T03:06:50-05:00" level=debug msg="Unable to get BiosUUID" |
In Linux, try this command to try to retrieve the UUID:
| Code Block | ||
|---|---|---|
| ||
sudo dmidecode |grep UUID |
Any of the above commands should return a 35byte string formatted like:
| Code Block | ||
|---|---|---|
| ||
4C4C7544-0057-4C30-8046-C2C04F4C9132 |
The BIOS UUID is required by the Armor Agent, to ensure uniqueness of the device. The BIOS UUID must be readable by the operating system. If the BIOS UUID is not available to the operating system please check with your provider.
Related Documentation
...