Control Manager Installation Guide - Trend Micro? Online Help

Control Manager 6.0 Installation Guide
1-8
• Normal security: Control Manager uses HTTP for communication
• Medium security: Control Manager uses HTTPS for communication if HTTPS is
supported and HTTP if HTTPS is not supported
• High security: Control Manager uses HTTPS for communication
One-Way Communication
NAT traversal has become an increasingly more significant issue in the current, realworld
network environment. In order to address this issue, MCP uses one-way
communication. One-way communication has the MCP client initiating the connection
to and polling of commands from the server. Each request is a CGI-like command
query or log transmission. In order to reduce the network impact, the connection is kept
alive and open as much as possible. A subsequent request uses an existing open
connection. Even if the connection is dropped, all connections involving SSL to the
same host benefit from session ID cache that drastically reduces reconnection time.
Two-Way Communication
Two-way communication is an alternative to one-way communication. It is still based on
one-way communication, but has an extra channel to receive server notifications. This
extra channel is also based on HTTP protocol. Two-way communication can improve
real-time dispatching and processing of commands from the server by the MCP agent.
The MCP agent side needs a web server or CGI compatible program that can process
CGI-like requests to receive notifications from the Control Manager server.
Single Sign-on (SSO) Support
Through MCP, Control Manager supports single sign-on (SSO) functionality for Trend
Micro products. This feature allows users to sign in to Control Manager and access the
resources of other Trend Micro products without having to sign in to those products as
well.