Securing Groupwise Agents; Setting Up Ssl Connections; Protecting Agent Web Consoles; Protecting Agent Startup And Configuration Files - Novell GROUPWISE 8 - ADMINISTRATION Administration Manual

Securing GroupWise Agents

8 5
Section 85.1, "Setting Up SSL Connections," on page 1207
Section 85.2, "Protecting Agent Web Consoles," on page 1207
Section 85.3, "Protecting Agent Startup and Configuration Files," on page 1207
Section 85.4, "Protecting Agent Log Files," on page 1208
Section 85.5, "Protecting Agent Processes on Linux," on page 1209
Section 85.6, "Protecting Trusted Applications," on page 1209

85.1 Setting Up SSL Connections

®
All of the GroupWise agents should be configured to use SSL connections, as described in:
"Securing the Post Office with SSL Connections to the POA" on page 511
"Securing the Domain with SSL Connections to the MTA" on page 643
"Securing Internet Agent Connections with SSL" on page 788
"Securing WebAccess Agent Connections with SSL" on page 897
"Configuring Authentication and Intruder Lockout for the Monitor Web Console" on
page 1023

85.2 Protecting Agent Web Consoles

If you do not provide passwords on the GroupWise agent Web consoles, unauthorized persons can
access them by simply knowing the IP address or hostname of the machine where the agent runs,
along with the HTTP port the agent is using. Set up GroupWise agent Web consoles with passwords
as described in:
"Using the POA Web Console" on page 544
"Using the MTA Web Console" on page 673
"Using the Internet Agent Web Console" on page 805
"Using the WebAccess Agent Web Console" on page 949
"Configuring Authentication and Intruder Lockout for the Monitor Web Console" on
page 1023
85.3 Protecting Agent Startup and Configuration
Files
The startup and configuration files for all GroupWise agents should be protected from tampering.
Agent startup files are found in the following default locations:
85
Securing GroupWise Agents 1207