- Sun Cluster 3.0 12/01 Security with the Apache and iPlanet Web and Messaging Agents
- Assumptions and Limitations
- Solaris OE Service Restriction
- Sun Cluster 3.0 Daemons
- Terminal Server Usage
- Node Authentication
- Securing Sun Cluster 3.0 12/01 Software
- Verifying Node Hardening
- Maintaining a Secure System
- Solaris Security Toolkit Software Backout Capabilities
The secured Sun Cluster 3.0 12/01 software configuration implemented by the Solaris Security Toolkit suncluster30u2-secure.driver is a Sun Microsystems-supported configuration for agents described in this document. Only Sun Cluster 3.0 12/01 implementations using the three agents explicitly described in this article and referenced in the Sun Cluster 3.0 12/01 Release Notes are supported in hardened configurations.
Hardening Sun Cluster 2.x, 3.0, and 3.0 update 1 software is not supported. Only agents described in this article and listed in the Sun Cluster 3.0 12/01 Release Notes are supported in hardened configurations.
While it is not required that you use the Solaris Security Toolkit software (toolkit) to harden the cluster, it is strongly recommended. Using the toolkit, you can easily create an error free, documented, and standardized hardened configuration. In addition, the toolkit provides a mechanism for undoing hardening changes should it become necessary.
Sun Microsystems supports a hardened Sun Cluster 3.0 12/01 cluster, using the agents specified in this document, whether security modifications are performed manually or through the use of the Solaris Security Toolkit software.
Please note that the toolkit is not a supported Sun product; only the end-configuration created by the toolkit is supported. Toolkit support is available through the Sun™ SupportForum discussion group at http://www.sun.com/security/jass