Security Compliance determines component version inconsistencies between the OfficeScan server and OfficeScan agents. Inconsistencies typically occur when agents cannot connect to the server to update components. If the agent obtains updates from another source (such as the Trend Micro ActiveUpdate server), it is possible for a agent’s component version to be newer than the version on the server.

Security Compliance checks the following components:

  • Smart Scan Agent Pattern

  • Virus Pattern

  • IntelliTrap Pattern

  • IntelliTrap Exception Pattern

  • Virus Scan Engine

  • Spyware Pattern

  • Spyware Active-monitoring Pattern

  • Spyware Scan Engine

  • Virus Cleanup Template

  • Virus Cleanup Engine

  • Common Firewall Pattern

  • Common Firewall Driver

  • Behavior Monitoring Driver

  • Behavior Monitoring Core Service

  • Behavior Monitoring Configuration Pattern

  • Digital Signature Pattern

  • Policy Enforcement Pattern

  • Behavior Monitoring Detection Pattern

  • Global C&C IP List

  • Relevance Rule Pattern

  • Early Boot Cleanup Driver

  • Memory Scan Trigger Pattern

  • Memory Inspection Pattern

  • Browser Exploit Prevention Pattern

  • Script analyzer Pattern

  • Program Version

A non-compliant agent is counted at least twice in the Compliance Report.

  • In the Endpoints with Inconsistent Component Versions category

  • In the category for which the agent is non-compliant. For example, if the agent’s Smart Scan Agent Pattern version is not consistent with the version on the server, the agent is counted in the Smart Scan Agent Pattern category. If more than one component version is inconsistent, the agent is counted in each category for which it is non-compliant.

To resolve component version inconsistencies, update outdated components on the agents or server.