Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note
Home > Armor Anywhere - Product User Guide > Protection dashboard (Armor Anywhere)

...

In the Protection screen, the Protection score focuses on the stability of Armor services to determine if 

  • The agent is responding (hearbeating) to Armor
  • The agent has registered properly

For Armor Anywhere, the Protection scores focuses on the following services:  

  • Malware Protection
  • FIM
  • IDS
  • Filebeat (for Windows and Linux)
  • Winlogbeat (for Windows)
  • Vulnerability Scanning

Review Widgets and Graph 

Widget and Graph Type

Description

Protection Score

This widget displays a calculated score that includes the number of subagents in an unhealthy state.

Score range

Health status

10 - 8

Good

7 - 4Fair
3 - 1Poor
Note
  • For Armor Complete, only virtual machines that are in a Powered On state are included. 
  • For Armor Anywhere, only virtual machines that have communicated (heartbeated) with Armor in the last 4 hours are included. 
Info

Scores in the security dashboards are calculated and updated every night at 2:00 AM UTC.

Assets ProtectedThis widget displays the number of virtual machines that contain the Armor agent.
Healthy ServicesThis widget displays the percentage of agents and subagents that are working properly.
Protection Score TrendThis graph displays the history of your protection scores.  

Understand Service Health 

...

The Service Health section displays the virtual machines that contain the installed Armor agent. 
To view this section, you must have the Read Virtual Machines(s)permission assigned to your account.

Column

Description

Asset Name

This column displays the name of the virtual machine.

You can click the name of the virtual machine to access the Virtual Machine details screen.

Status

This column displays the security status of the virtual machine.

  • Unprotected indicates the agent is not installed in the instance.
    • Instances without an agent will be labeled as Unprotected. All instances from the public cloud account will be displayed.
  • Needs Attention indicates that the agent is installed, but has not properly communicated (heartbeated) with Armor.
  • OK indicates that the agent is installed and has communicated (hearbeated) with Armor.
Location

For Armor Complete, this column will display name of the Armor virtual site.

For Armor Anywhere, this column will display the name of the public cloud provider.

Ticket

This column displays the support ticket that troubleshoots the Protection issue.
A Protection issue will automatically generate a support ticket.

Improve your Protection Score 

...

You can use the information below to troubleshoot the issues displayed in the Protection screen. 

Armor recommends that you troubleshoot these issues to:

  • Improve your Protection scores
  • Improve your overall health scores
  • Increase the overall security of your environment

Review each step to troubleshoot your problem. If the first step does not resolve the issue, then continue to the second step until the issue has been resolved. As always, you can send a support ticket. 

Note

To learn how to send a support ticket, see Support Tickets.

Excerpt Include
ESLP:Troubleshoot logging score (snippet)
ESLP:Troubleshoot logging score (snippet)
nopaneltrue

Excerpt Include
ESLP:Troubleshoot Malware Protection scores (snippet)
ESLP:Troubleshoot Malware Protection scores (snippet)
nopaneltrue

Excerpt Include
ESLP:Troubleshoot FIM score (snippet)
ESLP:Troubleshoot FIM score (snippet)
nopaneltrue

Intrusion Detection System (IDS)

...

Issue: IDS has not provided a heartbeat in the past 4 hours

Expand
titleStep 1: Verify the status of the agent

DescriptionCommand
WindowsVerify that the service is running
gsv -displayname *trend*
LinuxVerify that the service is running
ps_axu | grep ds_agent
Expand
titleStep 2: Check the connectivity of the agent

DescriptionCommand
WindowsVerify the URL endpoint epsec.armor.com
& "C:\Program Files\Trend Micro\Deep Security Agent\dsa_query.cmd" -c GetAgentStatus | sls -pattern url

Confirm connection to the URL
new-object System.Net.Sockets.TcpClient('146.88.106.210', 443)



LinuxVerify the URL endpoint epsec.armor.com
/opt/ds_agent/dsa_query -c GetAgentStatus | grep AgentStatus.dsmUrl

Confirm connection to the URLtelnet 146.88.106.210 443
Expand
titleStep 3: Manually heartbeat the agent

DescriptionCommand
WindowsVerify a 200 response
Code Block
PS C:\Users\Administrator> & "C:\Program Files\Trend Micro\Deep Security Agent\dsa_control.cmd" -m
HTTP Status: 200 - OK
Response:
Manager contact has been scheduled to occur in the next few seconds.
LinuxVerify a 200 response
Code Block
/opt/ds_agent/dsa_control -m


Issue: IDS is installed but has not been configured

Expand
titleStep 1: Verify the status of the agent

DescriptionCommand
WindowsVerify that the service is running
gsv -displayname *trend*
LinuxVerify that the service is running
ps_axu | grep ds_agent
Expand
titleStep 2: Check the connectivity of the agent

DescriptionCommand
WindowsVerify the URL endpoint epsec.armor.com
& "C:\Program Files\Trend Micro\Deep Security Agent\dsa_query.cmd" -c GetAgentStatus | sls -pattern url

Confirm connection to the URL
new-object System.Net.Sockets.TcpClient('146.88.106.210', 443)



LinuxVerify the URL endpoint epsec.armor.com
/opt/ds_agent/dsa_query -c GetAgentStatus | grep AgentStatus.dsmUrl

Confirm connection to the URLtelnet 146.88.106.210 443
Expand
titleStep 3: Manually heartbeat the agent

DescriptionCommand
WindowsVerify a 200 response
Code Block
PS C:\Users\Administrator> & "C:\Program Files\Trend Micro\Deep Security Agent\dsa_control.cmd" -m
HTTP Status: 200 - OK
Response:
Manager contact has been scheduled to occur in the next few seconds.
LinuxVerify a 200 response
Code Block
/opt/ds_agent/dsa_control -m


Issue: IDS is not installed or enabled

Expand
titleStep 1: Verify the status of the agent

DescriptionCommand
WindowsVerify that the service is running
gsv -displayname *trend*
LinuxVerify that the service is running
ps_axu | grep ds_agent
Expand
titleStep 2: Check the connectivity of the agent

DescriptionCommand
WindowsVerify the URL endpoint epsec.armor.com
& "C:\Program Files\Trend Micro\Deep Security Agent\dsa_query.cmd" -c GetAgentStatus | sls -pattern url

Confirm connection to the URL
new-object System.Net.Sockets.TcpClient('146.88.106.210', 443)



LinuxVerify the URL endpoint epsec.armor.com
/opt/ds_agent/dsa_query -c GetAgentStatus | grep AgentStatus.dsmUrl

Confirm connection to the URLtelnet 146.88.106.210 443
Expand
titleStep 3: Manually heartbeat the agent
Windows
Code Block
PS C:\Users\Administrator> & "C:\Program Files\Trend Micro\Deep Security Agent\dsa_control.cmd" -m
HTTP Status: 200 - OK
Response:
Manager contact has been scheduled to occur in the next few seconds.
Linux
Code Block
/opt/ds_agent/dsa_control -m

Vulnerability Scanning

...

Issue: If IR Agent is not installed

Expand
titleStep 1: Verify the status of the agent
Windows
  • IR Agent files are located within C:\Program Files\Rapid7
  • The IR Agent service name is "Rapid7 Insight Agent"
Linux
  • IR Agent files are located within /opt/rapid7/ir_agent
  • IR Agent logs are located within /opt/rapid7/ir_agent/agent.log*
  • Upgrade logs are one level above, within /opt/rapid7/upgrade*
Expand
titleStep 2: Check connectivity of the agent
PortDestination
443/tcp (IR Agent)
  • endpoint.ingress.rapid7.com *
    • (United States)

  • eu.endpoint.ingress.rapid7.com *
    • (Europe, Middle East, Africa)
Note

