|C H A P T E R 2|
This chapter provides important security guidelines. The practice of configuring a system to limit unauthorized access is called hardening. This chapter contains the following information:
The SC runs independently of the host domain. The SC does not share any compute resources, such as RAM memory or persistent storage, with the host domain. The SC communicates to the host domain through dedicated hardware. The SC will never log in to the host domain. However, the SC does provide access to the host serial console port for user login, and it does log all console traffic.
The following are security practices to consider:
The following are configuration steps that contribute to hardening your system:
For information about using the Solaris Security Toolkit to create secure configurations for systems running the Solaris Operating System, refer to the following web site:
The platform security configuration checklist in TABLE 2-1 identifies the setsc and setupsc command parameters and other tasks for securing the SC and host. For detailed information on the setsc and setupsc command parameters involving system controller security, see the command descriptions insetsc and setupsc.
See the password restrictions in password.
Ensure that SC user account permissions are aligned with the role of the user. A user account can be granted 4 permission levels. See permission levels in userperm.
Set a time-out for an interaction session established over a serial connection or network connection (Telnet or SSH). See sc_clitimeout.
The SC defaults to DHCP enabled with the SSH protocol for remote connections. To establish an SSH session requires the admin password or a default, system-specific password based on chassis serial number. See Default DHCP Connection. You can define the session idle time-out period that applies to all network connections to the SC. The default is no session idle time-out period.
If the SC is on a general-purpose network, you can ensure secure remote access to the SC by using Secure Shell rather than Telnet. SSH encrypts data flowing between host and client. SSH provides authentication mechanisms that identify both hosts and users, enabling secure connections between known systems. Telnet is fundamentally insecure, because the Telnet protocol transmits information, including passwords, unencrypted.
|Note - SSH does not help with FTP or Telnet protocols. FTP is used to download new ALOM CMT images. These protocols are insecure and should be used cautiously on general-purpose networks.|
The SC provides limited SSH functionality, supporting only SSH version 2 (SSHv2) client requests. TABLE 2-2 identifies the various SSH server attributes and describes how the attributes are handled in this subset. These attribute settings are not configurable.
If you use SSH as your remote access type, you can make as many as eight simultaneous SSH connections to the SC.
See To Configure the Network Interface Variables.
The SSH server on ALOM CMT does not support the following features:
If you try to use any of the above features, an error message is generated. For example, running the command:
generates the following messages:
It is good security practice for well-managed machines to get new host keys periodically. If you suspect that the host key might be compromised, you can use the ssh-keygen command to regenerate system host keys.
Host keys, once generated, can only be replaced and not deleted without resorting to the setdefaults command. For newly generated host keys to be activated, the SSH server must be restarted either by running the restartssh command or through a reboot. For further information on the ssh-keygen and restartssh commands (with examples), see ssh-keygen and restartssh.
|Note - You can also use the ssh-keygen command to display the host key fingerprint on the SC.|
For information on securing the Solaris Operating System, refer to the following books and articles: