Database Administration with Style! |
Database Diva Presents: Security Tutorials for Overworked Oracle™ Database Administrators |
|
|
Building an Oracle™ DatabaseIn addition to worrying about the risks associated with the software installed on the database server, you also need to worry about the risks associated with the features built into your database. For example, you aren't vulnerable to weaknesses in the http server if the http server isn't running.Instead of using the Oracle™ installer or the Database Creation Assistant (dbca) to create your database, use a script that installs the minimum functionality required, and then add the features required by your application. In Oracle™ 10g, you may specify the initial password for SYS and SYSTEM in the CREATE DATABASE statement using the following syntax: USER SYS IDENTIFIED BY password
If you do not specify passwords for SYS and SYSTEM, the default passwords CHANGE_ON_INSTALL and MANAGER will be used. If you use this feature, be sure to set the file permissisons to prohibit access by anyone who is not a member of the DBA group. Oracle™ provides a pair of sample parameter files in the dbs directory of the ORACLE_HOME, init.ora and initdw.ora. The initdw.ora file contains suggested parameters for a warehouse. Recommended Initalization Parameter Settings
Restrict access to all directories associated with the database and the Oracle binaries. Also restrict access to directories where log files, trace files, core files and archived log files may be written, as these files often contain sensitive information. After building the database, lock the SYS user, and change the passwords for for any users that were created with a default value. |
Last update 05/14/2008
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates.