Job Management Partner 1/Client Security Control Description, User's Guide and Operator's Guide

[Contents][Glossary][Index][Back][Next]


1.3.8 Gauge trends in security countermeasure statuses

n Overview

The example below shows how statistics are output. The administrator can use the statistics to judge whether a problem with security measures is a short-term or long-term problem.

Figure 1-18 Outputting statistics

[Figure]

n Work flow

  1. Security policy setup
    Based on the corporate security policy, the administrator sets the judgment policy (judgment items) and the action policy (actions triggered according to the judgment result).
  2. Collection of IT asset information
    The IT asset information for a client is collected and centrally managed in the asset management database.
  3. Security level judgment
    The IT asset information collected in step 2 is checked against the judgment policy set in step 1 to determine the client security level. The security levels of clients are judged one group at a time for the groups defined by the administrator.
    A security level judgment can be triggered in any of three ways: Automatic judgment when inventory information is updated, periodic judgment via Scheduled Tasks in Windows, or judgment by an administrator.
  4. Execution of statistics storage command
    When the command is executed, information about the status of security countermeasures is stored in the asset management database as statistics.
  5. Output of statistics
    Search for the statistics that you want to check. You can then check the countermeasure status by displaying the data as a graph or outputting it as a CSV file.

[Contents][Back][Next]


[Trademarks]

All Rights Reserved. Copyright (C) 2009, 2011, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated