Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Armor Knowledge Base


Feedback

Have a suggestion for the Armor Knowledge Base?

Send a message to kb@armor.com.









Error rendering macro 'excerpt-include'

No link could be created for 'Armor Management Portal (AMP) Only (snippet)'.

Overview

The Security Dashboard in the Armor Management Portal (AMP) displays the various statuses of your virtual machines: 

  • Green indicates a virtual machine in a Secured status.
  • Yellow indicates a virtual machine in a Warning status. 
  • Red indicates a virtual machine in a Critical status.

Virtual Machine status

Error rendering macro 'excerpt-include'

No link could be created for 'View and delete offline virtual machines (snippet)'.

The overall status of your virtual machine is based on the individual status of your virtual machine's subcomponents. Your virtual machine contains three subcomponents:

  • Anti-Malware
  • FIM
  • Patching

Armor reviews the status of your three subcomponents and labels your virtual machine based on the status of your most critical subcomponent.

For example, if Anti-Malware and FIM are both in a Secured status, but Patching is in a Critical status, then overall, your virtual machine is labeled as Critical.

In another example, if Anti-Malware is in a Critical status, FIM is in a Warning status, and Patching is in a Secured status, then overall, your virtual machine is labeled as Critical


Anti-Malware status

The Anti-Malware status can change based on the following two conditions:

  • The date of your last scan
  • The date that Armor last received your data

Condition 1 - Date of last scan

If the last scan for Anti-Malware took place between 7 to 13 days ago, then the Anti-Malware status changes from Secured to Warning.

If the last scan for Anti-Malware took place 14 days ago or more, then the Anti-Malware status changes from Warning to Critical.

Date of last scanSecurity status
7 to 13 days agoWarning
14 days or moreCritical

 


Condition 2 - Date that Armor last received your data

If Armor last received data between 24 to 48 hours ago, then the Anti-Malware status changes from Secured to Warning.

If Armor last received data over 48 hours ago, then the Anti-Malware status changes from Warning to Critical.

 

Date of Armor receiving your dataSecurity status
24 to 48 hours agoWarning
Over 48 hoursCritical

 

Armor labels the Anti-Malware status based on the worst status of the two conditions. For example, if the date of your last scan was 9 days ago, but Armor last received your data 72 hours ago, then overall, the Anti-Malware status is Critical


Troubleshoot Anti-Malware

Armor troubleshoots virtual machines that contain Anti-Malware subcomponents in a Warning or Critical status. To troubleshoot with Armor, you must submit a support ticket.

  1. In the Armor Management Portal (AMP), at the bottom, click New
  2. Click Ticket
  3. In Ticket Subject, enter a descriptive name. 
  4. In Add Recipient, enter the email address of additional users who should receive support updates. 
  5. In Ticket Explanation, enter useful details that can help Armor troubleshoot the problem quickly, especially the name of the virtual name. 
  6. Click Attach File to add relevant images of your issue, such as the code or error message. 
  7. Click Create Ticket
  8. To view the status of your ticket, in the left-side navigation, click Support, and then click Tickets + Notifications

 


FIM status

Armor determines the status of FIM based on how long FIM has been offline.

  • If FIM is offline for 2 to 7 days, then the FIM status changes from Secured to Warning
  • If FIM is offline for 8 days or more, then the FIM status changes from Warning to Critical

Length of offline statusSecurity Status
2 to 7 daysWarning
8 days or moreCritical

 


Troubleshoot FIM 

Armor troubleshoots virtual machines that contain FIM subcomponents in a Warning or Critical status. To troubleshoot with Armor, you must submit a support ticket.

  1. In the Armor Management Portal (AMP), at the bottom, click New
  2. Click Ticket
  3. In Ticket Subject, enter a descriptive name. 
  4. In Add Recipient, enter the email address of additional users who should receive support updates. 
  5. In Ticket Explanation, enter useful details that can help Armor troubleshoot the problem quickly, especially the name of the virtual name. 
  6. Click Attach File to add relevant images of your issue, such as the code or error message. 
  7. Click Create Ticket
  8. To view the status of your ticket, in the left-side navigation, click Support, and then click Tickets + Notifications

Patching status

Error rendering macro 'excerpt-include'

No link could be created for 'Patching (snippets)'.