- Created by George Alpizar, last modified on Feb 08, 2018
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 7 Next »
Error rendering macro 'excerpt-include'
No link could be created for 'Protection dashboard (snippet)'.
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.
Logging
Armor Service | Issue | Remediation | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Logging | The filebeat logging agent is not installed. | Step 1: Verify the status of filebeat
Step 2: Send a support ticket Error rendering macro 'excerpt-include' No link could be created for 'Create a support ticket (snippet)'. | ||||||||||||||||||||||||||||||||||||||||||||||||
Logging | The winlogbeat logging agent is not installed. This section only applies to Windows users. | Step 1: Verify the status of winlogbeat
Step 2: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new | ||||||||||||||||||||||||||||||||||||||||||||||||
Logging | Armor has not received a log in the past 4 hours. | Step 1: Check logging services
Step 2: Check connectivity
|
Malware Protection
Armor Service | Issue | Remediation | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Malware Protection | Malware Protection has not provided a heartbeat in the past 4 hours. | Step 1: Verify the status of the agent
Step 2: Check the connectivity of the agent
Step 3: Manually heartbeat the agent
Step 4: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new | ||||||||||||||||||||||||||||||||||||||||
Malware Protection | Malware Protection is not installed or configured. | Step 1: Verify the status of the agent
Step 2: Check the connectivity of the agent
Step 3: Manually heartbeat the agent
Step 4: Check the components for the agent
Component.AM.mode describes if the Malware Protection module is installed. Component.AM.rules is the number of rules derived from the Armor Deep Security Manager. Step 5: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new | ||||||||||||||||||||||||||||||||||||||||
Malware Protection | Reboot is required for Malware Protection. | Step 1: Reboot your server Step 1: Reboot your server Step 2: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new |
File Integrity Monitoring (FIM)
Armor Service | Issue | Remediation | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
File Integirty Monitoring (FIM) | FIM has not provided a heartbeat in the past 4 hours. | Step 1: Verify the status of the agent
Step 2: Check the connectivity of the agent
Step 3: Manually heartbeat the agent
Step 4: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new | ||||||||||||||||||||||||||||||||||||||||
File Integirty Monitoring (FIM) | FIM is installed but has not been configured. | Step 1: Verify the status of the agent
Step 2: Check the connectivity of the agent
Step 3: Manually heartbeat the agent
Step 4: Check the components for the agent
Component.IM.mode describes if the FIM module is installed. Component.IM.rules is the number of rules derived from the Armor Deep Security Manager. Step 5: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new | ||||||||||||||||||||||||||||||||||||||||
File Integirty Monitoring (FIM) | FIM is not installed. | Step 1: Verify the status of the agent
Step 2: Check the connectivity of the agent
Step 3: Manually heartbeat the agent
Step 4: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new |
Intrusion Detection System (IDS)
Armor Service | Issue | Remediation | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IDS | IDS has not provided a heartbeat in the past 4 hours. | Step 1: Verify the status of the agent
Step 2: Check the connectivity of the agent
Step 3: Manually heartbeat the agent
Step 4: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new | ||||||||||||||||||||||||||||||||||||
IDS | IDS is installed but has not been configured. | Step 1: Verify the status of the agent
Step 2: Check the connectivity of the agent
Step 3: Manually heartbeat the agent
Step 4: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new | ||||||||||||||||||||||||||||||||||||
IDS | IDS is not installed or enabled. | Step 1: Verify the status of the agent
Step 2: Check the connectivity of the agent
Step 3: Manually heartbeat the agent
Step 4: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new |
Vulnerability Scanning
Armor Service | Issue | Remediation | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Vulnerability Scanning | If IR Agent is not installed | Step 1: Verify the status of the agent
Step 2: Check connectivity of the agent
* 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: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new | ||||||||
Vulnerability Scanning | The Vulnerability Scanning agent did not run during the most recent scan. | Step 1: Verify the status of the agent
Step 2: Check connectivity of the agent
* 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: Send a support ticket Click the following link to open a support ticket in AMP: https://amp.armor.com/support/tickets/new |