Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

"Log Inspection Rules Require Log Files" appears after adding Log Inspection rules in Deep Security

    • Updated:
    • 13 Sep 2015
    • Product/Version:
    • Deep Security 8.0
    • Deep Security 9.0
    • Deep Security 9.5
    • Deep Security 9.6
    • Platform:
    • HPUX 11.x
    • IBM AIX
    • Linux - Red Hat RHEL 4 32-bit
    • Linux - Red Hat RHEL 4 64-bit
    • Linux - Red Hat RHEL 5 32-bit
    • Linux - Red Hat RHEL 5 64-bit
    • Linux - Red Hat RHEL 6 32-bit
    • Linux - Red Hat RHEL 6 64-bit
    • Linux - SuSE 10
    • Linux - SuSE 11
    • Unix - Solaris (Sun) version 10 (SunOS 5.10)
    • Unix - Solaris (Sun) version 9 (SunOS 5.9)
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary
After you enable the Log Inspection module and add Log Inspection rules, the following error appears:
Log Inspection Rules Require Log Files
Log Inspection Rules Require Log Files
Click image to enlarge.
Details
Public
A Log Inspection rule contains the file to monitor and the conditions to trigger the rule. The files to monitor should exist on the protected machine for the rule to work.
The error appears when you add an unnecessary rule and the files do not exist on your machine.
To verify the files controlled by the rule:
  1. On the Deep Security console, go to Policies > Log Inspection Rules.
  2. Double-click the rule. A new window will appear.
  3. Click Configuration tab.
Log files to monitor in a Log Inspection Rule
Click image to enlarge.
To resolve the issue, remove the unnecessary rules on the protected machine or on the profile being used.
To prevent this issue, run a Recommendation Scan for suggested rules:
  1. On the Deep Security Manager, go to Computers.
  2. Right-click the computer to scan and click Actions > Scan for Recommendations.
  3. View the results on the General tab of the protection module in the Computer/Policy Editor.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1098889
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.