How to isolate a suspect component in Host IPS
Technical Articles ID:
KB54960
Last Modified: 11/5/2020
Last Modified: 11/5/2020
Environment
McAfee Host Intrusion Prevention (Host IPS) 8.0
Summary
Host IPS is a collection of several components that protect the local system from vulnerabilities. It is possible that one component can make the whole package appear to be at fault. This article explains how to isolate the component within Host IPS that might be involved.
You mut perform most of the following steps at the local client's Host IPS Configuration user interface. The administrator must unlock the user interface to allow configuration.
NOTE: This process includes troubleshooting steps that might require repeated restarts, logons, or re-creating issues.
You mut perform most of the following steps at the local client's Host IPS Configuration user interface. The administrator must unlock the user interface to allow configuration.
Disable all components and test for failure
-
Verify if IPS is disabled:
- Go to the IPS Policy tab.
- Make sure that Enable Host IPS is deselected.
- Make sure that Enable Network IPS is deselected.
-
Verify if Firewall is disabled:
- Go to the Firewall Policy tab.
- Make sure that Enable Firewall is deselected.
-
Clear the Blocked Hosts list:
- Go to the Blocked Hosts tab.
- Clear the list by selecting each entry and clicking Remove.
-
Enable Activity logging:
- Go to the Activity Log tab.
- Verify that all traffic logging and filter option checkboxes are selected.
-
Test the system
to verify if the problem recurs:- If the problem still occurs, continue to step 6.
- If the problem does not occur, go to step 1 of the "Iterative testing phase of each component" section below.
-
Check the following:
- Stop the McAfee Host IPS service and retest.
If the problem goes away, report the issue as associated directly with the service. - Uninstall the Host IPS agent from the local box and retest.
If the problem goes away, report the issue as associated to installed files and not a specific component.
- Stop the McAfee Host IPS service and retest.
Iterative testing phase of each component
-
Test Host IPS:
- Go to the Activity Log tab and clear the log.
- Go to the IPS Policy tab.
- Click Enable Host IPS.
-
Test the system
to determine if the problem recurs:-
If the problem recurs:
- Deselect Enable Host IPS.
- Retest to verify that the problem goes away.
NOTE: If the problem goes away, Host IPS can potentially be associated with the issue.
- Save a copy of the Activity log and rename it to Host IPS Activity Log wProb.
- Click Enable Host IPS and verify the problem returns.
- If the problem does not recur, go to step 5 to test Network IPS.
-
-
Test all IPS engines:
- Click Help and select Troubleshooting.
- Click Enable IPS Logging.
- Select logging for All Message Types.
- Select Functionality.
- On the HIPS Engines pop-up window, deselect Enable / Disable all engines.
- Click OK to close the HIPS Engines pop-up window.
- Click OK to close the Troubleshooting pop-up window.
-
Test the system to determine if the problem recurs:
-
If the problem recurs, the problem is associated with the IPS component, but not the specific engines.
- Get the IPS Log and report that the IPS component might be the problem.
- If the problem does not recur, the issue might be associated with a specific engine. Continue to step 3 to test each IPS engine.
-
-
Test each IPS engine:
- Click Help and select Troubleshooting.
- Make sure that Enable IPS Logging is still selected.
- Make sure that logging for All Message Types is still selected.
- Click Functionality.
-
Begin at the top, select the first box, and retest to see if the issue recurs:
- Click OK.
- Work down the list with only one engine enabled for each test.
- Note which engines are associated with the issue.
- Get the IPS log for each test and label each log with the name of the engine tested.
- Follow this process for each engine.
- If one or more of the IPS engines are identified, note the IPS engines in the case notes.
- When individual testing of the engines is complete, enable all engines to continue to the next step.
-
Test IPS Adaptive Mode:
- Go to the Activity Log tab and clear the log.
- Click Enable Adaptive Mode.
-
Test the system
to determine if the problem recurs:-
If the problem recurs:
- Deselect Enable Adaptive Mode.
- Retest to verify if the problem goes away.
- If the problem goes away, Host IPS in Adaptive Mode can potentially be associated with the issue.
- Save a copy of the Activity log and rename it Host IPS Adaptive Activity Log wProb.
- If the problem does not recur, deselect Enable Host IPS and continue to the next step.
-
-
Test Network IPS:
- Go to the Activity Log tab and clear the log.
- Go to the IPS Policy tab.
- Select Enable Network IPS.
-
Test the system to determine if the problem recurs:
-
If the problem recurs:
- Deselect Enable Network IPS.
- Retest to verify if the problem goes away.
- If the problem goes away, Network IPS can potentially be associated with the issue.
- Save a copy of the Activity log and rename it Network IPS Activity Log wProb.
- If the problem does not recur, select Enable Network IPS and continue to the next step.
-
-
Test Automatic Blocking of Network IPS:
- Go to the Activity Log tab and clear the log.
- Select Automatically Block Attackers.
-
Test the system to determine if the problem recurs:
-
If the problem recurs:
- Deselect Automatically Block Attackers.
- Retest to verify if the problem goes away.
- If the problem goes away, Network IPS in Block Attackers Mode can potentially be associated with the issue.
- Go to the Blocked Hosts tab and identify any new entries to the list.
- Note the blocked attacker entries and review for false positives.
- Save a copy of the Activity log and rename it Network IPS Adaptive Activity Log wProb.
- If the problem does not recur, deselect Enable Network IPS and continue to the next step.
-
-
Test Firewall Policy:
- Go to the Activity Log tab and clear the log.
- Go to the Firewall Policy tab.
- Click Enable Firewall.
-
Test the system to determine if the problem recurs:
-
If the problem recurs:
- Deselect Enable Firewall.
- Retest to verify if the problem goes away.
- If the problem goes away, Host IPS Firewall can potentially be associated with the issue.
- Save a copy of the Activity log and rename it Firewall Activity Log wProb.
- If the problem does not recur, select the Enable Firewall checkbox and continue to the next step.
-
-
Test Firewall Learn Mode:
- Go to the Activity Log tab and clear the log.
- Go to the Firewall Policy tab.
- Select Learn Mode Incoming Enabled.
- Test the system to determine if the problem recurs. If the problem recurs:
- Save a copy of the Activity log and rename it Firewall Activity Log LearnIN wProb.
- If the problem goes away, Firewall Incoming Learn Mode can potentially be associated with the issue.
- Retest to verify if the problem goes away.
- Deselect Learn Mode Incoming Enable.
- Go to the Activity Log tab and clear the log.
- Go to the Firewall Policy tab.
- Select Learn Mode Outgoing Enabled (both Incoming and Outgoing must be selected).
-
Test the system to determine if the problem recurs. If the problem recurs:
- Select Learn Mode Outgoing Enabled.
- Retest to verify if the problem goes away.
- If the problem goes away, Firewall Learn ModeIncoming can potentially be associated with the issue.
- Save a copy of the Activity log and rename it Firewall Activity Log LearnINOUT wProb.
- Go to the Activity Log tab and clear the log.
- Go to the Firewall Policy tab.
- Select Learn Mode Incoming Enabled (both Incoming and Outgoing must be selected).
- Test the system to determine if the problem recurs. If the problem recurs:
- Deselect Learn Mode Incoming Enabled.
- Retest to verify if the problem goes away.
- If the problem ceases, Firewall Outgoing Learn Mode can potentially be associated with the issue.
- Save a copy of the Activity log and rename it Firewall Activity Log LearnOUT wProb.
- Test with the
Any Any rule.
NOTE: You might need to configure this step from the ePO management console. It is imperative that the first rule configured in the firewall rule list is theAny Any test rule. If other policies have been configured from the console, they take precedence over the locally created rules.
- Create a rule and name it
Any Any . - Set the Action to Permit.
- Set the Protocol to IP TCP.
- Set the Direction to Either and click OK.
- If it is being pushed from the console, move the
Any Any rule to be the first processed rule in the policy list. - If the rule is created locally, make sure that no other rules continue it.
- Test the system
to determine if the problem recurs. If the problem recurs:- Deactivate the
Any Any rule. - Retest to verify if the problem goes away.
- If the problem goes away, there is probably a configuration error with the rules.
- Obtain a screenshot of the Agent Configuration UI on the Firewall Policy tab.
- Export the Host IPS policy settings from ePO.
- Save a copy of the Activity log and rename it to Firewall Activity Log AnyAny Test.
- Deactivate the
- Create a rule and name it
- Go to the Firewall Policy tab.
- Deselect Enable Firewall and continue to the next step.
-
Test Blocked Hosts Policy:
- Go to the Activity Log tab and clear the log.
- Go to the Blocked Hosts tab.
- Remove all blocked hosts from the list.
- Test the system to determine if the problem recurs. If the problem recurs, it is probably not associated with the Blocked Hosts Policy.