4 Cluster Database Policies

This chapter provides the following information for each of the Cluster Database policies:

Brief description of the policy
Summary of the policy's main properties
Default values for the policy: parameters with their default values and objects excluded by default
Impact of the policy violation
Action to perform when the violation occurs

The Cluster Database policies are categorized as follows

Section 4.1, "Configuration Policies"
Section 4.2, "Security Policies - UNIX"
Section 4.3, "Security Policies - Windows"
Section 4.4, "Storage Policies"

4.1 Configuration Policies

The configuration policies for the Cluster Database target are:

4.1.1 Force Logging Disabled

When Data Guard Broker is being used, this policy checks the primary database for disabled force logging.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Configuration	Database Instance; Cluster Database	Oracle Server 9i Release 2 or later	The underlying metrics have a collection frequency of once every 24 hours.	Yes	The primary database is not in force logging mode. As a result, unlogged direct writes in the primary database cannot be propagated to the standby database.

^Footnote 1The policy rule is evaluated each time its underlying db_init_params and ha_info metrics are collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The primary database is not in force logging mode. As a result, unlogged direct writes in the primary database cannot be propagated to the standby database.

Action

The primary database should be put in force logging mode using the ALTER DATABASE FORCE LOGGING parameter.

4.1.2 Installation of JAccelerator (NCOMP)

This policy checks for installation of JAccelerator (NCOMP) that improves Java Virtual Machine performance by running natively compiled (NCOMP) classes.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Configuration	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	JAccelerator (NCOMP) is not installed. Without JAccelerator Java VM performance will be sub-optimal.

^Footnote 1The policy rule is evaluated each time its underlying metric is collected.

Defaults

Parameters and Their Default Values

Parameter default values are dependent on the version of the Oracle Database target. Refer to the Oracle Database documentation for that version of the database target to learn about the parameters and their default values.

Objects Excluded by Default

Not Applicable

Impact of Violation

Java VM performance will be sub-optimal.

Action

For improved Java Virtual Machine performance, install JAccelerator (NCOMP) which typically contains Natively compiled (NCOMP) classes.

4.1.3 Insufficient Number of Control Files

This policy checks for use of a single control file.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Configuration	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	Your database has insufficient control files. If you lose the only copy of the control file due to a media error, there will be unnecessary down time and other risks.

^Footnote 1The policy rule is evaluated each time its underlying db_controlfiles metric are collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Not Applicable

Impact of Violation

The control file is one of the most important files in an Oracle database. It maintains many physical characteristics and important recovery information about the database. If you lose the only copy of the control file due to a media error, there will be unnecessary down time and other risks.

Action

Use at least two control files that are multiplexed on different disks.

4.1.4 Insufficient Number of Redo Logs

This policy checks for use of less than three redo logs.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Configuration	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	Your database has insufficient number of redo log files. When the size and number of online redo logs are inadequate, LGWR will wait for ARCH to complete its writing to the archived log destination, before it overwrites that log. This can cause severe performance slowdowns during peak activity periods.

^Footnote 1The policy rule is evaluated each time its underlying db_redoLogs metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Not Applicable

Impact of Violation

The online redo log files are used to record changes in the database for the purposes of recoverability. When archiving is enabled, these online redo logs need to be archived before they can be reused. Every database requires at least two online redo log groups to be up and running. When the size and number of online redo logs are inadequate, LGWR will wait for ARCH to complete its writing to the archived log destination, before it overwrites that log. This can cause severe performance slowdowns during peak activity periods.

Action

Oracle recommends having at least three online redo log groups with at least two members in each group. For obvious reasons, members of the same group must be on different disk drives.

4.1.5 Recovery Area Location Not Set

This policy checks if the DB_RECOVERY_FILE_DEST initialization parameter is set.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Configuration	Database Instance; Cluster Database	Oracle Server 10g Release1 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	The recovery area location is not set. Setting the recovery area location provides a unified storage location for all recovery components.

^Footnote 1The policy rule is evaluated each time its underlying db_init_params metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Not setting the recovery area location results in a divided storage location for all recovery components.

Action

Set the recovery area location to provide a unified storage location for all recovery components.

4.2 Security Policies - UNIX

The security policies for the Cluster Database target for UNIX are:

4.2.1 Access to ALL_SOURCE View

This policy ensures restricted access to ALL_SOURCE view.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege to the ALL_SOURCE view.

^Footnote 1The policy rule is evaluated each time its underlying allSourceRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

ALL_SOURCE view contains the source of all the stored packages in the database.

Action

Revoke access to the ALL_SOURCE view from the non-SYS database users.

4.2.2 Access to DBA Role Privileges View

This policy ensures restricted access to DBA_ROLE_PRIVS view.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the DBA_ROLE_PRIVS view.

^Footnote 1The policy rule is evaluated each time its underlying dbaRolePrivsRec metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The DBA_ROLE_PRIVS view lists the roles granted to users and other roles. Knowledge of the structure of roles in the database can be exploited by a malicious user.

Action

Restrict access to DBA_ROLE_PRIVS view.

4.2.3 Access to DBA Roles View

This policy ensures restricted access to DBA_ROLES view.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the DBA_ROLES view.

^Footnote 1The policy rule is evaluated each time its underlying dbaRoleRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

DBA_ROLES view contains details of all roles in the database. Knowledge of the structure of roles in the database can be exploited by a malicious user. For example, a public select privilege might increase the likelihood of Denial of Service attacks.

Action

Restrict access to DBA_ROLES view.

4.2.4 Access to DBA_SYS_PRIVS View

This policy ensures restricted access to DBA_SYS_PRIVS view.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the DBA_SYS_PRIVS view.

^Footnote 1The policy rule is evaluated each time its underlying dbaSysPrivsRec metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

DBA_SYS_PRIVS view can be queried to find system privileges granted to roles and users. Knowledge of the structure of roles in the database can be exploited by a malicious user.

Action

Restrict access to DBA_SYS_PRIVS view.

4.2.5 Access to DBA_TAB_PRIVS View

This policy ensures restricted access to DBA_TAB_PRIVS view.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database may be insecure as user %grantee% has %privilege% privilege to the DBA_TAB_PRIVS view.

^Footnote 1The policy rule is evaluated each time its underlying dbaTabPrivsRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Lists privileges granted to users or roles on objects in the database. Knowledge of the structure of roles in the database can be exploited by a malicious user.

Action

Restrict access to DBA_TAB_PRIVS view.

4.2.6 Access to DBA_USERS View

This policy ensures restricted access to DBA_USERS view.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the DBA_USERS view.

^Footnote 1The policy rule is evaluated each time its underlying dbaUsersRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Contains user name and password hashes and other account information. Access to this information can be used to mount brute-force attacks against the database.

Action

Restrict access to DBA_USERS view.

4.2.7 Access to ROLE_ROLE_PRIVS View

This policy ensures restricted access to ROLE_ROLE_PRIVS view.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the ROLE_ROLE_PRIVS view.

^Footnote 1The policy rule is evaluated each time its underlying rolerolePrivsRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Lists roles granted to other roles. Knowledge of the structure of roles in the database can be exploited by a malicious user.

Action

Restrict access to ROLE_ROLE_PRIVS view.

4.2.8 Access to STATS$SQL Summary Table

This policy ensures restricted access to the STATS$SQL_SUMMARY table.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure. User %grantee% has %privilege% privilege on the STATS$SQL_SUMMARY table.

^Footnote 1The policy rule is evaluated each time its underlying sqlSummaryRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Contains first few lines of SQL text of the most resource intensive commands given to the server. SQL statements executed without bind variables can appear and expose privileged information.

Action

Restrict access to the STATS$SQL_SUMMARY table.

4.2.9 Access to STATS$SQL Text Table

This policy ensures restricted access to the STATS$SQLTEXT table.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on STATS$SQLTEXT table.

^Footnote 1The policy rule is evaluated each time its underlying sqlTextRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The STATS$SQLTEXT table provides the full text of the recently-executed SQL statements. The SQL statements can reveal sensitive information.

Action

Restrict access to the STATS$SQLTEXT table.

4.2.10 Access to SYS.AUDIT$ Table

This policy ensures restricted access to the SYS.AUD$ table.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the SYS.AUD$ table.

^Footnote 1The policy rule is evaluated each time its underlying audTabRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The SYS.AUD$ table is the system audit table. If you set the parameter AUDIT_TRAIL to DB, all audited activity will be written to the SYS.AUD$ table. Thus a malicious user can gain access to the sensitive audit information.

Action

Revoke access to the SYS.AUD$ table from the non-DBA/SYS database users.

4.2.11 Access to SYS.LINK$ Table

This policy ensures restricted access to the SYS.LINK$ table.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the USER$ table.

^Footnote 1The policy rule is evaluated each time its underlying linkTabRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

A malicious user can gain access to user names and passwords from the SYS.LINK$ table.

Action

Revoke access to SYS.LINK$ table.

4.2.12 Access to SYS.SOURCE$ Table

This policy ensures restricted access to the SYS.SOURCE$ table.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the SOURCE$ table.

^Footnote 1The policy rule is evaluated each time its underlying sourceTabRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

A malicious user can gain access to the source of all stored packages in the database.

Action

Revoke access to the SYS.SOURCE$ table from the non-SYS/DBA database users.

4.2.13 Access to SYS.USER$ Table

This policy ensures restricted access to the SYS.USER$ table.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the USER$ table.

^Footnote 1The policy rule is evaluated each time its underlying userTabRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

