![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Job Management Partner 1/Client Security Control Description, User's Guide and Operator's Guide
When installing a client security control system, it is important to consider the functionality to be used. The functionality for a client security control system includes core functionality, and functionality that can be selected depending on management requirements.
- Organization of this subsection
- (1) Core functionality
- (2) Optional functionality
(1) Core functionality
The core functionality of a client security control system consists of that to manage inventory information, and that to manage client security. The following table lists the products required to implement this functionality, and their respective installation destinations.
Table 4-1 Core functionality and product installation destinations
Core functionality Required product Installation destination Management of inventory information and management of client security JP1/CSC - Manager Management server Asset Information Manager or Asset Information Manager Subset Component of JP1/Software Distribution Manager JP1/Software Distribution Manager JP1/Software Distribution Client Client
(2) Optional functionality
A client security control system also provides optional functionality, which an administrator can choose based on the management requirements. The following table lists the optional functionality of a client security control system, and the installation destination of each product.
Table 4-2 Optional functionality and product installation destinations
No. Optional functionality Required product Installation destination 1 Managing information about Windows security updates not yet applied on clients MBSA or WUA Client#1 2 Managing the status of anti-virus product settings (such as whether or not pattern files are up to date) Anti-virus product supported by JP1/Software Distribution#2 Client 3 Controlling client network connections from a remote system. JP1/CSC - Manager Remote Option Remote management server 4 Automatically updating judgment policies for anti-virus products (including virus definition file version and engine version) (by linkage with a client). Anti-virus product compatible with automatic judgment policy updating#3 Client 5 Automatically updating judgment policies for anti-virus products (including virus definition file version, engine version, etc.) (by linkage with JP1/CSC - Manager Remote Option). JP1/CSC - Manager Remote Option Remote management server Anti-virus product compatible with automatic judgment policy updating #3 6 Using a quarantine system to control network connections for clients with high security risk levels and to implement security measures. See Part 5. Quarantine Systems See Part 5. Quarantine Systems
- #1
- To use MBSA, the MBSA command line interface and the MBSA database file must be set up.
- To use WUA, WUA 2.0 and Windows Installer 3.0 must be installed and the WUA 2.0 database file must be set up.
- For details about MBSA and WUA, see 7.4 Detecting security updates not applied to a client.
- #2
- For details about anti-virus products supported by JP1/Software Distribution, see the manual Job Management Partner 1/Software Distribution Description and Planning Guide.
- #3
- For details about the anti-virus products compatible with automatic judgment policy updating, see 4.6 Installing anti-virus products that link with automatic judgment policy updating.
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