* The agent will perform a lookup to the applicable DNS entry, which may resolve to one of multiple Amazon Web Services based subnets. As a result, if your firewall does not support outbound filtering by domain name, then you may need to open all outbound traffic to 443/tcp to accommodate this service.

Issue: The Vulnerability Scanning agent did not run during the most recent scan

Expand
titleStep 1: Verify the status of the agent
Windows
  • IR Agent files are located within C:\Program Files\Rapid7
  • The IR Agent service name is "Rapid7 Insight Agent"
Linux
  • IR Agent files are located within /opt/rapid7/ir_agent
  • IR Agent logs are located within /opt/rapid7/ir_agent/agent.log*
  • Upgrade logs are one level above, within /opt/rapid7/upgrade*
Expand
titleStep 2: Check connectivity of the agent
PortDestination
443/tcp (IR Agent)
Note

* The agent will perform a lookup to the applicable DNS entry, which may resolve to one of multiple Amazon Web Services based subnets. As a result, if your firewall does not support outbound filtering by domain name, then you may need to open all outbound traffic to 443/tcp to accommodate this service.

Issue: The Vulnerability Scanning agent is not installed

Expand
titleStep 1: Verify the status of the agent
Windows
  • IR Agent files are located within C:\Program Files\Rapid7
  • The IR Agent service name is "Rapid7 Insight Agent"
Linux
  • IR Agent files are located within /opt/rapid7/ir_agent
  • IR Agent logs are located within /opt/rapid7/ir_agent/agent.log*
  • Upgrade logs are one level above, within /opt/rapid7/upgrade*
Expand
titleStep 2: Check connectivity of the agent
PortDestination
443/tcp (IR Agent)
Note

* The agent will perform a lookup to the applicable DNS entry, which may resolve to one of multiple Amazon Web Services based subnets. As a result, if your firewall does not support outbound filtering by domain name, then you may need to open all outbound traffic to 443/tcp to accommodate this service.

Step 3: Re-install the Armor agent.

Issue: The Vulnerability Scanning agent did not successfully sync

Expand
titleStep 1: Verify the status of the agent
Windows
  • IR Agent files are located within C:\Program Files\Rapid7
  • The IR Agent service name is "Rapid7 Insight Agent"
Linux
  • IR Agent files are located within /opt/rapid7/ir_agent
  • IR Agent logs are located within /opt/rapid7/ir_agent/agent.log*
  • Upgrade logs are one level above, within /opt/rapid7/upgrade*
Expand
titleStep 2: Check connectivity of the agent
PortDestination
443/tcp (IR Agent)
Note

* The agent will perform a lookup to the applicable DNS entry, which may resolve to one of multiple Amazon Web Services based subnets. As a result, if your firewall does not support outbound filtering by domain name, then you may need to open all outbound traffic to 443/tcp to accommodate this service.

Step 3: Re-install the Armor agent.


Anchor
Export Protection screen data
Export Protection screen data
Export Protection Screen Data

...

  1. In the Armor Management Portal (AMP), in the left-side navigation, click Security

  2. Click Protection.

  3. (Optional) Use the search bar to customize the data displayed. 

  4. Below the table, click CSV. You have the option to export all the data (All) or only the data that appears on the current screen (Current Set). 

    Column

    Description

    Asset NameThis column display the name of the virtual machine (or instance).
    LocationThis column displays the data center location for for the virtual machine (or instance).
    Service

    For Armor Complete, the Protection scores focuses on the following services:  

    • Malware Protection
    • FIM
    • Filebeat (for Linux)
    • Winlogbeat (for Windows)

    For Armor Anywhere, the Protection scores focuses on the following services:  

    • Malware Protection
    • FIM
    • IDS
    • Filebeat (for Linux)
    • Winlogbeat (for Windows)
    • Vulnerability Scanning
    StatusThis column displays the security status of the virtual machine (or instance), which can be:
    • Warning
    • Needs Attention
    • OK
    MessageThis column displays a brief message to explain the reason for the Warning or Needs Attention status.