User name and password hash may be read from the SYS.USER$ table, enabling a malicious user to launch a brute-force attack against the database.

Action

Restrict access to SYS.USER$ table.

4.2.14 Access to SYS.USER_HISTORY$ Table

This policy ensures restricted access to the SYS.USER_HISTORY$ table.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the SYS.USER_HISTORY$ table.

^Footnote 1The policy rule is evaluated each time its underlying userHistRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

User name and password hash may be read from the SYS.USER_HISTORY$ table, enabling a malicious user to launch a brute-force attack.

Action

Revoke access to SYS.USER_HISTORY$ table from the non-DBA/SYS database users.

4.2.15 Access to USER_ROLE_PRIVS View

This policy ensures restricted to the USER_ROLE_PRIVS view.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the USER_ROLE_PRIVS view.

^Footnote 1The policy rule is evaluated each time its underlying userRolePrivsRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Lists the roles granted to the current user. Knowledge of the structure of roles in the database can be exploited by a malicious user.

Action

Restrict access to the USER_ROLE_PRIVS view.

4.2.16 Access to USER_TAB_PRIVS View

This policy ensures restricted access to the USER_TAB_PRIVS table.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. User %grantee% has %privilege% privilege on the USER_TAB_PRIVS view.

^Footnote 1The policy rule is evaluated each time its underlying userTabPrivsRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Lists the grants on objects for which the user is the owner, grantor, or grantee. Knowledge of the grants in the database can be exploited by a malicious user.

Action

Restrict access to the USER_TAB_PRIVS view.

4.2.17 Control File Permission

This policy ensures that access to the control files directory is restricted to the owner of the Oracle software set and the DBA group.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. The control file (%file_name%) permission is %permission%.

^Footnote 1The policy rule is evaluated each time its underlying dbControlFilesPermRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Control files are binary configuration files that control access to data files. Control files are stored in the directory specified by the CONTROL_FILES initialization parameter. A public write privilege on this directory could pose a serious security risk.

Action

Restrict permission to the control files to:

Owner of the Oracle software installation
DBA group

Do not give read and write permissions to public

4.2.18 Default Passwords

This policy ensures there are no default passwords for known accounts.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. Default password for the account %dbaccount% has not been changed.

^Footnote 1The policy rule is evaluated each time its underlying defaultAccountPasswordsRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

A malicious user can gain access to the database using default passwords.

Action

Change all default passwords.

4.2.19 Excessive Allowed Failed Login Attempts

This policy ensures that the number of allowed failed login attempts is no more than 10.

The FAILED_LOGIN_ATTEMPTS parameter defines the number of successive failed login attempts that can be performed before an account's status is changed to locked. This protects against malicious users attempting to guess a password for an account.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. FAILED_LOGIN_ATTEMPTS is set to %limit% for the profile %profile%.

^Footnote 1The policy rule is evaluated each time its underlying loginserver_failed_logins metric is collected.

Defaults

Parameters and Their Default Values

Maximum FAILED_LOGIN_ATTEMPTS: 10 failed attempts

Objects Excluded by Default

None

Impact of Violation

Permits manual and automated password guessing by a malicious user.

By setting the parameter to UNLIMITED, a malicious user can attempt an unlimited amount of guesses of the password for all accounts granted the specified profile. However, setting the value too low may result in valid users locking their accounts when mistyping a password.

Action

In user profiles, set the value for the FAILED_LOGIN_ATTEMPTS setting to no more than 10.

4.2.20 Excessive PUBLIC EXECUTE Privileges

Checks for PUBLIC having execute privileges on powerful packages (UTL_HTTP, UTL_TCP and UTL_SMTP).

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in insecure state. EXECUTE privilege on the package %package% is granted to the PUBLIC role.

^Footnote 1The policy rule is evaluated each time its underlying executePrivilegesRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Privileges granted to the PUBLIC role automatically apply to all users. A malicious user can gain access to e-mail, network, and http modules using the EXECUTE privilege.

Action

Revoke EXECUTE privileges on powerful packages.

4.2.21 Execute UTL_FILE Privileges to PUBLIC

This policy ensures the PUBLIC role does not have EXECUTE privilege on the UTL_FILE package.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. EXECUTE privilege on UTL_FILE package is granted to PUBLIC.

^Footnote 1The policy rule is evaluated each time its underlying pubexecutePrivilegesRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Privileges granted to the PUBLIC role automatically apply to all users. A malicious user can read and write arbitrary files in the system when granted the UTL_FILE privilege.

Action

Revoke EXECUTE privileges granted to UTL_FILE package from PUBLIC.

4.2.22 Oracle Home Datafile Permission

This policy ensures that access to the datafiles is restricted to the owner of the Oracle software set and the DBA group.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. The datafile (%file_name%) permission is %permission%.

^Footnote 1The policy rule is evaluated each time its underlying dbDataFilesPermRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The datafiles contain all the database data. If datafiles are made readable to public, they can be read by a user who has no database privileges on the data.

Action

Restrict permissions to the datafiles to:

Owner of the Oracle software set
DBA group

Do not give read and write permissions to public.

4.2.23 Password Grace Time

This policy ensures that all profiles have PASSWORD_GRACE_TIME set to a reasonable number of days.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. PASSWORD_GRACE_TIME is set to %limit% days for the profile %profile%.

^Footnote 1The policy rule is evaluated each time its underlying pwdGraceRep metric is collected.

Defaults

Parameters and Their Default Values

MAX_PASSWORD_GRACE_TIME = 3

Objects Excluded by Default

Not Applicable

Impact of Violation

A high value for the PASSWORD_GRACE_TIME parameter may cause serious database security issues by allowing the user to keep the same password for a long time.

Action

Set the PASSWORD_GRACE_TIME parameter to no more than 3 days for all profiles.

4.2.24 Password Life Time

This policy ensures that all profiles have PASSWORD_LIFE_TIME set to a reasonable number of days.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. PASSWORD_LIFE_TIME is set to %limit% days for the profile %profile%.

^Footnote 1The policy rule is evaluated each time its underlying pwdLifeRep metric is collected.

Defaults

Parameters and Their Default Values

MAX_PASSWORD_LIFE_TIME = 90

Objects Excluded by Default

Not Applicable

Impact of Violation

A long password life time gives malicious users a long time to decipher the password. May cause serious database security issues.

Action

Set the PASSWORD_LIFE_TIME parameter to no more than 90 days for all profiles.

4.2.25 Password Locking Time

This policy ensures that PASSWORD_LOCK_TIME is set to a reasonable number of days for all profiles.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. PASSWORD_LOCK_TIME is set to %limit% days for the profile %profile%.

^Footnote 1The policy rule is evaluated each time its underlying pwdLockRep metric is collected.

Defaults

Parameters and Their Default Values

MIN_PASSWORD_LOCK_TIME = 1

Objects Excluded by Default

Not Applicable

Impact of Violation

The PASSWORD_LOCK_TIME resource relates to the number of days an account is locked after a user tries unsuccessfully to login for more than FAILED_LOGIN_ATTEMPTS (another related resource) times. Having a low value for this resource increases the likelihood of Denial of Service attacks.

Action

Set the PASSWORD_LOCK_TIME parameter to no less than 1 for all the profiles.

4.2.26 Password Reuse Maximum

This policy ensures that all profiles have PASSWORD_REUSE_MAX set to a reasonable number of times.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. PASSWORD_REUSE_MAX is set to %limit% times for the profile %profile%.

^Footnote 1The policy rule is evaluated each time its underlying reuseMaxRep metric is collected.

Defaults

Parameters and Their Default Values

MAX_PASSWORD_REUSE_MAX = 20

Objects Excluded by Default

Not Applicable

Impact of Violation

The PASSWORD_REUSE_MAX parameter specifies the number of password changes required before the current password can be reused. Old passwords are usually the best guesses for the current password. A low value for the PASSWORD_REUSE_MAX parameter may cause serious database security issues by allowing users to reuse their old passwords more often. Ensuring a reasonable value for this resource will discourage users from reusing their passwords resulting in more secure password usage.

Action

Set the PASSWORD_REUSE_MAX parameter to no less than 20 times for all profiles.

4.2.27 Password Reuse Time

This policy ensures that all profiles have PASSWORD_REUSE_TIME set to a reasonable number of days.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. PASSWORD_REUSE_TIME is set to %limit% for the profile %profile%.

^Footnote 1The policy rule is evaluated each time its underlying passwdReuseTimeRep metric is collected.

Defaults

Parameters and Their Default Values

MAX_PASSWORD_REUSE_TIME = 2147483647

Objects Excluded by Default

Not Applicable

Impact of Violation

The PASSWORD_REUSE_TIME parameter defines the number of days before a password can be reused. A low value for the password reuse time can increase the danger of an already leaked password to cause serious database security issues.

Ensuring a reasonable value for this resource will discourage users from reusing their passwords resulting in more secure password usage.

Action

Set the PASSWORD_REUSE_TIME parameter to UNLIMITED for all profiles.

4.2.28 Profiles with Excessive Allowed Failed Login Attempts

This policy ensures that the number of allowed failed login attempts is no more than 10.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. FAILED_LOGIN_ATTEMPTS is set to %limit% for the profile %profile%.

^Footnote 1The policy rule is evaluated each time its underlying loginserver_failed_logins metric is collected.

Defaults

Parameters and Their Default Values

Maximum FAILED_LOGIN_ATTEMPTS: 10 failed attempts

Objects Excluded by Default

Not Applicable

Impact of Violation

Permits manual and automated password guessing by a malicious user.

Action

In user profiles, set the value for the FAILED_LOGIN_ATTEMPTS setting to no more than 10.

4.2.29 PUBLIC EXECUTE Privileges to DBMS Job

This policy ensures PUBLIC is not granted EXECUTE privileges on DBMS_JOB package.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. DBMS_JOB package has PUBLIC EXECUTE privileges.

^Footnote 1The policy rule is evaluated each time its underlying dbmsJobPrivsRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Granting EXECUTE privilege to PUBLIC on DBMS_JOB package allows all users to schedule jobs on the database.

Action

PUBLIC must not be granted EXECUTE privileges on DBMS_JOB package.

4.2.30 PUBLIC EXECUTE Privileges to DBMS LOB

This policy ensures PUBLIC group is not granted EXECUTE privileges to the DBMS_LOB package.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. DBMS_LOB package has PUBLIC EXECUTE privileges.

^Footnote 1The policy rule is evaluated each time its underlying dbmsLobRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The DBMS_LOB package can be used to access any file on the system as the owner of the Oracle software installation.

Action

Revoke the EXECUTE privileges on DBMS_LOB package from the PUBLIC group.

4.2.31 PUBLIC EXECUTE Privileges to DBMS SYS SQL

This policy ensures PUBLIC is not granted EXECUTE privileges on DBMS_SYS_SQL package.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. DBMS_SYS_SQL package has PUBLIC EXECUTE privileges.

^Footnote 1The policy rule is evaluated each time its underlying dbmsSysSqlRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The DBMS_SYS_SQL package can be used to run PL/SQL and SQL as the owner of the procedure rather than the caller.

Action

Revoke the EXECUTE privileges on DBMS_SYS_SQL package from the PUBLIC group.

4.2.32 System Privileges to Public

This policy ensures system privileges are not granted to PUBLIC.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. System privilege %privilege% is assigned to the PUBLIC role.

^Footnote 1The policy rule is evaluated each time its underlying systemPrivilegesRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Privileges granted to the PUBLIC role automatically apply to all users. There are security risks when granting SYSTEM privileges to all users.

Action

Revoke SYSTEM privileges from the PUBLIC role.

4.2.33 Unlimited Tablespace Quota

This policy ensures that database users are allocated a limited tablespace quota.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. User %dbuser% has an unlimited tablespace quota.

^Footnote 1The policy rule is evaluated each time its underlying tableSpaceQuotaRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Granting unlimited tablespace quotas can cause the filling up of the allocated disk space. This can lead to an unresponsive database.

Action

For users with an unlimited tablespace quota, reallocate their tablespace quotas to a specific limit.

4.2.34 Use of Database Links with Cleartext Password

Ensures database links with clear text passwords are not used, that is, the password is hashed or encrypted.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Security	Database Instance; Cluster Database	Oracle Server 9i and pre-9i	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. Database link %link% has clear text password.

^Footnote 1The policy rule is evaluated each time its underlying dbLinkPwdRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The table SYS.LINK$ contains the clear text password used by the database link. A malicious user can read clear text password from SYS.LINK$ table that can lead to undesirable consequences.

Action

Avoid creating fixed user database links.

4.2.35 Well Known Accounts

This policy ensures well-known accounts are expired and locked.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. Account %dbaccount% is not locked and terminated.

^Footnote 1The policy rule is evaluated each time its underlying installAndDemoAcccountsRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

A malicious user can gain access to the database using a well-known account.

Action

Expire and lock well-known accounts.

4.2.36 Well Known Accounts (Status)

This policy ensures well-known accounts are expired and locked.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. Account %dbaccount% is not locked and terminated.

^Footnote 1The policy rule is evaluated each time its underlying installAndDemoAccountsRepmetric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

A malicious user can gain access to the database using a well-known account.

Action

Expire and lock well-known accounts.

4.3 Security Policies - Windows

The security policies for the Cluster Database target for Windows are:

4.3.1 Control File Permission (Windows)

This policy ensures that access to the control files directory is restricted to the owner of the Oracle software set and the DBA group. The following permissions on Windows NT based platforms are considered critical: DELETE, WRITE_DAC, WRITE_OWNER, CHANGE, ADD, and FULL. The policy gives the number of users or user groups which have been granted such permissions, and lists the users and user groups in parentheses.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8	The underlying metric has a collection frequency of once every 24 hours.	No	Database is in an insecure state. The users %users% have critical permissions on the control file (%file_name%).

^Footnote 1The policy rule is evaluated each time its underlying dbControlFilesPermNTRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

Action

Restrict permission to the control files to:

Owner of the Oracle software installation
DBA group

Do not give read and write permissions to public.

4.3.2 Oracle Home Datafile Permission (Windows)

This policy ensures that access to the datafiles is restricted to the owner of the Oracle software set and the DBA group. The following permissions on Windows NT based platforms are considered critical: DELETE, WRITE_DAC, WRITE_OWNER, CHANGE, ADD, and FULL. The policy gives the number of users or user groups which have been granted such permissions, and lists the users and user groups in parentheses.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Security	Database Instance; Cluster Database	Oracle Server 8 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Database is in an insecure state. The users %users% have critical permissions on the datafile (%file_name%).

^Footnote 1The policy rule is evaluated each time its underlying dbDataFilesPermNTRep metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

The datafiles contain all the database data. If datafiles are made readable to public, they can be read by a user who has no database privileges on the data.

Action

Restrict permissions to the datafiles to:

Owner of the Oracle software set
DBA group

Do not give read and write permissions to public.

4.4 Storage Policies

The storage policies for the Cluster Database target are:

4.4.1 Default Permanent Tablespace Set to a System Tablespace

This policy verifies that the DEFAULT_PERMANENT_TABLESPACE database property is set to a non-system tablespace. The default permanent tablespace for the database is used as the default permanent tablespace for any users who are not explicitly assigned a permanent tablespace. The default permanent tablespace is defaulted to the SYSTEM tablespace until it is changed by a DBA.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Storage	Database Instance; Cluster Database	Oracle Server 10g Release 1 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	The default permanent tablespace is not set explicitly and defaults to SYSTEM tablespace.

^Footnote 1The policy rule is evaluated each time its underlying db_recTablespaceSettings metric is collected.

Defaults

Parameters and Their Default Values

SYSTEM

Objects Excluded by Default

Not Applicable

Impact of Violation

If not specified explicitly, the DEFAULT_PERMANENT_TABLESPACE is defaulted to the SYSTEM tablespace. This is not the recommended setting. The default permanent tablespace for the database is used as the permanent tablespace for any non-SYSTEM users who are not explicitly assigned a permanent tablespace. If the database default permanent tablespace is set to a system tablespace, then any user who is not explicitly assigned a tablespace uses the system tablespace. Non-SYSTEM users should not be using a system tablespaces to store data. Doing so may result in performance degradation for the database.

Action

Set the DEFAULT_PERMANENT_TABLESPACE to a non-system tablespace. Create or edit a tablespace and set it to be the default permanent tablespace.

Clicking the DEFAULT_PERMANENT_TABLESPACE link will bring up the Tablespace Search page. From this page you can create or edit a tablespace and set it to be the default permanent tablespace.

On the Administration property page for the database instance, click Tablespaces under the Storage options. After providing your credentials, create or edit a permanent tablespace and set it to be the default permanent tablespace.

4.4.2 Default Temporary Tablespace Set to a System Tablespace

This policy verifies that the DEFAULT_TEMP_TABLESPACE database property is set to a non-system tablespace. The default temporary tablespace for the database is used as the temporary tablespace for any users that are not explicitly assigned a temporary tablespace. The temporary tablespace is defaulted to the SYSTEM tablespace until it is changed by a DBA.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Warning	Storage	Database Instance; Cluster Database	Oracle Server 9i or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	The default temporary tablespace is not set explicitly and defaults to SYSTEM tablespace.

^Footnote 1The policy rule is evaluated each time its underlying db_recTablespaceSettings metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Not Applicable

Impact of Violation

If not specified explicitly, the DEFAULT_TEMP_TABLESPACE defaults to the SYSTEM tablespace. This is not the recommended setting. The default temporary tablespace is used as the temporary tablespace for any users who are not explicitly assigned a temporary tablespace. If the database default temporary tablespace is set to a system tablespace, then any user who is not explicitly assigned a temporary tablespace uses the system tablespace as their temporary tablespace. System tablespaces should not be used to store temporary data. Doing so can result in performance degradation for the database.

Action

Set the DEFAULT_TEMP_TABLESPACE to a non-system temporary tablespace. In Oracle Database 10g Release 1 or later, you can also set the DEFAULT_TEMP_TABLESPACE to a temporary tablespace group. Create or edit a temporary tablespace, or temporary tablespace group, and set it to be the default temporary tablespace.

Clicking the DEFAULT_TEMP_TABLESPACE link will bring up the Tablespace Search page. From this page the user can create or edit a temporary tablespace and set it to be the default temporary tablespace.

On the Administration property page for the database instance, click Tablespaces under the Storage options. After providing your credentials, create or edit a temporary tablespace and set it to be the default temporary tablespace.

4.4.3 Dictionary Managed Tablespaces

This policy determines whether dictionary managed tablespaces are being used. Use locally managed tablespaces.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	Tablespace %TABLESPACE_NAME% is dictionary managed. Oracle recommends using locally managed tablespaces, with AUTO segment-space management, to enhance performance and ease of space management.

^Footnote 1The policy rule is evaluated each time its underlying db_recTablespaceSettings metric is collected.

Defaults

Parameters and Their Default Values

Not Applicable

Objects Excluded by Default

Not Applicable

Impact of Violation

These tablespaces are dictionary managed. Oracle recommends using locally managed tablespaces, with AUTO segment-space management, to enhance performance and ease of space management.

Action

Redefine these tablespaces to be locally managed.

4.4.4 Insufficient Redo Log Size

This policy, using the SMALL_REDO_LOGS parameter, checks for redo log files that are less than 1 MB.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Critical	Storage	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	Your database has redo log that has insufficient size.

^Footnote 1The policy rule is evaluated each time its underlying db_redo_logs metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Not Applicable

Impact of Violation

Small redo logs cause system checkpoints to continuously put a high load on the buffer cache and I/O system.

Action

Increase size of the redo logs to at least 1 MB.

4.4.5 Non-System Data Segments in a System Tablespace

Redefine the tablespaces containing the segments to be locally managed; or, reorganize these segments, specifying a Next Extent value that is a multiple of Initial Extent, and a Percent Increase value of 0.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	Segment %OBJECT% belonging to non-system users are stored in system tablespace %TABLESPACE_NAME%. This makes it more difficult to manage these data segments and may result in performance degradation in the system tablespace.

^Footnote 1The policy rule is evaluated each time its underlying db_recSegmentSettings metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Cluster object types because the Reorganize Objects wizard does not support them.

All user accounts that are, by default, part of the Oracle Database or Enterprise Manager. For example: SYS, SYSTEM, SYSMAN, CTXSYS, SCOTT, ADAMS, and so on.

Impact of Violation

These segments belonging to non-system users are stored in system tablespaces SYSTEM or SYSAUX. This violation makes it more difficult to manage these data segments and may result in performance degradation in the system tablespace. System users include users that are part of the DBMS such as SYS and SYSTEM, or that are part of facilities supplied by Oracle: for example, CTXSYS, SYSMAN, and OLAPSYS.

Action

Relocate the non-system segments to a non-system tablespace.

4.4.6 Non-Uniform Default Extent Size for Dictionary Managed Tablespaces

This policy checks for tablespaces with non-uniform default extent size.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	Tablespace %TABLESPACE_NAME% uses non-uniform extents. Using uniform extents ensures that any free extent in the tablespace can always be used for any segment in the tablespace.

^Footnote 1The policy rule is evaluated each time its underlying db_tablespaces metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

SYSTEM tablespace. This policy is only applicable to PERMANENT DICTIONARY tablespaces.

Impact of Violation

Tablespaces using a non-uniform default extent size exist. Extents in a tablespace should be the same size. This ensures that any free extent in the tablespace can always be used for any segment in the tablespace.

Action

To ensure uniform extent sizes, set each tablespace's default storage clause so that the NEXT value should be equal to or a multiple of the INITIAL value, and the PCTINCREASE value is set to zero. Then never explicitly specify a storage clause at the segment level. Instead, let the storage values for the segments be inherited from the default storage clause of the tablespace.

4.4.7 Rollback in SYSTEM Tablespace

Rollback in SYSTEM Tablespace.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	All	See following table	Yes	Your SYSTEM tablespace contains rollback segment %RBS_NAME%. The SYSTEM tablespace should be reserved only for the Oracle data dictionary and its associated objects.

^Footnote 1The policy rule is evaluated each time its underlying metric is collected.

The following table lists the policy's underlying metrics.

Underlying Metric	Collection Frequency
db_init_params	Every 24 hours
db_rollback_segs	Every 24 hours

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Not Applicable

Impact of Violation

The SYSTEM tablespace should be reserved only for the Oracle data dictionary and its associated objects. It should NOT be used to store any other types of objects such as user tables, user indexes, user views, rollback segments, undo segments, or temporary segments.

Action

Use a tablespace dedicated to undo instead of the SYSTEM tablespace.

4.4.8 Segment in Dictionary Tablespace with Extent Growth Policy Violation

This policy, using the SEG_EXT_GROWTH_VIO parameter, checks for segments in dictionary managed tablespaces having irregular extent sizes and/or non-zero Percent Increase settings.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	Segment %OBJECT% in dictionary managed tablespace %TABLESPACE_NAME% has irregular extent sizes and/or non-zero Percent Increase settings. This can result in inefficient reuse of space and fragmentation problems.

^Footnote 1The policy rule is evaluated each time its underlying db_recSegmentSettings metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Not Applicable

Impact of Violation

These segments have extents with sizes that are not multiples of the initial extent, and/or a non-zero Percent Increase setting. This can result in inefficient reuse of space and fragmentation problems.

Action

4.4.9 Tablespace Not Using Automatic Segment-Space Management

