This chapter outlines the planning process for a secure installation and describes several recommended deployment topologies for the systems.
To better understand security needs, the following questions must be asked:
You can protect many of the resources in the production environment. Consider the type of resources that you want to protect when determining the level of security to provide.
When using DIVA Enterprise Connect, protect the following resources:
DIVA Enterprise Connect is installed on a server attached to one or more disks; either a local, or remote, disk directly connected to the DIVA Enterprise Connect system. Independent access to these disks presents a security risk. This type of external access might be from a rogue system that reads or writes to these disks, or from an internal system that accidentally provides access to these disk devices.
You must protect DIVA Enterprise Connect system configuration settings from operating system level non-administrator users. In general, these settings are protected automatically by operating system level administrative users. Making the configuration files writable to non-administrative operating system users presents a security risk.
In general, the resources described in the previous section must be protected from all non-administrator access on a configured system, or from rogue external systems that can access these resources through the WAN or FC fabric.
Protection failures against strategic resources can range from inappropriate access (that is, access to data outside of normal DIVArchive operations) to data corruption (erroneously deleting assets, or writing to disk or tape outside of normal permissions).
This section describes how to install and configure an infrastructure component securely.For information about installing DIVA Enterprise Connect, see the Oracle DIVA Enterprise Connect Installation, Configuration, and Operations Guide in the Oracle DIVA Enterprise Connect 1.0 documentation library.
Consider the following points when installing and configuring DIVArchive:
You must install DIVA Enterprise connect as a Linux user with admin privileges, but not as root. You must always run WebLogic as this user, and insure that the user is not used for other applications or services (for example, DIVArchive). The default DIVA Enterprise Connect installation directory permissions, and owners, should not be changed after installation without considering the security implications of the changes.
DIVA Enterprise Connect allows connections to DIVArchive using legacy DIVA tcp sockets, HTTP, or HTTPS. If you connect to a remote DIVArchive instance over a WAN, ensure that you connect over a trusted network. HTTP/HTTPS connections require that the Oracle DIVAnet ManagerAdapter component be installed and configured on the DIVArchive platform. If you use HTTP/HTTPS, Oracle recommends installing the ManagerAdapter component on the DIVArchive Manager system for increased system security.
DIVA Enterprise Connect employs Oracle WebLogic in its implementation. Oracle WebLogic has a browser based admin console utility. If external access to the WebLogic Admin Console port is not needed, Oracle recommends blocking the port using firewall software. Often, it will not be necessary to allow both the HTTP and HTTPS admin console ports to both be active; you can block one or both using firewall software.
By default, DIVA Enterprise Connect provides both an HTTP web services port, and an HTTPS web services port. If external access to either the HTTP or HTTPS ports are not needed, Oracle recommends blocking the port using firewall software. Often, it will not be necessary to allow both the HTTP and HTTPS web services ports to both be active; you can block one or both using firewall software.
After installing any portion of DIVA Enterprise Connect, go through the security checklist in Appendix A.