IBM System i Manual page 23

on a network encrypts and changes the password during each successful connection. You must
use the default password to initially set up your system if you use a local console on a network
(LAN).
Important: The device authentication requires a unique service tools device ID for each PC that is
configured with a local console on a network (LAN) connection.
When using an Operations Console local console on a network, the configuration wizard adds the
necessary information to the PC. The configuration wizard asks for the service tools device ID
and an access password. The access password protects the service tools device ID password on
the PC.
When establishing a network connection, the Operations Console configuration wizard prompts
you for the access password to access the encrypted service tools device ID and password. The
user will also be prompted for a valid service tools user ID and password.
Note: When you use the graphical control panel on systems with a keystick on a logical partition,
setting the mode to Secure might require you to use the LPAR menu on the primary
partition to select another mode.
User authentication
This security provides assurance as to who is using the service device. All problems related to
user authentication are the same regardless of console type. For more information, see the Service
tools topic.
Data privacy
This security provides confidence that the console data can only be read by the intended
recipient. Operations Console local console directly attached to the server uses a physical
connection similar to a twinaxial console or secure network connection for LAN connectivity to
protect console data. Operations Console using a direct connection has the same data privacy of a
twinaxial connection. If the physical connection is secure as discussed under service device
authentication, the console data remains protected. To protect the data, ensure only authorized
people enter the computer room.
Operations Console local console on a network uses a secure network connection if the
appropriate cryptographic products are installed. The console session uses the strongest
encryption possible, depending on the cryptographic products installed on the system and the PC
running Operations Console. If no cryptographic products are installed, there can be no data
encryption.
Data integrity
This security provides confidence that the console data has not changed en route to the recipient.
An Operations Console local console directly attached to the system has the same data integrity
as a twinaxial connection. If the physical connection is secure, the console data remains protected.
An Operations Console local console on a network uses a secure network connection if the
appropriate cryptographic products are installed. The console session uses the strongest
encryption possible, depending on the cryptographic products installed on the system and the PC
running Operations Console. If no cryptographic products are installed, there can be no data
encryption.
Data encryption
Enhanced authentication and data encryption provide network security for console procedures.
Operations Console local console on a network uses a version of SSL which supports device and
user authentication but without using certificates.
Administration
Operations Console administration allows system administrators to control access to console functions,
including the remote control panel and virtual control panel. When using Operations Console local
15
Operations Console