This policy checks for locally managed tablespaces that are using MANUAL segment space management.

There are two segment-space management settings: MANUAL and AUTO.

MANUAL segment-space management uses free lists to manage free space within segments. Free lists are lists of data blocks that have space available for inserting rows. With this form of segment-space management, you must specify and tune the PCTUSED, FREELISTS and FREELIST GROUPS storage parameters for schema objects created in the tablespace.
AUTO segment-space management uses bitmaps to manage the free space in segments. The bitmap describes the status of each data block within a segment with respect to the amount of space in the block available for inserting rows. These bitmaps allow the database to manage free space automatically.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	Oracle Server 9.2 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	Tablespace %TABLESPACE_NAME% is not using automatic segment-space management.

^Footnote 1The policy rule is evaluated each time its underlying db_recTablespaceSettings metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Not Applicable

Impact of Violation

Automatic segment-space management is a simpler and more efficient way of managing space within a segment. It completely eliminates any need to specify and tune the PCTUSED, FREELISTS and FREELIST GROUPS storage parameters for schema objects created in the tablespace.

In a RAC environment, there is the additional benefit of avoiding the hard partitioning of space inherent with using free list groups.

Action

Change the segment-space management of all permanent locally managed tablespaces to AUTO.

Clicking the name of each tablespace listed will bring up the Reorganize Objects wizard with the tablespace automatically selected. This wizard allows you to change the segment-space management of the tablespace from MANUAL to AUTO.

4.4.10 Tablespaces Containing Rollback and Data Segments

This policy, using the TBSP_MIXED_SEGS parameter, checks for tablespaces containing both rollback and data segments.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	Tablespace %TABLESPACE_NAME% contains both rollback and data segments. Mixing segment types in this way makes it more difficult to manage space and may degrade performance in the tablespace.

^Footnote 1The policy rule is evaluated each time its underlying db_recTablespaceSettings metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

SYSTEM tablespace

Impact of Violation

These tablespaces contain both rollback and data segments. Mixing segment types in this way makes it more difficult to manage space and may degrade performance in the tablespace. Use of a dedicated tablespace for rollback segments enhances availability and performance.

Action

Use Automatic Undo Management (in Oracle Server Release 9.0.1 or later) and perform one of the following:

Drop the rollback segments from this tablespace
Create one or more tablespaces dedicated to rollback segments and drop the rollback segments from this tablespace
Dedicate this tablespace to rollback segments and move the data segments to another tablespace

4.4.11 Users with a System Tablespace as Default Tablespace

This policy, using the SYSTEM_AS_DEFAULT_TBSP parameter, checks for any user having a System tablespace listed as their default tablespace.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	All	The underlying metric has a collection frequency of once every 24 hours.	Yes	User %USER_NAME% uses SYSTEM tablespace as the default tablespace. This will result in non-system data segments being added to the SYSTEM tablespace and possible performance degradation in the SYSTEM tablespace.

^Footnote 1The policy rule is evaluated each time its underlying db_recUserSettings metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Cluster object types because the Reorganize Objects wizard does not support them.

All user accounts that are, by default, part of the Oracle Database or Enterprise Manager, for example: SYS, SYSTEM, SYSMAN, CTXSYS, SCOTT, ADAMS, and so on.

Impact of Violation

These users use a system tablespace as the default tablespace. This violation will result in non-system data segments being added to the system tablespace, making it more difficult to manage these data segments and possibly resulting in performance degradation in the system tablespace.

Action

Change the default tablespace for these users to specify a non-system tablespace.

4.4.12 Users with Permanent Tablespace as Temporary Tablespace

This policy checks the PERM_AS_TEMP_TBSP parameter to detect whether a permanent tablespace is being used as a temporary tablespace.

Policy Summary

The following table lists the policy's main properties.

Severity	Category	Target Type	Versions Affected	Policy Rule Evaluation^Foot 1	Automatically Enabled?	Alert Message
Informational	Storage	Database Instance; Cluster Database	Oracle Server 9.2 or later	The underlying metric has a collection frequency of once every 24 hours.	Yes	User %USER_NAME% uses permanent tablespace %TABLESPACE_NAME% as the temporary tablespace. Using a permanent tablespace as the temporary tablespace may result in performance degradation, especially for Real Application Clusters.

^Footnote 1The policy rule is evaluated each time its underlying Db_recUserSettings metric is collected.

Defaults

Parameters and Their Default Values

Objects Excluded by Default

Not Applicable

Impact of Violation

These users use a permanent tablespace as the temporary tablespace. Using temporary tablespaces allows space management for sort operations to be more efficient. Using a permanent tablespace for these operations may result in performance degradation, especially for Real Application Clusters.

Action

Change the temporary tablespace for these users to specify a tablespace of type TEMPORARY.