CIS Oracle Database Server 11 - 11g R2 Benchmark v1.0.0

CIS Oracle Database Server 11 - 11g R2
v1.0.0
Benchmark
Export Date 12-11-2012

The CIS Security Benchmarks division provides consensus-oriented information security products, services, tools, metrics, suggestions, and
recommendations (the SB Products) as a public service to Internet users worldwide. Downloading or using SB Products in any way signifies
and confirms your acceptance of and your binding agreement to these CIS Security Benchmarks Terms of Use.
CIS SECURITY BENCHMARKS TERMS OF USE

BOTH CIS SECURITY BENCHMARKS DIVISION MEMBERS AND NON-MEMBERS MAY:
Download, install, and use each of the SB Products on a single computer, and/or
Print one or more copies of any SB Product that is in a .txt, .pdf, .doc, .mcw, or .rtf format, but only if each such copy is printed in
its entirety and is kept intact, including without limitation the text of these CIS Security Benchmarks Terms of Use.
UNDER THE FOLLOWING TERMS AND CONDITIONS:

SB Products Provided As Is. CIS is providing the SB Products as is and as available without: (1) any representations,
warranties, or covenants of any kind whatsoever (including the absence of any warranty regarding: (a) the effect or lack of effect
of any SB Product on the operation or the security of any network, system, software, hardware, or any component of any of them,
and (b) the accuracy, utility, reliability, timeliness, or completeness of any SB Product); or (2) the responsibility to make or notify
you of any corrections, updates, upgrades, or fixes.
Intellectual Property and Rights Reserved. You are not acquiring any title or ownership rights in or to any SB Product, and full
title and all ownership rights to the SB Products remain the exclusive property of CIS. All rights to the SB Products not expressly
granted in these Terms of Use are hereby reserved.
Restrictions. You acknowledge and agree that you may not: (1) decompile, dis-assemble, alter, reverse engineer, or otherwise
attempt to derive the source code for any software SB Product that is not already in the form of source code; (2) distribute,
redistribute, sell, rent, lease, sublicense or otherwise transfer or exploit any rights to any SB Product in any way or for any
purpose; (3) post any SB Product on any website, bulletin board, ftp server, newsgroup, or other similar mechanism or device;
(4) remove from or alter these CIS Security Benchmarks Terms of Use on any SB Product; (5) remove or alter any proprietary
notices on any SB Product; (6) use any SB Product or any component of an SB Product with any derivative works based directly
on an SB Product or any component of an SB Product; (7) use any SB Product or any component of an SB Product with other
products or applications that are directly and specifically dependent on such SB Product or any component for any part of their
functionality; (8) represent or claim a particular level of compliance or consistency with any SB Product; or (9) facilitate or
otherwise aid other individuals or entities in violating these CIS Security Benchmarks Terms of Use.
Your Responsibility to Evaluate Risks. You acknowledge and agree that: (1) no network, system, device, hardware, software,
or component can be made fully secure; (2) you have the sole responsibility to evaluate the risks and benefits of the SB Products
to your particular circumstances and requirements; and (3) CIS is not assuming any of the liabilities associated with your use of
any or all of the SB Products.
CIS Liability. You acknowledge and agree that neither CIS nor any of its employees, officers, directors, agents or other service
providers has or will have any liability to you whatsoever (whether based in contract, tort, strict liability or otherwise) for any
direct, indirect, incidental, consequential, or special damages that arise out of or are connected in any way with your use o f any
SB Product.
Indemnification. You agree to indemnify, defend, and hold CIS and all of CIS's employees, officers, directors, agents and other
service providers harmless from and against any liabilities, costs and expenses incurred by any of them in connection with yo ur
violation of these CIS Security Benchmarks Terms of Use.
Jurisdiction. You acknowledge and agree that: (1) these CIS Security Benchmarks Terms of Use will be governed by and
construed in accordance with the laws of the State of Maryland; (2) any action at law or in equity arising out of or relating to
these CIS Security Benchmarks Terms of Use shall be filed only in the courts located in the State of Maryland; and (3) you hereby
consent and submit to the personal jurisdiction of such courts for the purposes of litigating any such action.
U.S. Export Control and Sanctions laws. Regarding your use of the SB Products with any non-U.S. entity or country, you
acknowledge that it is your responsibility to understand and abide by all U.S. sanctions and export control laws as set from time
to time by the U.S. Bureau of Industry and Security (BIS) and the U.S. Office of Foreign Assets Control (OFAC).
SPECIAL RULES FOR CIS MEMBER ORGANIZATIONS: CIS reserves the right to create special rules for: (1) CIS Members; and (2) Non-
Member organizations and individuals with which CIS has a written contractual relationship. CIS hereby grants to each CIS Member
Organization in good standing the right to distribute the SB Products within such Members own organization, whether by manual or
electronic means. Each such Member Organization acknowledges and agrees that the foregoing grants in this paragraph are subject to the
terms of such Members membership arrangement with CIS and may, therefore, be modified or terminated by CIS at any time.
1|Pa ge
Table of Contents
Overview...................................................................................................................................................................................... 8
Recommendations .............................................................................................................................................................. 12
1 Oracle Database Installation and Patching Requirements ............................................................... 12
1.1 Change the Oracle default account passwords .................................................................................... 12
1.1.1 Change the default password for 'APEX_040000' (Scored) ................................................ 12
1.1.2 Change the default password for 'APPQOSSYS' (Scored) ..................................................... 13
1.1.3 Change the default password for 'CTXSYS' (Scored) ............................................................... 14
1.1.4 Change the default password for 'DBSNMP' (Scored) ............................................................ 15
1.1.5 Change the default password for 'DIP' (Scored) ........................................................................ 16
1.1.6 Change the default password for 'EXFSYS' (Scored) ............................................................... 17
1.1.7 Change the default password for 'MDDATA' (Scored) ........................................................... 17
1.1.8 Change the default password for 'MDSYS' (Scored) ................................................................ 18
1.1.9 Change the default password for 'LBACSYS' (Scored)............................................................ 19
1.1.10 Change the default password for 'OLAPSYS' (Scored) ........................................................ 20
1.1.11 Change the default password for 'ORACLE_OCM' (Scored).............................................. 21
1.1.12 Change the default password for 'ORDDATA' (Scored) ...................................................... 21
1.1.13 Change the default password for 'ORDPLUGINS' (Scored)............................................... 22
1.1.14 Change the default password for 'ORDSYS' (Scored) ........................................................... 23
1.1.15 Change the default password for 'OUTLN' (Scored) ............................................................. 24
1.1.16 Change the default password for 'OWBSYS_AUDIT' (Scored) ........................................ 25
1.1.17 Change the default password for 'OWBSYS' (Scored).......................................................... 26
1.1.18 Change the default password for 'SI_INFORMTN_SCHEMA' (Scored) ....................... 26
1.1.19 Change the default password for 'SPATIAL_CSW_ADMIN_USR' (Scored) ............... 27
1.1.20 Change the default password for 'SPATIAL_WFS_ADMIN_USR' (Scored) ............... 28
1.1.21 Change the default password for 'SYS' (Scored) ..................................................................... 29
1.1.22 Change the default password for 'SYSTEM' (Scored)........................................................... 30
1.1.23 Change the default password for 'WK_TEST' (Scored) ....................................................... 31
1.1.24 Change the default password for 'WKPROXY' (Scored) ..................................................... 32
2|Pa ge
1.1.25 Change the default password for 'WKSYS' (Scored) ............................................................. 33
1.1.26 Change the default password for 'WMSYS' (Scored) ............................................................ 33
1.1.27 Change the default password for 'XDB' (Scored).................................................................... 34
1.2 Remove Oracle Sample Users ......................................................................................................................... 35
1.2.1 Remove the sample user 'BI' (Scored) ............................................................................................. 35
1.2.2 Remove the sample user 'HR' (Scored) ........................................................................................... 36
1.2.3 Remove the sample user 'IX' (Scored).............................................................................................. 37
1.2.4 Remove the sample user 'OE' (Scored) ............................................................................................ 37
1.2.5 Remove the sample user 'PM' (Scored) ........................................................................................... 38
1.2.6 Remove the sample user 'SCOTT' (Scored) ................................................................................... 39
1.2.7 Remove the sample user 'SH' (Scored) ............................................................................................ 40
1.3 Ensure the latest version/patches for Oracle software is installed (Not Scored) ..... 40
2 Oracle Parameter Settings .................................................................................................................................... 41
2.1 listener.ora settings .............................................................................................................................................. 42
2.1.1 Setting for 'secure_control_listener_name' parameter (Scored)...................................... 42
2.1.2 extproc configuration in listener.ora (Scored)............................................................................ 42
2.1.3 Setting for the 'admin_restrictions_listener_name' parameter (Scored) .................... 43
2.1.4 Change the default port numbers that connect to Oracle (Scored)................................ 44
2.1.5 Setting for parameter 'secure_register_listener_name' parameter (Scored) ........... 45
2.2 sqlnet.ora settings.................................................................................................................................................. 45
2.3 Setting for the 'audit_sys_operations' parameter (Scored) ..................................................... 45
2.4 Setting for the 'audit_trail' parameter (Scored) ............................................................................. 46
2.5 Setting for the 'global_names' parameter (Scored) ...................................................................... 47
2.6 Setting for the 'local_listener' parameter (Scored)....................................................................... 48
2.7 Setting for the 'o7_dictionary_accessibility' parameter (Scored)........................................ 49
2.8 Setting for the 'os_roles' parameter (Scored) .................................................................................. 49
2.9 Setting for the 'remote_listener' parameter (Scored) ................................................................. 50
2.10 Setting for the 'remote_login_passwordfile' parameter (Scored)..................................... 51
2.11 Setting for the 'remote_os_authent' parameter (Scored)....................................................... 51
2.12 Setting for the 'remote_os_roles' parameter (Scored)............................................................. 52
3|Pa ge
2.13 Setting for the 'utl_file_dir' parameter (Scored).......................................................................... 53
2.14 Setting for the 'sec_case_sensitive_logon' parameter (Scored).......................................... 53
2.15 Setting for the 'sec_max_failed_login_attempts' parameter (Scored)............................. 54
2.16 Setting for the 'sec_protocol_error_further_action' parameter (Scored) ..................... 55
2.17 Setting for the 'sec_protocol_error_trace_action' parameter (Scored).......................... 56
2.18 Setting for the 'sec_return_server_release_banner' parameter (Scored)..................... 56
2.19 Setting for the 'sql92_security' parameter (Scored)................................................................. 57
2.20 Setting for undocumented '_trace_files_public' parameter (Scored).............................. 58
3 Oracle client/user connection and login restrictions .......................................................................... 58
3.1 Restrictions on failed login attempts via the default DB profile (Scored)...................... 59
3.2 Requirements for account locking via on the default DB profile (Scored) .................... 59
3.3 Restrictions on password duration via the default DB profile (Sco red) ......................... 60
3.4 Restrictions on password history via the default DB profile (Scored)............................. 61
3.5 Restrictions on password use (reuse) via a DB profile (Scored) ......................................... 61
3.6 Requirements for account locking (grace time) via a DB profile (Scored) .................... 62
3.7 Requirements for limiting EXTERNAL user login capability (Scored) ............................. 62
3.8 Requirement for setting the password verification function (Not Scored)................... 63
3.9 Requirements for limiting the number of sessions per user (Scored) ............................. 64
4 Oracle user access and authorization restrictions................................................................................. 64
4.1 Default Public Privileges for Packages and Object Types.............................................................. 64
4.1.1 Limit public access to the DBMS_ADVISOR package (Scored)........................................... 65
4.1.2 Limit public access to the DBMS_CRYPTO package (Scored)............................................. 65
4.1.3 Limit public access to the DBMS_JAVA package (Scored) .................................................... 66
4.1.4 Limit public access to the DBMS_JAVA_TEST package (Scored) ...................................... 67
4.1.5 Limit public access to the DBMS_JOB package (Scored) ....................................................... 67
4.1.6 Limit public access to the DBMS_LDAP package (Scored) ................................................... 68
4.1.7 Limit public access to the DBMS_LOB package (Scored) ...................................................... 68
4.1.8 Limit public access to the DBMS_OBFUSCATION_TOOLKIT package (Scored)....... 69
4.1.9 Limit public access to the DBMS_RANDOM package (Scored) .......................................... 70
4.1.10 Limit public access to the DBMS_SCHEDULER package (Scored) ................................ 70
4|Pa ge
4.1.11 Limit public access to the DBMS_SQL package (Scored) .................................................... 71
4.1.12 Limit public access to the DBMS_XMLGEN package (Scored)......................................... 72
4.1.13 Limit public access to the DBMS_XMLQUERY package (Scored) .................................. 72
4.1.14 Limit public access to the UTL_FILE package (Scored)....................................................... 73
4.1.15 Limit public access to the UTL_INADDR package (Scored) .............................................. 74
4.1.16 Limit public access to the UTL_TCP package (Scored) ........................................................ 74
4.1.17 Limit public access to the UTL_MAIL package (Scored) ..................................................... 75
4.1.18 Limit public access to the UTL_SMTP package (Scored) .................................................... 76
4.1.19 Limit public access to the UTL_DBWS package (Scored) ................................................... 76
4.1.20 Limit public access to the UTL_ORAMTS package (Scored) ............................................. 77
4.1.21 Limit public access to the UTL_HTTP package (Scored) .................................................... 78
4.1.22 Limit public access to the HTTPURITYPE object type (Scored) .................................... 78
4.2 Non-Default Public Privileges for Packages and Object Types .................................................. 79
4.2.1 Limiting public user access to the DBMS_SYS_SQL package (Scored) .......................... 79
4.2.2 Limit public access to the DBMS_BACKUP_RESTORE package (Scored) .................... 80
4.2.3 Limiting public user access to the DBMS_AQADM_SYSCALLS package (Scored) .. 80
4.2.4 Limiting public user access to the DBMS_REPACT_SQL_UTL package (Scored) .... 81
4.2.5 Limiting public user access to the INITJVMAUX package (Scored) ................................ 82
4.2.6 Limiting public user access to the DBMS_STREAMS_ADM_UTL package (Scored)
............................................................................................................................................................................................... 82
4.2.7 Limiting public user access to the DBMS_AQADM_SYS package (Scored) ................. 83
4.2.8 Limiting public user access to the DBMS_STREAMS_RPC package (Scored)............ 84
4.2.9 Limiting public user access to the DBMS_AQADM_SYS package (Scored) ................. 84
4.2.10 Limiting public user access to the DBMS_PRVTAQIM package (Scored) ................. 85
4.2.11 Limiting public user access to the LTADM package (Scored) ......................................... 85
4.2.12 Limiting public user access to the WWV_DBMS_SQL package (Scored)................... 86
4.2.13 Limiting public user access to the WWV_EXECUTE_IMMEDIATE package
(Scored) ........................................................................................................................................................................... 87
4.2.14 Limiting public user access to the DBMS_IJOB package (Scored) ................................ 87
4.2.15 Limiting public user access to the DBMS_FILE_TRANSFER package (Scored)..... 88
4.3 System Privileges ................................................................................................................................................... 89
5|Pa ge
4.3.1 Limiting users by restricting the SELECT ANY DICTIONARY privilege (Scored) .. 89
4.3.2 Limiting users by restricting the SELECT ANY TABLE privilege (Scored)................. 90
4.3.3 Limiting users by restricting the AUDIT SYSTEM privilege (Scored) ........................... 90
4.3.4 Limiting users by restricting the EXEMPT ACCESS POLICY (Scored)........................... 91
4.3.5 Limiting users by restricting the BECOME USER privilege (Scored)............................. 92
4.3.6 Limiting users by restricting the CREATE PROCEDURE privilege (Scored) ............. 92
4.3.7 Limiting users by restricting the ALTER SYSTEM privilege (Scored)........................... 93
4.3.8 Limiting users by restricting the CREATE ANY LIBRARY privilege (Not Scored) . 94
4.3.9 Limiting users by restricting GRANT ANY OBJECT PRIVILEGE privilege (Scored)
............................................................................................................................................................................................... 95
4.3.10 Limiting users by restricting GRANT ANY ROLE privilege (Scored) .......................... 95
4.3.11 Limiting users by restricting GRANT ANY PRIVILEGE privilege (Scored).............. 96
4.4 Role Privileges.......................................................................................................................................................... 97
4.4.1 Limiting user authorizations for the DELETE_CATALOG_ROLE (Not Scored) ........ 97
4.4.2 Limiting user authorizations for the SELECT_CATALOG_ROLE (Not Scored) ......... 98
4.4.3 Limiting user authorizations for the EXECUTE_CATALOG role (Not Scored).......... 98
4.4.4 Limiting users by restricting the DBA role (Not Scored) ...................................................... 99
4.5 Table and View privileges.............................................................................................................................. 100
4.5.1 Limiting authorizations for the SYS.AUD$ table (Scored)................................................. 100
4.5.2 Limiting authorizations for the SYS.USER_HISTORY$ table (Scored)........................ 100
4.5.3 Limiting authorizations for the SYS.LINK$ table (Scored)................................................ 101
4.5.4 Limiting authorizations for the SYS.USER$ table (Scored)............................................... 102
4.5.5 Limiting user authorizations for the DBA_% views (Scored) ......................................... 102
4.5.6 Limiting authorizations for the SCHEDULER$_CREDENTIAL table (Scored) ....... 103
4.5.7 Drop table sys.user$mig (Scored).................................................................................................... 104
4.6 Limiting basic user privileges to restrict the ANY keyword (Scored) ........................... 104
4.7 Limiting users by restricting the WITH_ADMIN privilege (Scored) ............................... 105
4.8 Limit direct privileges for proxy user (Scored) ........................................................................... 106
4.9 Revoke execute any procedure from user OUTLN (Scored) ................................................ 106
4.10 Revoke execute any procedure from user DBSNMP (Scored) ......................................... 107
5 Audit/Logging Policies and Procedures.................................................................................................... 108
6|Pa ge
5.1 Audit all CREATE SESSION (logon/logoff) activities (Scored) ........................................... 108
5.2 Audit all CREATE USER object activities/requests (Scored)............................................... 108
5.3 Audit all ALTER USER object activities/requests (Scored).................................................. 109
5.4 Audit all DROP USER object activities/requests (Scored) .................................................... 110
5.5 Audit all user ROLE activities/requests (Scored)....................................................................... 110
5.6 Audit all user GRANT ROLE activities/requests (Scored)..................................................... 111
5.7 Audit all user CREATE PROFILE activities/requests (Scored) ........................................... 112
5.8 Audit all user ALTER PROFILE activities/requests (Scored).............................................. 112
5.9 Audit all user DROP PROFILE activities/requests (Scored) ................................................ 113
5.10 Audit all DATABASE LINK activities/requests (Scored) ..................................................... 113
5.11 Audit all PUBLIC DATABASE LINK activities/requests (Scored)................................... 114
5.12 Audit all PUBLIC SYNONYM activities/requests (Scored)............................................... 115
5.13 Audit all user SYNONYM activities/requests (Scored)......................................................... 115
5.14 Audit all grants and revokes of privileges on directories (Scored) .............................. 116
5.15 Audit all user SELECT ANY DICTIONARY activities/requests (Scored) .................... 117
5.16 Audit all user GRANT ANY OBJECT PRIVILEGE activities/requests (Scored) ....... 117
5.17 Audit all user GRANT ANY PRIVILEGE activities/requests (Not Scored)................. 118
5.18 Audit all user CREATE PROCEDURE activities/requests (Scored) ............................... 119
5.19 Audit all user CREATE ANY PROCEDURE activities/requests (Scored).................... 120
5.20 Audit all user ALTER ANY PROCEDURE activities/requests (Scored) ....................... 120
5.21 Audit all user DROP ANY PROCEDURE activities/requests (Scored) ......................... 121
5.22 Audit all user CREATE ANY LIBRARY activities/requests (Sco red) ............................ 121
5.23 Audit all user DROP ANY LIBRARY activities/requests (Scored).................................. 122
5.24 Audit all user CREATE ANY TRIGGER activities/requests (Scored) ............................ 123
5.25 Audit all user ALTER ANY TRIGGER activities/requests (Scored) ............................... 123
5.26 Audit all user DROP ANY TRIGGER activities/requests (Scored).................................. 124
5.27 Set AUDIT ALL ON SYS.AUD$ activities (Scored)..................................................................... 124
5.28 Audit all user ALTER SYSTEM activities/requests (Scored)............................................. 125
Appendix: Change History .......................................................................................................................................... 127
7|Pa ge
Overview
This document is intended to address the recommended security settings for the Oracle
11g, r2 Database , running on either an x86 (32-bit) or x64 (64-bit) AMD/Intel chip
platform. This guide was tested against Amazon ami-3d739c54 and against the Intel x64
chip running a 64-bit version of Oracle Linux 2.6.18-194 configured as a stand-alone
system, running as a "Database server," including all Oracle CPUs up through April 15,
2012. Future Oracle 11g r2 critical patch updates (CPUs) may impact the recommend ations
included in this document.
To obtain the latest version of this guide, please visit http://benchmarks.cisecurity.org. If

you have questions, comments, or have identified ways to improve this guide, please write
us at [email protected].
Intended Audience
This benchmark is intended for system and application administrators, security specialists,
auditors, help desk, and platform deployment personnel who plan to develop, deploy,
assess, or secure solutions that incorporate Oracle Database Server 11g R2 on Or acle Linux
or Microsoft Windows Server.
Consensus Guidance
This benchmark was created using a consensus review process comprised of volunteer and
contract subject matter experts. Consensus participants provide perspective from a diverse
set of backgrounds including consulting, software development, audit and compliance,
security research, operations, government, and legal.
Each CIS benchmark undergoes two phases of consensus review. The first phase occurs
during initial benchmark development. During this phase, subject matter experts convene
to discuss, create, and test working drafts of the benchmark. This discussion occurs until
consensus has been reached on benchmark recommendations. The second phase begins
after the benchmark has been released to the public Internet. During this phase, all
feedback provided by the Internet community is reviewed by the consensus team for
incorporation in the benchmark. If you are interested in participating in the consensus
review process, please send us a note to [email protected].
8|Pa ge
Typographical Conventions
The following typographical conventions are used throughout this guide:
Convention Meaning
Stylized Monospace font Used for blocks of code, command, and script examples.
Text should be interpreted exactly as presented.
Monospace font Used for inline code, commands, or examples. Text should
be interpreted exactly as presented.
<italic font in brackets> Italic texts set in angle brackets denote a variable
requiring substitution for a real value.
Italic font Used to denote the title of a book, article, or other
publication.
Note Additional information or caveats
Scoring Information
A scoring status indicates whether compliance with the given recommendation impacts the
assessed target's benchmark score. The following scoring statuses are used in this
benchmark:
Scored
Failure to comply with "Scored" recommendations will decrease the final benchmark score.
Compliance with "Scored" recommendations will increase the final benchmark score.
Not Scored
Failure to comply with "Not Scored" recommendations will not decrease the final
benchmark score. Compliance with "Not Scored" recommendations will not increase the
final benchmark score.
9|Pa ge
Profile Definitions
The following configuration profiles are defined by this Benchmark:
Level 1 - 11.x on any platform
Items in this profile apply to Oracle Database 11g and intend to:
o be practical and prudent;

o provide a clear security benefit; and
o not negatively inhibit the utility of the technology beyond acceptable means.
Level 1 - 11.2 on any platform
This profile extends the "Level 1 - 11.x on any platform" profile. Items in this profile
apply to Oracle Database 11g R2 and exhibit one or more of the following
characteristics:
Items in this profile intend to:
o be practical and prudent;

o provide a clear security benefit; and
o not negatively inhibit the utility of the technology beyond acceptable means.
10 | P a g e
Acknowledgements
This benchmark exemplifies the great things a community of users, vendors, and subject matter
experts can accomplish through consensus collaboration. The CIS community thanks the entire
consensus team with special recognition to the following individuals who contributed greatly to
the creation of this guide:
Author
Alan Covell
Contributor
Andy McConnell
Johan Verbrugghen
Don Granaman , Solutionary
Andre van Winssen CISSP, CISA, CEH, Oracle Certified Master 10g/11g
Stephen Suddeth
Andy Peters
Alf-Ivar Holm
Surachart Opun
Ron Reidy
Louis Lam
Editor
Alexander Kornbrust
Paul Wright OCP and GSOC
11 | P a g e
Recommendations
1 Oracle Database Installation and Patching Requirements
One of the best ways to ensure secure Oracle security is to implement Critical Patch
Updates (CPUs) as they come out, along with any applicable OS patches that will not
interfere with system operations.
1.1 Change the Oracle default account passwords

Depending from the chosen installation method, Oracle 11gR2 creates a number of well-
known, default accounts with default passwords, which are normally locked and expired.
The majority of these default accounts are powerful and allow to overtake the data base if
the account is open. That's why the passwords of these accounts should be changed
immediately to avoid that unlocking and unexpiring the account opens a security hole in
the database.
Any of these accounts that are not required can potentially be deleted, but extensive testing
should be should be done in a non-Production environment prior to removing a default
account, to avoid breaking critical processes associated with legacy applications.
A password change in Oracle 11 could be done using 4 different ways (alter user, grant, OCI
password call and direct update on SYS.USER$ (unsupported)). The disadvantage of the
alter user and grant syntax is that the password is transferred in clear text over the
network.
The SQL*Plus password command is transferring the encrypted password over the
network but the Oracle client has to be compatible to the database (e.g. 11.2.0.2 client can't
use the password against 11.2.0.3 due to API changes in the appropriate OCI call).
If the alter user syntax is used, the command should be executed on the database server
itself.
1.1.1 Change the default password for 'APEX_040000' (Scored)

Profile Applicability:
12 | P a g e
Description:
The APEX_040000 account owns the greatest part of the objects created by the database
during the installation of Oracle Database Application Express (ODAE).
Rationale:
Some pre-installed versions of APEX 4.0 come with a default password and can provide a
point for database access/control by unauthorized users, opening up the tables, views, etc..
Audit:
select 'defaultpwd' as defaultpassword

from sys.user$
where name='APEX_040000'
and
substr(spare4,3,40)=rawtohex(utl_raw.cast_to_varchar2(sys.dbms_crypto.hash(utl_raw.cas
t_to_raw('oracle')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from sys.user$ where name='APEX_040000' and
password='EE7785338B8FFE3D';
Remediation:
Execute the following command to change the password

SQL> password apex_040000
Enter the new password twice:

Changing password for apex_040000
New password:
Retype new password:
Password changed
1.1.2 Change the default password for 'APPQOSSYS' (Scored)

Description:
The APPQOSSYS account manages/owns all Quality of Service objects and provides an
intuitive, policy-driven system to manage service level requirements.
Rationale:
As the default APPQOSSYS account created by Oracle has a well-known password and can
provide a point for database access by unauthorized users if left at the default setting, this
value should be changed according to the needs of the organization.
13 | P a g e
Audit:

from sys.user$
where name='APPQOSSYS'
and
t_to_raw('appqossys')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='APPQOSSYS';
Remediation:

SQL> password appoqssys

Changing password for appqossys
New password:
Password changed
1.1.3 Change the default password for 'CTXSYS' (Scored)

Description:
The CTXSYS is used to administer Oracle Text.
Rationale:
As the default CTXSYS account created by Oracle has a well-known password and can
Audit:

from sys.user$
where name='CTXSYS'
and
t_to_raw('ctxsys')||hextoraw(substr(spare4,43,20)), 3)))
union
from sys.user$
where name='CTXSYS'
and
t_to_raw('change_on_install')||hextoraw(substr(spare4,43,20)), 3)))
14 | P a g e
union
select 'defaultpwd' from dba_users_with_defpwd where username='CTXSYS';
Remediation:

SQL> password ctxsys

Changing password for ctxsys
New password:
Password changed
References:
1. http://docs.oracle.com/cd/E11882_01/server.112/e10575/tdpsg_user_accounts.ht
m#TDPSG20030
1.1.4 Change the default password for 'DBSNMP' (Scored)

Description:
The DBSNMP account is used by the Oracle Enterprise Manager to monitor and manage the
database.
Rationale:
Depending from the installation, the default DBSNMP account created by Oracle could have a
well-known password and can be potentially used to retrieve the Oracle password hashes.
Audit:

from sys.user$
where name='DBSNMP'
and
t_to_raw('dbsnmp')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='DBSNMP';
Remediation:

SQL> password dbsnmp
15 | P a g e
Changing password for dbsnmp
New password:
Password changed
References:
m#TDPSG20030
1.1.5 Change the default password for 'DIP' (Scored)

Description:
The DIP account supports the operation of the Oracle Internet Directory and Oracle Label
Security.
Rationale:
As the default DIP account created by Oracle has a well-known password and can provide a
point for database access by unauthorized users if left at the default setting, this value
should be changed according to the needs of the organization.
Audit:

from sys.user$
where name='DIP'
and
t_to_raw('dip')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='DIP';
Remediation:

SQL> password dip

Changing password for dip
New password:
Password changed
References:
16 | P a g e
1. http://docs.oracle.com/cd/E11882_01/server.112/e25513/statviews_5082.htm#R
EFRN23725
1.1.6 Change the default password for 'EXFSYS' (Scored)

Description:
The EXFSYS account accesses the EXFSYS schema, which facilitates use of the Rules Manager
and Expression Filter feature and allows the user to build complex PL/SQL rules and
expressions.
Rationale:
As the default EXFSYS account created by Oracle has a well-known password and can
Audit:

from sys.user$
where name='EXFSYS'
and
t_to_raw('exfsys')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='EXFSYS';
Remediation:

SQL> password exfsys

Changing password for exfsys
New password:
Password changed
1.1.7 Change the default password for 'MDDATA' (Scored)

Description:
17 | P a g e
The MDDATA account owns the schema used by Oracle Spatial for storing Geocoder and
router data, which allows the plotting of datapoints, such as market locations/types,
against latitude and longitude on a map, in a way similar to a GPS presentation.
Rationale:
As the default MDDATA account created by Oracle has a well-known password and can be
potentially corrupted to allow the installation of malware disguised as a business process,
this value should be reset according to the needs of the organization.
Audit:

from sys.user$
where name='MDDATA'
and
t_to_raw('mddata')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='MDDATA';
Remediation:

SQL> password mddata

Changing password for mddata
New password:
Password changed
1.1.8 Change the default password for 'MDSYS' (Scored)

Description:
The MDSYS is the user in that operationalizes the Oracle Multimedia Locator, which serves
as part of the storage, management, and retrieval of audio/video images.
Rationale:
As the default MDSYS account created by Oracle has a well-known password and can be
potentially corrupted to allow the installation of malware disguised and AV plugins, this
value should be reset according to the needs of the organization.
18 | P a g e
Audit:

from sys.user$
where name='MDSYS'
and
t_to_raw('sys')||hextoraw(substr(spare4,43,20)), 3)))
union
from sys.user$
where name='MDSYS'
and
t_to_raw('mdsys')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='MDSYS';
Remediation:

SQL> password mdsys

Changing password for mdsys
New password:
Password changed
1.1.9 Change the default password for 'LBACSYS' (Scored)

Description:
The LBACSYS account administers the Oracle Label Security (OLS) feature.
Rationale:
As the default LBACSYS account created by Oracle has a well-known password and can
provide a point for database access/control by unauthorized users, opening up the tables,
views, etc. This value should be changed according to the needs of the organization.
Audit:

from sys.user$
where name='LBACSYS'
and
t_to_raw('lbacsys')||hextoraw(substr(spare4,43,20)), 3)))
19 | P a g e
union
select 'defaultpwd' from dba_users_with_defpwd where username='LBACSYS';
Remediation:

SQL> password lbacsys

Changing password for lbacsys
New password:
Password changed
1.1.10 Change the default password for 'OLAPSYS' (Scored)

Description:
The OLAPSYS account owns the online analytical processing (OLAP) catalog. OLAP
applications are developed/operate to use business intelligence and data warehousing
systems and OLAP is optimized for this type of application.
Rationale:
As the default OLAPSYS account created by Oracle has a well-known password and can be
potentially corrupted to allow the installation of malware disguised as a business process,
Audit:

from sys.user$
where name='OLAPSYS'
and
t_to_raw('manager')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='OLAPSYS';
Remediation:

SQL> password olapsys

Changing password for olapsys
New password:
20 | P a g e
Password changed
1.1.11 Change the default password for 'ORACLE_OCM' (Scored)

Description:
The ORACLE_OCM account supports the operation of the Configuration Manager with the
instance and MyOracleSupport.
Rationale:
As the default ORACLE_OCM account created by Oracle has a well-known password and can
Audit:

from sys.user$
where name='ORACLE_OCM'
and
t_to_raw('oracle_ocm')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='ORACLE_COM';
Remediation:

SQL> password oracle_ocm

Changing password for oracle_ocm
New password:
Password changed
References:
EFRN23725
1.1.12 Change the default password for 'ORDDATA' (Scored)

21 | P a g e
Description:
The ORDDATA user operationalizes/owns the Oracle Multimedia DICOM modality: Digital
Imaging and Communications in Medicine (DICOM), which is the industry standard for
medical imaging, enables the Database to store, manage, and manipulate all DICOM format
medical content.
Rationale:
As the default ORDDATA account created by Oracle has a well-known password and can be
potentially corrupted to allow the installation of malware disguised as AV plugins, or cause
a Denial-of-Service condition by deleting the account, this value should be reset according
to the needs of the organization.
Audit:

from sys.user$
where name='ORDDATA'
and
t_to_raw('orddata')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='ORDDATA';
Remediation:

SQL> password orddata

Changing password for orddata
New password:
Password changed
1.1.13 Change the default password for 'ORDPLUGINS' (Scored)

Description:
The ORDPLUGINS provide the plugins to enable the database to store, manage, and retrieve
audio/video images, such as the DICOM medical data format .
Rationale:
22 | P a g e
As the default ORDPLUGINS account created by Oracle has a well-known password and can
be potentially corrupted to allow the installation of malware disguised and AV plugins, this
value should be reset according to the needs of the organization.
Audit:

from sys.user$
where name='ORDPLUGINS'
and
t_to_raw('ordplugins')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='ORDPLUGINS';
Remediation:

SQL> password ordplugins

Changing password for ordplugins
New password:
Password changed
1.1.14 Change the default password for 'ORDSYS' (Scored)

Description:
The ORDSYS user functions as the Oracle Multimedia administrator. DICOM

modality: Digital Imaging and Communications in Medicine (DICOM), which is the industry
standard for medical imaging, enables the Database to store, manage, and manipulate all
DICOM format medical content.
Rationale:
As the default ORDDATA account created by Oracle has a well-known password and can be
potentially corrupted to allow the installation of malware disguised as AV plugins, or cause
a Denial-of-Service condition by deleting the account, this value should be reset according
Audit:

from sys.user$
23 | P a g e
where name='ORDSYS'
and
t_to_raw('ordsys')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='ORDSYS';
Remediation:

SQL> password ordsys

Changing password for ordsys
New password:
Password changed
1.1.15 Change the default password for 'OUTLN' (Scored)

Description:
The OUTLN user helps preserve application stability by preventing changes to the database
environment from overly impacting system performance characteristics.
Rationale:
As the default OUTLN account created by Oracle has a well-known password and can
Audit:

from sys.user$
where name='OUTLN'
and
t_to_raw('outln')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='OUTLN';
Remediation:

SQL> password outln
24 | P a g e
Changing password for outln
New password:
Password changed
References:
EFRN23725
1.1.16 Change the default password for 'OWBSYS_AUDIT' (Scored)

Description:
The OWBSYS_AUDIT account handles access to the OWBSYS audit/logging tables, which
record Warehouse Builder workspace and user analysis/query operations.
Rationale:
As the default OWBSYS_UDIT account created by Oracle has a well-known password and can
be potentially used to take alter the audit/logging tables to alter/delete forensic data that
can reveal unauthorized access/alteration of data, this value should be reset according to
the needs of the organization.
Audit:

from sys.user$
where name='OWBSYS_AUDIT'
and
t_to_raw('owbsys_audit')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='OWBSYS_AUDIT';
Remediation:

SQL> password owbsys_audit

Changing password for owbsys_audit
New password:
Password changed
25 | P a g e
1.1.17 Change the default password for 'OWBSYS' (Scored)
Description:
The OWBSYS account handles Oracle Warehouse Builder database administrative tasks,
which is created during installation and defines the language of repository for the
Warehouse Builder workspaces and user analysis/query operations.
Rationale:
As the default OWBSYS account created by Oracle has a well-known password and can be
potentially used to take over the database warehouse structures or access user queries,
Audit:

from sys.user$
where name='OWBSYS'
and
t_to_raw('owbsys')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='OWBSYS';
Remediation:

SQL> password owbsys

Changing password for owbsys
New password:
Password changed
1.1.18 Change the default password for 'SI_INFORMTN_SCHEMA'

(Scored)
Description:
26 | P a g e
The SI_INFORMTN_SCHEMA functions as the location for storing plugins supplied by Oracle
and all other third-party plugins.
Rationale:
As the default SI_INFORMTN_SCHEMA account created by Oracle has a well-known password

and can be potentially corrupted to allow the installation of malware disguised as third -
party multimedia plugins, this value should be reset according to the needs of the
organization.
Audit:

from sys.user$
where name='SI_INFORMTN_SCHEMA'
and
t_to_raw('si_informtn_schema')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='SI_INFORMTN_SCHEMA';
Remediation:

SQL> password si_informtn_schema

Changing password for si_informtn_schema
New password:
Password changed
1.1.19 Change the default password for 'SPATIAL_CSW_ADMIN_USR'

(Scored)
Description:
The SPATIAL_CSW_ADMIN_USR account owns the Catalog Services for the Web (CSW)
capabilities, which are used by Oracle to load record-type metadata and instances from the
DB into the main memory when these records are cached.
Rationale:
27 | P a g e
As the default SPATIAL_CSW_ADMIN_USR account created by Oracle has a well-known
password and can be potentially corrupted to allow the installation of malware disguised
as a business process, this value should be reset according to the needs of the organization.
Audit:

from sys.user$
where name='SPATIAL_CSW_ADMIN_USR'
and
t_to_raw('spatial_csw_admin_usr')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='SPATIAL_CSW_ADMIN_USR';
Remediation:

SQL> password spatial_csw_admin_usr

Changing password for spatial_csw_admin_usr
New password:
Password changed
1.1.20 Change the default password for 'SPATIAL_WFS_ADMIN_USR'

(Scored)
Description:
The SPATIAL_WFS_ADMIN_USR account owns the Web Feature Service (WFS) capabilities,
which are used by Oracle to load feature instance/metadata from the DB into the main
memory when these are pulled from a cache.
Rationale:
As the default SPATIAL_WFS_ADMIN_USR account created by Oracle has a well-known

password and can be potentially corrupted to allow the installation of malware disguised
as a business process, this value should be reset according to the needs of the organization.
Audit:

from sys.user$
28 | P a g e
where name='SPATIAL_WFS_ADMIN_USR'
and
t_to_raw('spatial_wfs_admin_usr')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='SPATIAL_WFS_ADMIN_USR';
Remediation:

SQL> password spatial_wfs_admin_usr

Changing password for spatial_wfs_admin_usr
New password:
Password changed
1.1.21 Change the default password for 'SYS' (Scored)

Description:
The SYS account is the highest level user created by the database installation.
Rationale:
Older versions of Oracle had a well-known password and with the "SYS and SYSDBA" login
provides the most powerful a point for an unauthorized user if left at the default setting,
this value should be changed according to the needs of the organization.
Audit:

from sys.user$
where name='SYS'
and
union
from sys.user$
where name='SYS'
and
union
from sys.user$
where name='SYS'
29 | P a g e
and
t_to_raw('d_syspw')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='SYS';
Remediation:

SQL> password sys

Changing password for sys
New password:
Password changed
References:
EFRN23725
2. http://www.oracleforensics.com/wordpress/index.php/2012/10/24/sys_throttler
-and-distributed-database-forensics/
1.1.22 Change the default password for 'SYSTEM' (Scored)

Description:
The SYSTEM user is created for administrative purposes during the database installation.
Rationale:
In older versions of Oracle the default SYSTEM account had a well-known password and can
provide a point for full dba access by unauthorized users if left at the default setting, this
Audit:

from sys.user$
where name='SYSTEM'
and
union
from sys.user$
30 | P a g e
where name='SYSTEM'
and
t_to_raw('d_systpw')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='SYSTEM';
Remediation:

SQL> password system

Changing password for system
New password:
Password changed
References:
EFRN23725
1.1.23 Change the default password for 'WK_TEST' (Scored)

Description:
The WK_TEST account handles access to Oracle Ultrasearch
Rationale:
As the default WK_TEST account created by Oracle has a well-known password and can be
potentially used to take alter the tables or alter/delete forensic data, this value should be
reset according to the needs of the organization.
Audit:

from sys.user$
where name='WK_TEST'
and
t_to_raw('wk_test')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='WK_TEST';
31 | P a g e
Remediation:

SQL> password wk_test

Changing password for wk_test
New password:
Password changed
1.1.24 Change the default password for 'WKPROXY' (Scored)

Description:
The WKPROXY account handles the Oracle 9i Application Ultra Search.
Rationale:
As the default WKPROXY account created by Oracle has a well-known password and can be
potentially used to take alter the tables or alter/delete forensic data, this value should be
reset according to the needs of the organization.
Audit:

from sys.user$
where name='WKPROXY'
and
union
from sys.user$
where name='WKPROXY'
and
t_to_raw('wkproxy')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='WKPROXY';
Remediation:

SQL> password wkproxy

Changing password for wkproxy
New password:
32 | P a g e
Password changed
1.1.25 Change the default password for 'WKSYS' (Scored)

Description:
The WKSYS account is the Ultra Search administrator.
Rationale:
As the default WKSYS account created by Oracle has a well-known password and can
Audit:

from sys.user$
where name='WKSYS'
and
t_to_raw('wksys')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='WKSYS';
Remediation:

SQL> password wksys

Changing password for wksys
New password:
Password changed
1.1.26 Change the default password for 'WMSYS' (Scored)

Description:
33 | P a g e
The WMSYS account stores manages all metadata for the Workspace manager, which
provides a virtual environment to isolate workspaces, such as a collection of changes to
production data, or keep a changes history, allowing the creation of "what if scenarios.
Rationale:
As the default WMSYS account created by Oracle has a well-known password and can
Audit:

from sys.user$
where name='WMSYS'
and
t_to_raw('wmsys')||hextoraw(substr(spare4,43,20)), 3)))
union
select 'defaultpwd' from dba_users_with_defpwd where username='WMSYS';
Remediation:

SQL> password wmsys

Changing password for wmsys
New password:
Password changed
1.1.27 Change the default password for 'XDB' (Scored)

Description:
The XDB account enables high-performance storage and retrieval of XML data.
Rationale:
As the default XDB account created by Oracle has a well-known password and can provide a
point for database access by unauthorized users if left at the default setting, this value
should be changed according to the needs of the organization.
Audit:
34 | P a g e
from sys.user$
where name='XDB'
and
t_to_raw('xdb')||hextoraw(substr(spare4,43,20)), 3)))
union
from sys.user$
where name='XDB'
and
union
select 'defaultpwd' from dba_users_w ith_defpwd where username='XDB';
Remediation:

SQL> password xdb

Changing password for xdb
New password:
Password changed
1.2 Remove Oracle Sample Users

Oracle sample schemas are not needed for the operation of the database. That's why the
Oracle sample users (BI,HR,OE,PM,IX,SH, SCOTT) should be removed after checking the the
schema are really sample schema.
1.2.1 Remove the sample user 'BI' (Scored)

Description:
The BI account owns the Business Intelligence (BI) sample schema.
Rationale:
As the default BI account created by Oracle has a well-known password and can be
potentially used to alter the database to launch exploits against Production to gain
unauthorized access to user data, this value should be reset according to the needs of the
organization.
Audit:
35 | P a g e
Ensure the BI user does not exist by executing the following query:
SQL> SELECT username FROM ALL_USERS WHERE USERNAME='BI';
Remediation:
Execute the following SQL to drop the BI user and all objects in the user's schema.
SQL> DROP USER BI CASCADE;
References:
m#TDPSG20303
1.2.2 Remove the sample user 'HR' (Scored)

Description:
The HR account is used to manage the HR (Human Resources) sample schema.
Rationale:
As the default HR account created by Oracle has a well-known password and can be
organization.
Audit:
Ensure the HR user does not exist by executing the following SQL:
SQL> SELECT username FROM ALL_USERS WHERE USERNAME='HR';
Remediation:
Execute the following SQL to drop the HR user and all objects in the user's schema:
SQL> DROP USER HR CASCADE;
References:
36 | P a g e
1. http://docs.oracle.com/cd/E11882_01/server.112/e10831/scripts.htm#autoId3
m#TDPSG20303
1.2.3 Remove the sample user 'IX' (Scored)

Description:
The IX account is used to manage the Information eXchange (IX) sample schema.
Rationale:
As the default IX account created by Oracle has a well-known password and can be
organization.
Audit:
Ensure the IX user does not exist by executing the following query:
SQL> SELECT username FROM ALL_USERS WHERE USERNAME='IX';
Remediation:
Execute the following SQL to drop the IX user and all objects in the user's schema.
SQL> DROP USER IX CASCADE;
References:
m#TDPSG20303
1.2.4 Remove the sample user 'OE' (Scored)

Description:
37 | P a g e
The OE account is used to manage the Order Entry (OE) sample schema.
Rationale:
As the default OE account created by Oracle has a well-known password and can be
organization.
Audit:
Ensure the OE user does not exist by executing the following query:
SQL> SELECT username FROM ALL_USERS WHERE USERNAME='OE';
Remediation:
Execute the following SQL to drop the OE user and all objects in the user's schema.
SQL> DROP USER OE CASCADE;
References:
m#TDPSG20303
1.2.5 Remove the sample user 'PM' (Scored)

Description:
The PM account is used to manage the product media (PM) sample schema for Business-to-
Business.
Rationale:
As the default PM account created by Oracle has a well-known password and can be
organization.
Audit:
38 | P a g e
Ensure the user PM does not exist by executing the following query:
SQL> SELECT username FROM ALL_USERS WHERE USERNAME='PM';
Remediation:
Execute the following SQL to drop the PM user and all objects in the user's schema:
SQL> DROP USER PM CASCADE;
References:
m#TDPSG20303
1.2.6 Remove the sample user 'SCOTT' (Scored)

Description:
The SCOTT account is used in examples throughout the Oracle database.
Rationale:
As the default SCOTT account created by Oracle has a well-known password and can be
potentially used to alter the database or to launch exploits against Production to gain
organization.
Audit:
Ensure the user SCOTT does not exist by executing the following query:
SQL> SELECT username FROM ALL_USERS WHERE USERNAME='SCOTT';
Remediation:
Execute the following SQL to drop the SCOTT user and all objects in the user's schema.
SQL> DROP USER SCOTT CASCADE;
39 | P a g e
References:
m#TDPSG20303
1.2.7 Remove the sample user 'SH' (Scored)

Description:
The SH account is used to manage the SH sales history schema, which stores business data.
Rationale:
As the default SH account created by Oracle has a well-known password and can be
organization.
Audit:
Ensure the SH user does not exist by executing the following query:
SQL> SELECT username FROM ALL_USERS WHERE USERNAME='SH';
Remediation:
Execute the following SQL to drop the BI user and all objects in the user's schema.
SQL> DROP USER SH CASCADE;
References:
m#TDPSG20303
1.3 Ensure the latest version/patches for Oracle software is installed

(Not Scored)
40 | P a g e
Description:
The Oracle installation version, along with the patch level, should be the most recent that is
compatible with the organizations' operational needs.
There are two ways to detect the patch level. Opatch is (only) checking if the files at the
operating system level are patched properly. The view DBA_REGISTRY_HISTORY shows if
the database related part was applied. If the result from DBA_REGISTRY_HISTORY is empty
no (security) patch was applied
To be on the safe side, the view DBA_REGISTRY history should be queried.
Rationale:
As using the most recent Oracle database software, along with all applicable patches can
help limit the possibilities for vulnerabilities in the software, the installation version
and/or patches applied during setup should be established according to the needs of the
organization.
Audit:
# opatch lsinventory -detail
and
SQL> select * from DBA_REGISTRY_HISTORY;
Remediation:
Download the apropriate patch (PSU, CPU) and apply it against the database. See
readme.txt for more details.
References:
1. http://www.oracle.com/us/support/assurance/fixing-policies/index.html
2. http://www.oracle.com/technetwork/topics/security/alerts-086861.html
2 Oracle Parameter Settings

The operation of the Oracle database instance is governed by numerous parameters that
are set in specific configuration files and are instance-specific in scope. As alterations of
these parameters can cause problems ranging from denial -of-service to theft of
41 | P a g e
proprietary information, these configurations should be carefully considered and
maintained.
Note:
For all files that have parameters that can be modified with the OS and/or SQL
commands/scripts, these will both be listed where appropriate.
2.1 listener.ora settings

Settings for the TNS Listener listener.ora
2.1.1 Setting for 'secure_control_listener_name' parameter (Scored)

Description:
The SECURE_CONTROL_listener_name setting determines the type of control connection the

Oracle server requires for remote configuration of the listener.
Rationale:
As listener configuration changes via unencrypted remote connections can result in

unauthorized users sniffing the control configuration information from the network, these
control values should be set according to the needs of the organization.
Audit:
$ grep -i SECURE_CONTROL $ORACLE_HOME/network/admin/listener.ora
Remediation:
Set the SECURE_CONTROL_<listener_name> according to the needs of the organization.
References:
1. http://docs.oracle.com/cd/E11882_01/network.112/e10835/listener.htm#NETRF
327
2.1.2 extproc configuration in listener.ora (Scored)

42 | P a g e
Description:
Oracle Extproc allows to run procedures from operating system libraries. These library
calls can allow to run any operating system command.
Rationale:
Extproc should be removed from the listener.ora to avoid that attackers are abusing the
external procedure feature.
Audit:
$ grep -i extproc $ORACLE_HOME/network/admin/listener.ora
Remediation:
Remove extproc from the listener.ora.
References:
1. http://docs.oracle.com/cd/E11882_01/network.112/e10836/advcfg.htm#NETAG0
132
2.1.3 Setting for the 'admin_restrictions_listener_name' parameter

(Scored)
Description:
The admin_restrictions_<listener_name> setting in the listener.ora file can require

that any attempted real-time alteration of the parameters in the listener via the set
command file be refused unless the listener.ora file is manually altered then restarted by
a privileged user.
Rationale:
As blocking unprivileged users from making alterations of the listener.ora file, where
remote data/services are specified, will help protect data confidentiality, this value should
be set to the needs of the organization.
43 | P a g e
Audit:
$ grep -i admin_restrictions \
$ORACLE_HOME/network/admin/listener.ora
$ (not set by default)
Remediation:
Set the ADMIN_RESTRICTIONS_<listener_name> to the value ON.
References:
310
2.1.4 Change the default port numbers that connect to Oracle (Scored)
Description:
The Oracle installation creates a number of well-known ports for connections to the
listener service; these ports which are often targeted by unauthorized users' automated
exploits.
Rationale:
As the default ports created by Oracle can provide a target for exploits by unauthorized
users, the ports should be changed according to the needs of the organization.
Audit:
$ grep 1521 $ORACLE_HOME/network/admin/listener.ora
Remediation:
(new port example is "1527")
$ sed -e 's/1521/1527/' <$ORACLE_HOME/network/admin/listener.ora>

$ORACLE_HOME/network/admin/listener.ora.new mv
$ORACLE_HOME/network/admin/listener.ora.new $ORACLE_HOME/network/admin/listener.ora;
fi
44 | P a g e
2.1.5 Setting for parameter 'secure_register_listener_name' parameter
(Scored)
Description:
The SECURE_REGISTER_<listener_name> setting specifies the protocols which are used to

connect to the TNS listener.
Rationale:
As listener configuration changes via unencrypted remote connections can result in

unauthorized users sniffing the control configuration information from the network, these
control values should be set according to the needs of the organization.
Audit:
$ grep -i SECURE_REGISTER $ORACLE_HOME/network/admin/listener.ora
Remediation:
Use a text editor such as vi to set the SECURE_REGISTER_listener_name=TCPS or

SECURE_REGISTER_listener_name=IPC under the SECURE_REGISTER_listenername= parameter
found in $ORACLE_HOME/network/admin/listener.ora
References:
328
2. https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=145388
3.1
1.1
4. http://www.joxeankoret.com/download/tnspoison.pdf
2.2 sqlnet.ora settings

Settings for sqlnet.ora
2.3 Setting for the 'audit_sys_operations' parameter (Scored)

45 | P a g e
Description:
The AUDIT_SYS_OPERATIONS setting provides for the auditing of all user activities conducted
under the SYSOPER and SYSDBA accounts.
Rationale:
If the parameter AUDIT_SYS_OPERATIONS is FALSE all statements except of

Startup/Shutdown and Logon by SYSDBA/SYSOPER users are not audited.
Audit:
SQL> select value from v$parameter where upper(name)='AUDIT_SYS_OPERATIONS';
Remediation:
SQL> ALTER SYSTEM SET AUDIT_SYS_OPERATIONS = true SCOPE=SPFILE;
References:
1. http://docs.oracle.com/cd/E11882_01/server.112/e25513/initparams015.htm#R
EFRN10005
2.4 Setting for the 'audit_trail' parameter (Scored)

Description:
The audit_trail setting determines whether or not Oracle's basic audit features are
enabled. These can be set to "Operating System"(OS), "DB,", "DB,EXTENDED", "XML"
or "XML,EXTENDED".
Rationale:
As enabling the basic auditing features for the Oracle instance permits the collection of data
to troubleshoot problems, as well as providing value forensic logs in the case of a system
breach, this value should be set according to the needs of the organization.
Audit:
46 | P a g e
SQL> select value
from v$parameter
where upper(name)='AUDIT_TRAIL';
Remediation:
SQL> alter system set audit_trail = DB,EXTENDED scope = spfile;
or
SQL> alter system set audit_trail = OS scope = spfile;
or
SQL> alter system set audit_trail = XML,EXTENDED scope = spfile;
References:
EFRN10006
2. http://www.oracle.com/technetwork/database/audit-vault/learnmore/twp-
security-auditperformance-166655.pdf
2.5 Setting for the 'global_names' parameter (Scored)

Description:
The global_names setting requires that the name of a database link matches that of the
remote database it will connect to.
Rationale:
As not requiring database connections to match the domain that is being called remotely
could allow unauthorized domain sources to potentially connect via brute-force tactics, this
value should be set according to the needs of the organization.
Audit:
SQL> select value from v$parameter where upper(name)='GLOBAL_NAMES';
Remediation:
47 | P a g e
SQL> alter system set global_names = true scope = spfile;
References:
EFRN10065
2.6 Setting for the 'local_listener' parameter (Scored)

Description:
The local_listener setting specifies a network name that resolves to an address of the
Oracle TNS listener.
Rationale:
The TNS poisoning attack allows to redirect TNS network traffic to another system by
registering a listener to the TNS listener. This attack can be performed by unauthorized
users with network access. By specifying the IPC protocol it is no longer possible to register
listeners via TCP/IP.
Audit:
SQL> select value from v$parameter a where upper(name) = 'LOCAL_LISTENER';
Remediation:
SQL> alter system set local_listener='(DESCRIPTION=(ADDRESS=

(PROTOCOL=IPC)(KEY=REGISTER)))' scope = both;
References:
EFRN10082
3.1
1.1
4. http://www.joxeankoret.com/download/tnspoison.pdf
48 | P a g e
2.7 Setting for the 'o7_dictionary_accessibility' parameter (Scored)
Description:
The O7_dictionary_accessibility setting is a database initializations parameter that

allows/disallows with the EXECUTE ANY PROCEDURE and SELECT ANY DICTIONARY
access to objects in the SYS schema; this functionality was created for the ease of migration
from Oracle 7 databases to later versions.
Rationale:
As leaving the SYS schema so open to connection could permit unauthorized access to
critical data structures, this value should be set according to the needs of the organization.
Audit:
SQL> select value from v$parameter where upper(name)='O7_DICTIONARY_ACCESSIBILITY';
Remediation:
SQL> ALTER SYSTEM SET O7_DICTIONARY_ACCESSIBILITY=FALSE scope=spfile;
References:
EFRN10133
2.8 Setting for the 'os_roles' parameter (Scored)

Description:
The os_roles setting permits externally created groups to be applied to database

management.
Rationale:
49 | P a g e
As allowing the OS use external groups for database management could cause privilege
overlaps and generally weaken security, this value should be set according to the needs of
the organization.
Audit:
SQL> select value from v$parameter where upper(name)='OS_ROLES';
Remediation:
SQL> ALTER SYSTEM SET OS_ROLES=false SCOPE=SPFILE;
References:
EFRN10153
2.9 Setting for the 'remote_listener' parameter (Scored)

Description:
The remote_listener setting determines whether or not a valid listener can be established
on a system separate from the database instance.
Rationale:
As permitting a remote listener for connections to the database instance can allow for the
potential spoofing of connections and that could compromise data confidentiality and
integrity, this value should be disabled/restricted according to the needs of the
organization.
Audit:
SQL> select value from v$parameter a where upper(name) = 'REMOTE_LISTENER';
Remediation:
SQL> alter system set remote_listener ='' scope = spfile;
References:
50 | P a g e
EFRN10183
2.10 Setting for the 'remote_login_passwordfile' parameter (Scored)

Level 1 - 11.2 on any platform
Description:
The remote_login_passwordfile setting specifies whether or not Oracle checks for a

password file during login and how many databases can use the password file.
Rationale:
As the use of this sort of password login file could permit unsecured, privileged
connections to the database, this value should be set according to the needs of the
organization.
Audit:
SQL> select value from v$parameter where upper(name)='REMOTE_LOGIN_PASSWORDFILE';
Remediation:
SQL> ALTER SYSTEM SET remote_login_passwordfile = none scope = spfile;
References:
EFRN10184
2.11 Setting for the 'remote_os_authent' parameter (Scored)

Description:
The remote_os_authent setting determines whether or not OS 'roles' with the attendant
privileges are allowed for remote client connections.
Rationale:
51 | P a g e
As permitting OS roles for database connections to can allow the spoofing of connections
and permit granting the privileges of an OS role to unauthorized users to make
connections, this value should be restricted according to the needs of the organization.
Audit:
SQL> select value from v$parameter where upper(name)='REMOTE_OS_AUTHENT';
Remediation:
SQL> alter system set remote_os_authent = false scope = spfile;
References:
EFRN10185
2.12 Setting for the 'remote_os_roles' parameter (Scored)

Description:
The remote_os_roles setting permits remote users' OS roles to be applied to database

management.
Rationale:
As allowing remote clients OS roles to have permissions for database management could
cause privilege overlaps and generally weaken security, this value should be set according
Audit:
SQL> select value from v$parameter a where upper(name) = 'REMOTE_OS_ROLES';
Remediation:
SQL> ALTER SYSTEM SET REMOTE_OS_ROLES=false SCOPE=SPFILE;
References:
EFRN10186
52 | P a g e
2.13 Setting for the 'utl_file_dir' parameter (Scored)
Description:
The utl_file_dir setting allows packages like utl_file to access

(read/write/modify/delete) files specified in utl_file_dir. (This is deprecated but usable in
11g.)
Rationale:
As using the utl_file_dir to create directories allows the manipulation of files in

these directories.
Audit:
SQL> select value from v$parameter where upper(name)='UTL_FILE_DIR';
Remediation:
SQL> ALTER SYSTEM SET UTIL_FILE_DIR = '' SCOPE=SPFILE;
References:
EFRN10230
2.14 Setting for the 'sec_case_sensitive_logon' parameter (Scored)

Description:
The SEC_CASE_SENSITIVE_LOGON information determines whether or not case-sensitivity is

required for passwords during login.
Due to the security bug CVE-2012-3137 it is recommended to set this parameter to TRUE if
the October 2012 CPU/PSU or later was applied.
If the patch was not applied it is recommended to set this parameter to FALSE to avoid that
the vulnerability could be abused.
53 | P a g e
Rationale:
Oracle 11g databases without CPU October 2012 patch or later are vulnerable to CVE-
2012-3137 if case-sensisitve SHA-1 password hashes are used. To avoid this kind of attack
the old DES-hashes have to be used.
Audit:
SQL> select value from v$parameter where upper(name)='SEC_CASE_SENSITIVE_LOGON';
Remediation:
SQL> ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON=TRUE scope=spfile;
Impact:
If SEC_CASE_SENSITIVE_LOGON is FALSE, all user with SHA-1 hashes only ("select

name,password,spare4 from sys.user$ where password is null and spare4 is not null") are
no longer able to connect to the database. In this case the password for all users withou t
DES hash have to set again.
References:
EFRN10299
2. https://support.oracle.com/epmos/faces/DocumentDisplay?id=1492721.1
3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-3137
2.15 Setting for the 'sec_max_failed_login_attempts' parameter

(Scored)
Description:
The SEC_MAX_FAILED_LOGIN_ATTEMPTS parameter determines how many failed login

attempts are allowed before Oracle closes the login connection.
Rationale:
54 | P a g e
As allowing an unlimited number of login attempts for a user connection can facilitate both
brute-force login attacks and the occurrence of Denial-of-Service , this value (10) should be
set according to the needs of the organization.
Audit:
SQL> select value from v$parameter where upper(name)='SEC_MAX_FAILED_LOGIN_ATTEMPTS';
Remediation:
SQL> ALTER SYSTEM SET SEC_MAX_FAILED_LOGIN_ATTEMPTS = 10 scope=spfile;
References:
EFRN10274
2.16 Setting for the 'sec_protocol_error_further_action' parameter

(Scored)
Description:
The SEC_PROTOCOL_ERROR_FURTHER_ACTION setting determines the Oracle's server's

response to bad/malformed packets received from the client.
Rationale:
As bad packets received from the client can potentially indicate packet-based attacks on the
system, such as "TCP SYN Flood" or "Smurf" attacks, which could result in a Denial-of-
Service condition, this value should be set according to the needs of the organization.
Audit:
SQL> select value from v$parameter where

upper(name)='SEC_PROTOCOL_ERROR_FURTHER_ACTION';
Remediation:
SQL> ALTER SYSTEM SET SEC_PROTOCOL_ERROR_FURTHER_ACTION = delay,3 scope=spfile ;
OR
SQL> ALTER SYSTEM SET SEC_PROTOCOL_ERROR_FURTHER_ACTION = drop,3 scope=spfile ;
55 | P a g e
References:
EFRN10282
2.17 Setting for the 'sec_protocol_error_trace_action' parameter

(Scored)
Description:
The SEC_PROTOCOL_ERROR_TRACE_ACTION setting determines the Oracle's server's logging

response level to bad/malformed packets received from the client, by generating ALERT,
LOG, or TRACE levels of detail in the log files.
Rationale:
As bad packets received from the client can potentially indicate packet-based attacks on the
system, such as "TCP SYN Flood" or "Smurf" attacks, which could result in a Denial-of-
Service condition, this diagnostic/logging value for ALERT, LOG, or TRACE conditions should
be set according to the needs of the organization.
Audit:

upper(name)='SEC_PROTOCOL_ERROR_TRACE_ACTION';
Remediation:
SQL> ALTER SYSTEM SET SEC_PROTOCOL_ERROR_TRACE_ACTION=LOG scope=spfile;
References:
EFRN10283
2.18 Setting for the 'sec_return_server_release_banner' parameter

(Scored)
56 | P a g e
Description:
The information about patch/update release number provides information about the exact
patch/update release that is currently running on the database.
Rationale:
As allowing the database to return information about the patch/update release

number could facilitate unauthorized users' attempts to gain access based upon known
patch weaknesses , this value should be set according to the needs of the organization.
Audit:

upper(name)='SEC_RETURN_SERVER_RELEASE_BANNER';
Remediation:
SQL> ALTER SYSTEM SET sec_return_server_release_banner=false scope=spfile;
References:
EFRN10275
2.19 Setting for the 'sql92_security' parameter (Scored)

Description:
The sql92_security parameter setting FALSE allows to grant

only UPDATE or DELETE privileges without the need to grant SELECT privileges.
Rationale:
The default value FALSE of the parameter sql92_security is secure out-of-the-box. Several
security guides recommend the unsecure setting TRUE. This unsecure setting TRUE allows
users which need only UPDATE/DELETE privileges to select data directly instead of
guessing it.
Audit:
57 | P a g e
SQL> select value from v$parameter where upper(name)='SQL92_SECURITY';
Remediation:
SQL> ALTER SYSTEM SET sql92_security=FALSE SCOPE=SPFILE;
References:
EFRN10210
2.20 Setting for undocumented '_trace_files_public' parameter (Scored)

Description:
The _trace_files_public setting determines whether or not the system's trace file is
world readable.
Rationale:
As permitting the unix read permission to other anyone can read the instance's trace files
file which could contain sensitive information about instance operations, this value should
be restricted according to the needs of the organization.
Audit:
SQL> select value

from v$parameter where lower(name)='_trace_files_public';
Remediation:
SQL> alter system set "_trace_files_public"=false scope=spfile;
References:
1. http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4295521
746131
3 Oracle client/user connection and login restrictions

The restrictions on Client/User connections to the Oracle database help block unauthorized
access to data and services by setting access rules; these security measures help to ensure
58 | P a g e
that successful logins cannot be easily made through brute-force password attacks or
intuited by clever social engineering exploits. By the use of the base profile, e.g.
"DEFAULT," then assigning this profile to a client, the database administrator can set a
standard policy for password security/resource use to all users assigned the 'DEFAULT'
profile; however, this policy can still be overridden by local policy. All values assigned
below are the recommended minimums or maximums; higher, more restrictive values can
be applied at the discretion of the organization by creating a separate profile to assign to a
different user group.
3.1 Restrictions on failed login attempts via the default DB profile

(Scored)
Description:
The failed_login_attempts setting determines how many failed login attempts are
permitted before the system locks the user's account. While different profiles can have
different and more restrictive settings, such as USERS and APPS, the minimum(s)
recommended here should be set on the DEFAULT profile.
Rationale:
As repeated failed login attempts can indicate the initiation of a brute-force login attack,
this value should be set according to the needs of the organization (see warning below on
a known bug that can make this security measure backfire).
Audit:
SQL> SELECT PROFILE, RESOURCE_NAME, LIMIT FROM DBA_PROFILES WHERE PROFILE='DEFAULT'

AND RESOURCE_NAME='FAILED_LOGIN_ATTEMPTS';
Remediation:
SQL> ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS 5;
3.2 Requirements for account locking via on the default DB profile

(Scored)
59 | P a g e
Description:
The PASSWORD_LOCK_TIME setting determines how many days must pass for the user's
account to be unlocked after the set number of failed login attempts has occurred.
Rationale:
As locking the user account after repeated failed login attempts can block further brute -
force login attacks, but can create administrative headaches as this account unlocking
process always requires DBA intervention, this value should be set according to the
needs of the organization.
Audit:

AND RESOURCE_NAME='PASSWORD_LOCK_TIME';
Remediation:
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LOCK_TIME 1;
3.3 Restrictions on password duration via the default DB profile (Scored)

Description:
The password_life_time setting determines how long a password may be used before the
user is required to be change it.
Rationale:
As allowing passwords to remain unchanged for long periods makes the success of brute -
force login attacks more likely, this value should be set according to the needs of the
organization.
Audit:

AND RESOURCE_NAME='PASSWORD_LIFE_TIME';
Remediation:
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME 90;
60 | P a g e
3.4 Restrictions on password history via the default DB profile (Scored)
Description:
The password_reuse_max setting determines how many different passwords must be used
before the user is allowed to reuse a prior password.
Rationale:
As allowing reuse of a password within a short period of time after the password's initial
use can make the success of both social-engineering and brute-force password-based
attacks more likely, this value should be set according to the needs of the organization.
Audit:

AND RESOURCE_NAME='PASSWORD_REUSE_MAX';
Remediation:
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_REUSE_MAX 20;
3.5 Restrictions on password use (reuse) via a DB profile (Scored)

Description:
The password_reuse_time setting determines the amount of time in days that must pass
before the same password may be reused.
Rationale:
As reusing the same password after only a short period of time has passed makes the
success of brute-force login attacks more likely, this value should be set according to the
Audit:
61 | P a g e
SQL> SELECT PROFILE, RESOURCE_NAME, LIMIT FROM DBA_PROFILES WHERE PROFILE='DEFAULT'AND
RESOURCE_NAME='PASSWORD_REUSE_TIME';
Remediation:
SQL> ALTER PROFILE DEFAULT PASSWORD_REUSE_TIME 365;
3.6 Requirements for account locking (grace time) via a DB profile

(Scored)
Description:
The password_grace_time setting determines how many days can pass after the user's
password expires before the user's login capability is automatically locked out.
Rationale:
As locking the user account after the expiration of the password change requirement's
grace period can help prevent password-based attack against a forgotten or disused
accounts, while still allowing the account and its information to be accessible by DBA
intervention, this value should be set according to the needs of the organization.
Audit:
SQL> SELECT PROFILE, RESOURCE_NAME, LIMIT FROM DBA_PROFILES WHERE PROFILE='DEFAULT'AND

RESOURCE_NAME='PASSWORD_GRACE_TIME';
Remediation:
SQL> ALTER PROFILE DEFAULT PASSWORD_GRACE_TIME 5;
3.7 Requirements for limiting EXTERNAL user login capability (Scored)

Description:
The password='EXTERNAL' setting determines whether or not a user can be authenticated

by a remote OS to allow access to the database with full authorization.
62 | P a g e
Rationale:
As allowing remote OS authentication of a user to the database can potentially allow

supposed "privileged users" to connect as "authenticated," even when the remote system is
compromised, these logins should be disabled/restricted according to the needs of the
organization.
Audit:
SQL> SELECT USERNAME FROM DBA_USERS WHERE AUTHENTICATION_TYPE='EXTERNAL';
Remediation:
SQL> ALTER USER username IDENTIFIED BY password;
3.8 Requirement for setting the password verification function (Not

Scored)
Description:
The password_verify_function determines password settings requirements when a user

password is changed at the SQL command prompt. This setting does not apply for users
managed by the Oracle password file.
Rationale:
As requiring users to apply the 11gr2 security features in password creation, such as
forcing mixed-case complexity, the blocking of simple combinations, and change/history
settings can potentially thwart logins by unauthorized users, this function should be
applied/enabled according to the needs of the organization.
Audit:
SQL> SELECT PROFILE, RESOURCE_NAME FROM DBA_PROFILES WHERE

RESOURCE_NAME='PASSWORD_VERIFY_FUNCTION';
Remediation:
Create a custom password verification function which fulfills the password requirements of
the organization.
63 | P a g e
3.9 Requirements for limiting the number of sessions per user (Scored)
Description:
The SESSIONS_PER_USER (Number of sessions allowed) determines the maximum number

of user sessions that are allowed to be open concurrently.
Rationale:
As limiting the number of the SESSIONS_PER_USER can help prevent memory resource
exhaustion by poorly formed requests or intentional Denial-of-Service attacks, this value
should be set according to the needs of the organization.
To enable this setting it is necessary to enable the RESOURCE_LIMIT ( ALTER SYSTEM SET
RESOURCE_LIMIT = TRUE; ).
Audit:
SQL> SELECT PROFILE, RESOURCE_NAME, LIMIT FROM DBA_PROFILES WHERE

RESOURCE_NAME='SESSIONS_PER_USER' AND PROFILE='DEFAULT';
Remediation:
SQL> ALTER PROFILE DEFAULT LIMIT SESSIONS_PER_USER 10;
4 Oracle user access and authorization restrictions

The capability to use database resources at a given level, or user authorization rules, allows
for user manipulation of the various parts of the Oracle database; these authorizations
must be structured to block unauthorized use and/or corruption of vital data and services,
by setting restrictions on user capabilities, particularly those of the user PUBLIC; these
security measures help to ensure that successful logins cannot be easily redirected.
4.1 Default Public Privileges for Packages and Object Types

Revoke default public execute privileges from powerful packages and object types
64 | P a g e
4.1.1 Limit public access to the DBMS_ADVISOR package (Scored)
Description:
The Oracle database DBMS_ADVISOR package can be used to write files located on the
server where the Oracle instance is installed.
Rationale:
As use of the DBMS_ADVISOR package could allow an unauthorized user to corrupt operating
system files on the instance's host, use of this package should be restricted according to the
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_ADVISOR' AND

GRANTEE ='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_ADVISOR FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_advis.htm
4.1.2 Limit public access to the DBMS_CRYPTO package (Scored)

Description:
The DBMS_CRYPTO settings provide a toolset that determines the strength of the encryption
algorithm used to encrypt application data and is part of the SYS schema. The DES (56-bit
key), 3DES (168-bit key), 3DES-2KEY (112-bit key), AES (128/192/256-bit keys), and RC4
are available.
Rationale:
65 | P a g e
As execution of these cryptography procedures by the user PUBLIC can potentially
endanger portions of or all of the data storage, this value should be set according to the
Audit:
SQL> SELECT GRANTEE, PRIVILEGE, TABLE_NAME FROM DBA_TAB_PRIVS WHERE

TABLE_NAME='DBMS_CRYPTO';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_CRYPTO FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_crypto.htm#ARPLS
664
4.1.3 Limit public access to the DBMS_JAVA package (Scored)

Description:
The Oracle database DBMS_JAVA package can run Java classes (e.g. OS commands) or grant
Java privileges.
Rationale:
The DBMS_JAVA package could allow an attacker to run operating system commands from
the database.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_JAVA' AND

GRANTEE = 'PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_JAVA FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/java.112/e10588/appendixa.htm#JJDEV13
000
66 | P a g e
4.1.4 Limit public access to the DBMS_JAVA_TEST package (Scored)
Description:
The Oracle database DBMS_JAVA_TEST package can run Java classes (e.g. OS commands) or
grant Java privileges.
Rationale:
The DBMS_JAVA_TEST package could allow an attacker to run operating system commands
from the database..
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_JAVA_TEST'

AND GRANTEE ='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_JAVA_TEST FROM PUBLIC;
References:
1. http://www.databasesecurity.com/HackingAurora.pdf
4.1.5 Limit public access to the DBMS_JOB package (Scored)

Description:
The Oracle database DBMS_JOB package schedules and manages the jobs sent to the job
queue and has been superseded by the DBMS_SCHEDULER package, even though DBMS_JOB
has been retained for backwards compatibility.
Rationale:
As use of the DBMS_JOB package could allow an unauthorized user to disable or overload the
job queue and has been superseded by the DBMS_SCHEDULER package, this package should
be disabled or restricted according to the needs of the organization.
67 | P a g e
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS WHERE TABLE_NAME='DBMS_JOB' AND

GRANTEE='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_JOB FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_job.htm
4.1.6 Limit public access to the DBMS_LDAP package (Scored)

Description:
The Oracle database DBMS_LDAP package contains functions and procedures that enable
programmers to access data from LDAP servers.
Rationale:
As use of the DBMS_LDAP package can be used to create specially crafted error messages or
send information via DNS to the outside.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_LDAP' AND

GRANTEE ='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_LDAP FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E23943_01/oid.1111/e10186/dbmsldap_ref.htm#OIMA
D009
4.1.7 Limit public access to the DBMS_LOB package (Scored)

68 | P a g e
Description:
The Oracle database DBMS_LOB package provides subprograms that can manipulate and
read/write on BLOBs, CLOBs, NCLOBs, BFILEs, and temporary LOBs.
Rationale:
As use of the DBMS_LOB package could allow an unauthorized user to manipulate BLOBs,
CLOBs, NCLOBs, BFILEs, and temporary LOBs on the instance, either destroying data or
causing a Denial-of-Service condition due to corruption of disk space, use of this package
should be restricted according to the needs of the organization.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_LOB' AND

GRANTEE = 'PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_LOB FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_lob.htm
4.1.8 Limit public access to the DBMS_OBFUSCATION_TOOLKIT package

(Scored)
Description:
The DBMS_OBFUSCATION_TOOLKIT settings provide one of the tools that determine the
strength of the encryption algorithm used to encrypt application data and is part of the SYS
schema. The DES (56-bit key) and 3DES (168-bit key) are the only two types available.
Rationale:
As allowing the PUBLIC user privileges to access this capability can be potentially harm the
data storage, this access should be set according to the needs of the organization.
Audit:
69 | P a g e
SQL> SELECT GRANTEE, PRIVILEGE, TABLE_NAME FROM DBA_TAB_PRIVS WHERE
TABLE_NAME='DBMS_OBFUSCATION_TOOLKIT';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_OBFUSCATION_TOOLKIT FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_obtool.htm#ARPLS0
28
4.1.9 Limit public access to the DBMS_RANDOM package (Scored)

Description:
The Oracle database DBMS_RANDOM package is used for generating random numbers but
should not be used for cryptographic purposes.
Rationale:
As assignment of use of the DBMS_RANDOM package can allow the unauthorized application
of the random number-generating function, this capability should be restricted according
Audit:
SQL> SELECT GRANTEE FROM DBA_TAB_PRIVS WHERE TABLE_NAME= 'DBMS_RANDOM' AND

GRANTEE='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_BACKUP_RESTORE FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_random.htm
4.1.10 Limit public access to the DBMS_SCHEDULER package (Scored)

70 | P a g e
Description:
The Oracle database DBMS_SCHEDULER package schedules and manages the database and
operating system jobs .
Rationale:
As use of the DBMS_SCHEDULER package could allow an unauthorized user to run database or
operating system jobs.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS WHERE TABLE_NAME='DBMS_SCHEDULER'

AND GRANTEE='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_SCHEDULER FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_sched.htm
4.1.11 Limit public access to the DBMS_SQL package (Scored)

Description:
The Oracle database DBMS_SQL package is used for running dynamic SQL statements.
Rationale:
The DBMS_SQL package could allow privilege escalation if the input validation is not done
properly.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_SQL' and

GRANTEE='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_SQL FROM PUBLIC;
71 | P a g e
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_sql.htm
4.1.12 Limit public access to the DBMS_XMLGEN package (Scored)

Description:
The DBMS_XMLGEN package takes an arbitrary SQL query as input, converts it to XML
format, and returns the result as a CLOB.
Rationale:
The package DBMS_XMLGEN can be used to search the entire database for critical
information like creditcard numbers, ...
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_XMLGEN' AND

GRANTEE='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_XMLGEN FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_xmlgen.htm
2. http://www.red-database-security.com/wp/confidence2009.pdf
4.1.13 Limit public access to the DBMS_XMLQUERY package (Scored)

Description:
The Oracle package DBMS_XMLQUERY takes an arbitrary SQL query, converts it to XML
format, and returns the result. This package is similar to DBMS_XMLGEN.
Rationale:
72 | P a g e
The package DBMS_XMLQUERY can be used to search the entire database for critical
information like creditcard numbers, ...
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_XMLQUERY'

AND GRANTEE='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_XMLQUERY FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_xmlque.htm
4.1.14 Limit public access to the UTL_FILE package (Scored)

Description:
The Oracle database UTL_FILE package can be used to read/write files located on the
Rationale:
As use of the UTL_FILE package could allow an user to read files at the operating system.
These files could contain sensitive information (e.g. passwords in .bash_history).
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='UTL_FILE' AND

GRANTEE = ('PUBLIC');
Remediation:
SQL> REVOKE EXECUTE ON UTL_FILE FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/u_file.htm#ARPLS708
96
73 | P a g e
4.1.15 Limit public access to the UTL_INADDR package (Scored)
Description:
The Oracle database UTL_INADDR package can be used to create specially crafted error
messages or send information via DNS to the outside.
Rationale:
As use of the UTL_INADDR package is often used in SQL Injection attacks from the web it
should be revoked from public.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='UTL_INADDR' AND

GRANTEE ='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON UTL_INADDR FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/u_inaddr.htm
4.1.16 Limit public access to the UTL_TCP package (Scored)

Description:
The Oracle database UTL_TCP package can be used to read/write file to TCP sockets on the
Rationale:
As use of the UTL_TCP package could allow an unauthorized user to corrupt the TCP stream
used for carry the protocols that communicate with the instance's external
communications, use of this package should be restricted according to the needs of the
organization.
74 | P a g e
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS WHERE TABLE_NAME='UTL_TCP' AND

GRANTEE = 'PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON UTL_TCP FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/u_tcp.htm#ARPLS715
33
4.1.17 Limit public access to the UTL_MAIL package (Scored)

Description:
The Oracle database UTL_MAIL package can be used to send email from the server where
the Oracle instance is installed.
Rationale:
As use of the UTL_MAIL package could allow an unauthorized user to corrupt the SMTP
function to accept or generate junk mail that can result in a Denial-of-Service condition due
to network saturation, use of this package should be restricted according to the needs of
the organization.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='UTL_MAIL' and

GRANTEE ='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON UTL_MAIL FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/u_mail.htm
75 | P a g e
4.1.18 Limit public access to the UTL_SMTP package (Scored)
Description:
The Oracle database UTL_SMTP package can be used to send email from the server where
the Oracle instance is installed.
Rationale:
As use of the UTL_SMTP package could allow an unauthorized user to corrupt the SMTP
function to accept or generate junk mail that can result in a Denial-of-Service condition due
to network saturation, use of this package should be restricted according to the needs of
the organization.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='UTL_SMTP' and

GRANTEE = 'PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON UTL_SMTP FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/u_smtp.htm
4.1.19 Limit public access to the UTL_DBWS package (Scored)

Description:
The Oracle database UTL_DBWS package can be used to read/write file to web-based
applications on the server where the Oracle instance is installed.
Rationale:
As use of the UTL_DBWS package could allow an unauthorized user to corrupt the HTTP
stream used for carry the protocols that communicate with the instance's web -based
76 | P a g e
external communications, use of this package should be restricted according to the needs of
the organization.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='UTL_DBWS' AND

GRANTEE ='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON UTL_DBWS FROM 'PUBLIC';
References:
1. http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/u_dbws.htm
4.1.20 Limit public access to the UTL_ORAMTS package (Scored)

Description:
The Oracle database UTL_ORAMTS package can be used to perform HTTP-requests. This
could be used to send information to the outside.
Rationale:
As use of the UTL_ORAMTS package could be used to send (sensitive) information to external
websites. The use of this package should be restricted according to the needs of the
organization.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='UTL_ORAMTS' AND

GRANTEE ='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON UTL_ORAMTS FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/win.112/e26104/recovery.htm#NTMTS13
9
77 | P a g e
4.1.21 Limit public access to the UTL_HTTP package (Scored)
Description:
The Oracle database UTL_HTTP package can be used to perform HTTP-requests. This could
be used to send information to the outside.
Rationale:
As use of the UTL_HTTP package could be used to send (sensitive) information to external
websites. The use of this package should be restricted according to the needs of the
organization.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='UTL_HTTP' AND

GRANTEE = 'PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON UTL_HTTP FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/u_http.htm
4.1.22 Limit public access to the HTTPURITYPE object type (Scored)

Description:
The Oracle database HTTPURITYPE object type can be used to perform HTTP-requests. This
could be used to send information to the outside.
Rationale:
tbd.
Audit:
78 | P a g e
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='HTTPURITYPE' AND
GRANTEE ='PUBLIC' ;
Remediation:
SQL> REVOKE EXECUTE ON HTTPURITYPE FROM PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/t_dburi.htm#ARPLS71
705
4.2 Non-Default Public Privileges for Packages and Object

Types
Non-Default Public Privileges for Packages and Object Types
4.2.1 Limiting public user access to the DBMS_SYS_SQL package

(Scored)
Description:
The Oracle database DBMS_SYS_SQL package is shipped as undocumented.
Rationale:
As use of the DBMS_SYS_SQL package could allow an user to run code as a different user
without entering user credentials.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_SYS_SQL' and

grantee='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_SYS_SQL FROM PUBLIC;
References:
79 | P a g e
1. http://docs.oracle.com/cd/E11882_01/network.112/e16543/guidelines.htm#DBS
EG499
2. http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1325202
421535
4.2.2 Limit public access to the DBMS_BACKUP_RESTORE package

(Scored)
Description:
The Oracle database DBMS_BACKUP_RESTORE package is used for applying PL/SQL

commands to the native RMAN sequences.
Rationale:
As assignment of use of the DBMS_BACKUP_RESTORE package can allow to access file

permissions on operating system level.
Audit:
SQL> SELECT GRANTEE FROM DBA_TAB_PRIVS WHERE TABLE_NAME= 'DBMS_BACKUP_RESTORE' and

grantee='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_BACKUP_RESTORE FROM PUBLIC;
References:
1. http://psoug.org/reference/dbms_backup_restore.html
2. http://davidalejomarcos.wordpress.com/2011/09/13/how-to-list-files-on-a-
directory-from-oracle-database/
4.2.3 Limiting public user access to the DBMS_AQADM_SYSCALLS

package (Scored)
Description:
80 | P a g e
The Oracle database DBMS_AQADM_SYSCALLS package is shipped as undocumented and
allows to run SQL commands as user SYS.
Rationale:
As use of the DBMS_AQADM_SYSCALLS package could allow an unauthorized user to run SQL
commands as user SYS.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where

TABLE_NAME='DBMS_AQADM_SYSCALLS' and grantee='PUBLIC';
Remediation:
SQL> REVOKE EXECUTE ON DBMS_AQADM_SYSCALLS FROM PUBLIC;
References:
1. http://www.databasesecurity.com/dbsec/ohh-indirect-privilege-escalation.pdf
4.2.4 Limiting public user access to the DBMS_REPACT_SQL_UTL

package (Scored)
Description:
The Oracle database DBMS_REPACT_SQL_UTL package is shipped as undocumented and

Rationale:
As use of the DBMS_REPACT_SQL_UTL package could allow an unauthorized user to run SQL
Audit:

TABLE_NAME='DBMS_REPACT_SQL_UTL' and grantee='PUBLIC';
Remediation:
SQL> revoke execute on DBMS_REPACT_SQL_UTL from PUBLIC;
81 | P a g e
References:
4.2.5 Limiting public user access to the INITJVMAUX package (Scored)

Description:
The Oracle database INITJVMAUX package is shipped as undocumented and allows to run
SQL commands as user SYS.
Rationale:
As use of the INITJVMAUX package could allow an unauthorized user to run SQL commands
as user SYS.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='INITJVMAUX' and

grantee='PUBLIC';
Remediation:
SQL> Revoke execute on INITJVMAUX from PUBLIC;
References:
4.2.6 Limiting public user access to the DBMS_STREAMS_ADM_UTL

package (Scored)
Description:
The Oracle database DBMS_STREAMS_ADM_UTL package is shipped as undocumented and

Rationale:
82 | P a g e
As use of the DBMS_STREAMS_ADM_UTL package could allow an unauthorized user to run SQL
Audit:

TABLE_NAME='DBMS_STREAMS_ADM_UTL' and grantee='PUBLIC';
Remediation:
SQL> Revoke execute on DBMS_STREAMS_ADM_UTL from PUBLIC;
References:
4.2.7 Limiting public user access to the DBMS_AQADM_SYS package

(Scored)
Description:
The Oracle database DBMS_AQADM_SYS package is shipped as undocumented and allows to

run SQL commands as user SYS.
Rationale:
As use of the DBMS_AQADM_SYS package could allow an unauthorized user to run SQL
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_AQADM_SYS'

and grantee='PUBLIC';
Remediation:
SQL> Revoke execute on DBMS_AQADM_SYS from PUBLIC;
References:
1. http://www.google.de/#hl=de&safe=off&sclient=psy-
ab&q=DBMS_STREAMS_ADM_UTL&oq=DBMS_STREAMS_ADM_UTL&gs_l=serp.3..0i1
83 | P a g e
0i30.38260.38260.0.38463.1.1.0.0.0.0.105.105.0j1.1.0...0.0...1c.2.1-
46wqcQeow&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=2569366ac9a6532d&bpc
4.2.8 Limiting public user access to the DBMS_STREAMS_RPC package

(Scored)
Description:
The Oracle database DBMS_STREAMS_RPC package is shipped as undocumented and allows to

Rationale:
As use of the DBMS_STREAMS_RPC package could allow an unauthorized user to run SQL
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_STREAMS_RPC'

Remediation:
SQL> Revoke execute on DBMS_STREAMS_RPC from PUBLIC;
References:
4.2.9 Limiting public user access to the DBMS_AQADM_SYS package

(Scored)
Description:
The Oracle database DBMS_AQADM_SYS package is shipped as undocumented and allows to

Rationale:
84 | P a g e
As use of the DBMS_AQADM_SYS package could allow any user to run SQL commands as user
SYS.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_AQADM_SYS'

Remediation:
SQL> Revoke execute on DBMS_AQADM_SYS from PUBLIC;
4.2.10 Limiting public user access to the DBMS_PRVTAQIM package

(Scored)
Description:
The Oracle database DBMS_PRVTAQIM package is shipped as undocumented and allows to

Rationale:
As use of the DBMS_PRVTAQIM package could allow an unauthorized user to escalate

privileges because any SQL statements could be executed as user SYS.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_PRVTAQIM'

Remediation:
SQL> Revoke execute on DBMS_PRVTAQIM from PUBLIC;
References:
4.2.11 Limiting public user access to the LTADM package (Scored)

85 | P a g e
Description:
The Oracle database LTADM package is shipped as undocumented and allows privilege
escalation if granted to unprivileged users.
Rationale:
As use of the LTADM package could allow an unauthorized user to run any SQL command as
user SYS.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='LTADM' and

grantee='PUBLIC';
Remediation:
SQL> Revoke execute on LTADM from PUBLIC;
References:
4.2.12 Limiting public user access to the WWV_DBMS_SQL package

(Scored)
Description:
The Oracle database WWV_DBMS_SQL package is shipped as undocumented and allows Oracle
Application Express to run dynamic SQL statements.
Rationale:
As use of the WWV_DBMS_SQL package could allow an unauthorized user to run SQL
statements as Application Express (APEX) user.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='WWV_DBMS_SQL' and

grantee='PUBLIC';
86 | P a g e
Remediation:
SQL> Revoke execute on WWV_DBMS_SQL from PUBLIC;
References:
1. http://docs.oracle.com/cd/E11882_01/install.112/e12196/trouble.htm#HTMIG26
7
4.2.13 Limiting public user access to the WWV_EXECUTE_IMMEDIATE

package (Scored)
Description:
The Oracle database WWV_EXECUTE_IMMEDIATE package is shipped as undocumented and

allows Oracle Application Express to run dynamic SQL statements.
Rationale:
As use of the WWV_EXECUTE_IMMEDIATE package could allow an unauthorized user to run

SQL statements as Application Express (APEX) user.
Audit:

TABLE_NAME='WWV_EXECUTE_IMMEDIATE' and grantee='PUBLIC';
Remediation:
SQL> Revoke execute on WWV_EXECUTE_IMMEDIATE from PUBLIC;
References:
1. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-1811
2. https://forums.oracle.com/forums/thread.jspa?threadID=953790
4.2.14 Limiting public user access to the DBMS_IJOB package (Scored)

87 | P a g e
Description:
The Oracle database DBMS_IJOB package is shipped as undocumented and allows to run
database jobs in the context of another user.
Rationale:
As use of the DBMS_IJOB package could allow an attacker to change identities by using a
different username to execute a database job.
Audit:
SQL> SELECT GRANTEE, TABLE_NAME FROM DBA_TAB_PRIVS where TABLE_NAME='DBMS_IJOB' and

grantee='PUBLIC';
Remediation:
SQL> Revoke execute on DBMS_IJOB from PUBLIC;
4.2.15 Limiting public user access to the DBMS_FILE_TRANSFER package

(Scored)
Description:
The Oracle database DBMS_FILE_TRANSFER package allows to transfer files from one
database server to another.
Rationale:
As use of the DBMS_FILE_TRANSFER package could allow to transfer files from one
database server to another.
Audit:

TABLE_NAME='DBMS_FILE_TRANSFER' and GRANTEE='PUBLIC';
Remediation:
SQL> Revoke execute on DBMS_FILE_TRANSFER from PUBLIC;
References:
88 | P a g e
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_ftran.htm#ARPLS09
5
4.3 System Privileges

Revoke system privileges
4.3.1 Limiting users by restricting the SELECT ANY DICTIONARY privilege

(Scored)
Description:
The Oracle database SELECT ANY DICTIONARY privilege allows the designated user to access
SYS schema objects.
Rationale:
The Oracle database SELECT ANY DICTIONARY privilege allows the designated user to access
SYS schema objects. The Oracle password hashes are part of the SYS schema and can be
selected using SELECT ANY DICTIONARY privileges.
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS where PRIVILEGE='SELECT ANY

DICTIONARY' AND GRANTEE NOT IN
('DBA','DBSNMP','OEM_MONITOR','OLAPSYS','ORACLE_OCM','SYSMAN','WMSYS');
Remediation:
SQL>REVOKE SELECT_ANY_DICTIONARY from <grantee>;
References:
1. http://docs.oracle.com/cd/E11882_01/network.112/e16543/authorization.htm#B
ABHFJFJ
EFRN10133
3. http://arup.blogspot.de/2011/07/difference-between-select-any.html
89 | P a g e
4.3.2 Limiting users by restricting the SELECT ANY TABLE privilege
(Scored)
Description:
The Oracle database SELECT ANY TABLE privilege allows the designated user to open any
table, except of SYS, to view it.
Rationale:
As assignment of the SELECT ANY TABLE privilege can allow the unauthorized viewing of
sensitive data, this capability should be restricted according to the needs of the
organization.
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS where PRIVILEGE='SELECT_ANY_TABLE';
Remediation:
SQL> REVOKE SELECT_ANY_TABLE from <grantee>;
References:
1. http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_10002.htm
#SQLRF01702
4.3.3 Limiting users by restricting the AUDIT SYSTEM privilege (Scored)

Description:
The Oracle database AUDIT SYSTEM privilege allows the change auditing activities on the
system.
Rationale:
90 | P a g e
As assignment of the AUDIT SYSTEM privilege can allow the unauthorized alteration of
system audit activities, disabling the creation of audit trails, this capability should be
restricted according to the needs of the organization.
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS where

PRIVILEGE='AUDIT SYSTEM' AND GRANTEE NOT IN
('DBA','DATAPUMP_IMP_FULL_DATABASE','IMP_FULL_DATABASE','SYS');
Remediation:
SQL> REVOKE AUDIT SYSTEM from <grantee>;
References:
1. http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_4007.htm#
SQLRF01107
4.3.4 Limiting users by restricting the EXEMPT ACCESS POLICY (Scored)

Description:
The Oracle database EXEMPT ACCESS POLICY keyword provides the user the capability to
access all the table rows regardless of row-level security lockouts.
Rationale:
As assignment of the EXEMPT ACCESS POLICY privilege can allow an unauthorized user to
potentially access/change confidential data, this capability should be restricted according
Audit:
SQL> SELECT * FROM DBA_SYS_PRIVS WHERE PRIVILEGE='EXEMPT ACCESS POLICY';
Remediation:
SQL> REVOKE EXEMPT ACCESS POLICY FROM <grantee>;
References:
91 | P a g e
1. http://docs.oracle.com/cd/E11882_01/network.112/e16543/auditing.htm#DBSEG
419
2. http://docs.oracle.com/cd/E11882_01/network.112/e16543/vpd.htm#DBSEG309
4.3.5 Limiting users by restricting the BECOME USER privilege (Scored)

Description:
The Oracle database BECOME USER privilege allows the designated user to inherit the rights
of another user.
Rationale:
As assignment of the BECOME USER privilege can allow the unauthorized use of another
user's privileges, this capability should be restricted according to the needs of the
organization.
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS where PRIVILEGE='BECOME USER' AND
GRANTEE NOT IN ('DBA','SYS','IMP_FULL_DATABASE');
Remediation:
SQL> REVOKE BECOME USER from <grantee>;
References:
1. http://docs.oracle.com/cd/B19306_01/network.102/b14266/cfgaudit.htm
4.3.6 Limiting users by restricting the CREATE PROCEDURE privilege

(Scored)
Description:
The Oracle database CREATE PROCEDURE privilege allows the designated user to create a
stored procedure that will fire when given the correct command sequence.
92 | P a g e
Rationale:
As assignment of the CREATE PROCEDURE privilege can lead to severe problems in

unauthorized hands, such as rogue procedures facilitating data theft or Denial-of-Service by
corrupting data tables, this capability should be restricted according to the needs of the
organization.
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS where PRIVILEGE='CREATE PROCEDURE'

and GRANTEE NOT IN (
'DBA','DBSNMP','MDSYS','OLAPSYS','OWB$CLIENT','OWBSYS','RECOVERY_CATALOG_OWNER','SPATI
AL_CSW_ADMIN_USR','SPATIAL_WFS_ADMIN_USR','SYS','APEX_030200','APEX_040000','APEX_0401
00','APEX_040200');
Remediation:
REVOKE CREATE_PROCEDURE from <grantee>;
References:
SQLRF01309
4.3.7 Limiting users by restricting the ALTER SYSTEM privilege (Scored)

Description:
The Oracle database ALTER SYSTEM privilege allows the designated user to dynamically
alter the instance's running operations.
Rationale:
As assignment of the ALTER SYSTEM privilege can lead to severe problems, such as the
instance's session being killed or the stopping of redo log recording, which would make
transactions unrecoverable, this capability should be severely restricted according to the
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS WHERE PRIVILEGE='ALTER SYSTEM' and
GRANTEE NOT IN
('SYS','SYSTEM','APEX_030200','APEX_040000','APEX_040100','APEX_040200');
93 | P a g e
Remediation:
SQL> REVOKE ALTER SYSTEM from <grantee>;
References:
SQLRF00902
4.3.8 Limiting users by restricting the CREATE ANY LIBRARY privilege

(Not Scored)
Description:
The Oracle database CREATE (ANY) LIBRARY privilege allows the designated user to create
objects that are associated to the shared libraries.
Rationale:
As assignment of the CREATE (ANY) LIBRARY privilege can allow the creation of numerous
library-associated objects and potentially corrupt the libraries' integrity, this capability
Audit:
SQL> SELECT * FROM DBA_SYS_PRIVS where (PRIVILEGE='CREATE LIBRARY'

or PRIVILEGE='CREATE ANY LIBRARY') AND GRANTEE NOT IN ('SYS','SYSTEM','DBA');
Remediation:
SQL> REVOKE CREATE LIBRARY FROM <grantee>;

SQL> REVOKE CREATE ANY LIBRARY FROM <grantee>;
References:
SQLRF01301
2. http://docs.oracle.com/cd/E18283_01/server.112/e17120/manproc007.htm
94 | P a g e
4.3.9 Limiting users by restricting GRANT ANY OBJECT PRIVILEGE
privilege (Scored)
Description:
The Oracle database GRANT ANY OBJECT PRIVILEGE keyword provides the grantee the
capability to grant access to any single or multiple combinations of objects to any grantee
in the catalog of the database.
Rationale:
As authorization to use the GRANT ANY OBJECT PRIVILEGE capability can allow an
unauthorized user to potentially access/change confidential data or damage the data
catalog due to potential complete instance access, this capability should be restricted
according to the needs of the organization.
Audit:
SQL> SELECT * FROM DBA_SYS_PRIVS WHERE PRIVILEGE='GRANT ANY OBJECT PRIVILEGE' AND
GRANTEE NOT IN ('DBA','SYS','IMP_FULL_DATABASE','DATAPUMP_IMP_FULL_DATABASE');
Remediation:
SQL> REVOKE GRANT ANY OBJECT PRIVILEGE FROM <grantee>;
References:
1. http://docs.oracle.com/cd/E11882_01/network.112/e16543/authorization.htm#D
BSEG99914
4.3.10 Limiting users by restricting GRANT ANY ROLE privilege (Scored)

Description:
The Oracle database GRANT ANY ROLE keyword provides the grantee the capability to grant
any single role to any grantee in the catalog of the database.
Rationale:
95 | P a g e
As authorization to use the GRANT ANY ROLE capability can allow an unauthorized user to
potentially access/change confidential data or damage the data catalog due to potential
complete instance access, this capability should be restricted according to the needs of the
organization.
Audit:
SQL> SELECT * FROM DBA_SYS_PRIVS WHERE PRIVILEGE='GRANT ANY ROLE' AND GRANTEE NOT IN
('DBA','SYS','DATAPUMP_IMP_FULL_DATABASE','IMP_FULL_DATABASE','SPATIAL_WFS_ADMIN_USR',
'SPATIAL_CSW_ADMIN_USR');
Remediation:
SQL> REVOKE GRANT ANY ROLE FROM <grantee>;
References:
BSEG99903
4.3.11 Limiting users by restricting GRANT ANY PRIVILEGE privilege

(Scored)
Description:
The Oracle database GRANT ANY PRIVILEGE keyword provides the grantee the capability to
grant any single privilege to any item in the catalog of the database.
Rationale:
As authorization to use the GRANT ANY PRIVILEGE capability can allow an unauthorized
user to potentially access/change confidential data or damage the data catalog due to
potential complete instance access, this capability should be restricted according to the
Audit:
SQL> SELECT * FROM DBA_SYS_PRIVS WHERE PRIVILEGE='GRANT ANY PRIVILEGE' AND GRANTEE NOT
IN ('DBA','SYS','IMP_FULL_DATABASE','DATAPUMP_IMP_FULL_DATABASE');
Remediation:
96 | P a g e
SQL> REVOKE GRANT ANY PRIVILEGE FROM <grantee>;
References:
BSEG99876
4.4 Role Privileges

Revoke powerful roles
4.4.1 Limiting user authorizations for the DELETE_CATALOG_ROLE (Not

Scored)
Description:
The Oracle database DELETE_CATALOG_ROLE provides DELETE privileges for the records in
the system's audit table (AUD$).
Rationale:
As permitting unauthorized access to the DELETE_CATALOG_ROLE can allow the destruction

of audit records vital to the forensic investigation of unauthorized activities, this capability
Audit:
SQL> SELECT * FROM DBA_ROLE_PRIVS where granted_role='DELETE_CATALOG_ROLE' and

grantee not in ('DBA','SYS');
Remediation:
SQL> REVOKE DELETE_CATALOG_ROLE FROM <grantee>;
References:
BSEG99873
BSEG4414
97 | P a g e
4.4.2 Limiting user authorizations for the SELECT_CATALOG_ROLE (Not
Scored)
Description:
The Oracle database SELECT_CATALOG_ROLE provides SELECT privileges on all data

dictionary views held in the SYS schema.
Rationale:
As permitting unauthorized access to the SELECT_CATALOG_ROLE can allow the disclosure of

all dictionary data, this capability should be restricted according to the needs of the
organization.
Audit:
SQL> SELECT * FROM DBA_ROLE_PRIVS where granted_role='SELECT_CATALOG_ROLE' and

grantee not in ('DBA','SYS','IMP_FULL_DATABASE','EXP_FULL_DATABASE','OEM_MONITOR');
Remediation:
SQL> REVOKE SELECT_CATALOG_ROLE FROM <grantee>;
References:
BSEG99873
BSEG4414
4.4.3 Limiting user authorizations for the EXECUTE_CATALOG role (Not

Scored)
Description:
The Oracle database EXECUTE_CATALOG_ROLE provides EXECUTE privileges for a number of

packages and procedures in the data dictionary in the SYS schema.
98 | P a g e
Rationale:
As permitting unauthorized access to the EXECUTE_CATALOG_ROLE can allow the disruption

of operations by initialization of rogue procedures, this capability should be restricted
Audit:
SQL> SELECT * FROM DBA_ROLE_PRIVS where granted_role='EXECUTE_CATALOG_ROLE' and

grantee not in ('DBA','SYS','IMP_FULL_DATABASE','EXP_FULL_DATABASE');
Remediation:
SQL> REVOKE EXECUTE_CATALOG_ROLE FROM <grantee>;
References:
BSEG99873
BSEG4414
4.4.4 Limiting users by restricting the DBA role (Not Scored)

Description:
The Oracle database DBA role is the default database administrator role provided for the
allocation of administrative privileges.
Rationale:
As assignment of the DBA role to an ordinary user can provide a great number of
unnecessary privileges to that user and opens the door to data breaches, integrity
violations, and Denial-of-Service conditions, application of this role should be restricted
Audit:
SQL> SELECT GRANTEE, GRANTED_ROLE FROM DBA_ROLE_PRIVS WHERE GRANTED_ROLE='DBA' AND

GRANTEE NOT IN ('SYS','SYSTEM');
Remediation:
99 | P a g e
SQL> REVOKE DBA from <grantee>;
References:
BSEG4414
4.5 Table and View privileges

Revoke table and view privileges
4.5.1 Limiting authorizations for the SYS.AUD$ table (Scored)

Description:
The Oracle database SYS.AUD$ table contains all the audit records for the database of the
non-Data Manipulation Language (DML) events, such as ALTER, DROP, CREATE, and so
forth. (DML changes need trigger-based audit events to record data alterations.)
Rationale:
As permitting non-privileged users the authorization to manipulate the SYS_AUD$ table can
allow distortion of the audit records, hiding unauthorized activities, this capability should
be restricted according to the needs of the organization.
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_TAB_PRIVS WHERE TABLE_NAME='AUD$' and grantee
not in ('DELETE_CATALOG_ROLE');
Remediation:
SQL> REVOKE ALL ON AUD$ FROM <grantee>;
References:
1. http://docs.oracle.com/cd/E11882_01/network.112/e16543/auditing.htm#CEGDG
IAF
4.5.2 Limiting authorizations for the SYS.USER_HISTORY$ table (Scored)

100 | P a g e
Description:
The Oracle database SYS.USER_HISTORY$ table contains all the audit records for the user's
password change history. (This table gets updated by password changes if the user has an
assigned profile that has password reuse limit set, e.g., PASSWORD_REUSE_TIME set to other
than UNLIMITED.)
Rationale:
As permitting non-privileged users the authorization to manipulate the records in

the SYS.USER_HISTORY$ table can allow distortion of the audit trail, potentially hiding
unauthorized data confidentiality attacks or integrity changes, this capability should be
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_TAB_PRIVS WHERE TABLE_NAME='USER_HISTORY$';
Remediation:
SQL> REVOKE ALL ON USER_HISTORY$ FROM <username>;
References:
1. http://marcel.vandewaters.nl/oracle/database-oracle/password-history-reusing-a-
password
4.5.3 Limiting authorizations for the SYS.LINK$ table (Scored)

Description:
The Oracle database SYS.LINK$ table contains all the user's password information and data
table link information.
Rationale:
As permitting non-privileged users to manipulate or view the SYS.LINK$ table can allow
capture of password information and/or corrupt the primary database linkages, this
capability should be restricted according to the needs of the organization.
101 | P a g e
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_TAB_PRIVS WHERE TABLE_NAME='LINK$';
Remediation:
SQL> REVOKE ALL ON LINK$ FROM <grantee>;
4.5.4 Limiting authorizations for the SYS.USER$ table (Scored)

Description:
The Oracle database SYS.USER$ table contains the users' hashed password information.
Rationale:
As permitting non-privileged users the authorization to open the SYS.USER$ table can allow
the capture of password hashes for the later application of password cracking algorithms
to breach confidentiality, this capability should be restricted according to the needs of the
organization.
Audit:
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_TAB_PRIVS WHERE TABLE_NAME='USER$' and grantee
not in ('CTXSYS','XDB','APEX_030200', 'APEX_040000','APEX_040100','APEX_040200');
Remediation:
SQL> REVOKE ALL ON SYS.USER$ FROM <username>;
References:
1. http://dba.stackexchange.com/questions/17513/what-do-the-columns-in-sys-
user-represent
4.5.5 Limiting user authorizations for the DBA_% views (Scored)

Description:
102 | P a g e
The Oracle database DBA_ views show all information which is relevant to administrative
accounts.
Rationale:
As permitting users the authorization to manipulate the DBA_ views can expose sensitive
data.
Audit:
SQL> SELECT * FROM dba_tab_privs WHERE TABLE_NAME LIKE 'DBA_%' and grantee not in
('APEX_030200','APPQOSSYS','AQ_ADMINISTRATOR_ROLE','CTXSYS','EXFSYS','MDSYS','OLAP_XS_
ADMIN','OLAPSYS','ORDSYS','OWB$CLIENT','OWBSYS','SELECT_CATALOG_ROLE','WM_ADMIN_ROLE',
'WMSYS','XDBADMIN') and table_name not in
('DBA_SDO_MAPS','DBA_SDO_STYLES','DBA_SDO_THEMES','LBACSYS','ADM_PARALLEL_EXECUTE_TASK
');
Remediation:
Replace <non-DBA/SYS grantee>, in the query below, with the Oracle login(s) or role(s)
returned from the associated audit procedure and execute:
SQL> REVOKE ALL ON DBA_ FROM <Non-DBA/SYS grantee>;
References:
1. http://docs.oracle.com/cd/E11882_01/server.112/e25789/datadict.htm#autoId2
4.5.6 Limiting authorizations for the SCHEDULER$_CREDENTIAL table

(Scored)
Description:
The Oracle database SCHEDULER$_CREDENTIAL table contains the database scheduler

credential information.
Rationale:
As permitting non-privileged users the authorization to open the

SYS.SCHEDULER$_CREDENTIAL table.
Audit:
103 | P a g e
SQL> SELECT GRANTEE, PRIVILEGE FROM DBA_TAB_PRIVS WHERE
TABLE_NAME='SCHEDULER$_CREDENTIAL';
Remediation:
SQL> REVOKE ALL ON SYS.SCHEDULER$_CREDENTIAL FROM <username>;
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_sched.htm#ARPLS7
2292
2. http://berxblog.blogspot.de/2012/02/restore-dbmsschedulercreatecredential.html
4.5.7 Drop table sys.user$mig (Scored)

Description:
The table sys.user$mig is created during migration and contains the Oracle password
hashes before the migration starts.
Rationale:
The table sys.user$mig is not deleted after the migration. An attacker could access the table
containing the Oracle password hashes.
Audit:
SQL> select owner,table_name from all_tables where owner='SYS' and

table_name='USER$MIG';
Remediation:
SQL> drop table sys.user$mig;
4.6 Limiting basic user privileges to restrict the ANY keyword (Scored)
Description:
104 | P a g e
The Oracle database ANY keyword provides the user the capability to alter any item in the
catalog of the database.
Rationale:
As authorization to use the ANY expansion of a privilege can allow an unauthorized user to
potentially change confidential data or damage the data catalog, this capability should be
Audit:
SQL> SELECT * FROM DBA_SYS_PRIVS WHERE PRIVILEGE LIKE '%ANY%' AND GRANTEE NOT IN
('AQ_ADMINISTRATOR_ROLE','DBA','DBSNMP','EXFSYS','EXP_FULL_DATABASE','IMP_FULL_DATABAS
E','DATAPUMP_IMP_FULL_DATABASE','JAVADEBUGPRIV','MDSYS','OEM_MONITOR','OLAPSYS','OLAP_
DBA','ORACLE_OCM','OWB$CLIENT','OWBSYS','SCHEDULER_ADMIN','SPATIAL_CSW_ADMIN_USR','SPA
TIAL_WFS_ADMIN_USR','SYS','SYSMAN','SYSTEM','WMSYS','APEX_030200','APEX_040000','APEX_
040100','APEX_040200','LBACSYS');
Remediation:
SQL> REVOKE ALL ON '<ANY Privilege>' FROM <grantee>;
References:
BSEG99877
4.7 Limiting users by restricting the WITH_ADMIN privilege (Scored)

Description:
The Oracle database WITH_ADMIN privilege allows the designated user to grant another user
the same privileges.
Rationale:
As assignment of the WITH_ADMIN privilege can allow the granting of a restricted privilege to
an unauthorized user, this capability should be restricted according to the needs of the
organization.
Audit:
105 | P a g e
SQL> SELECT * FROM DBA_SYS_PRIVS WHERE ADMIN_OPTION='YES' and GRANTEE not in
('AQ_ADMINISTRATOR_ROLE','DBA','OWBSYS', 'SCHEDULER_ADMIN','SYS','SYSTEM','WMSYS');
Remediation:
SQL> REVOKE <privilege> FROM <grantee>;
4.8 Limit direct privileges for proxy user (Scored)

Description:
Do not grant privileges directly to proxy users
Rationale:
A proxy user should only have the ability to connect to the database.
Audit:
SQL> select * from dba_role_privs where grantee in (select proxy from dba_proxies) and
granted_role not in ('CONNECT');
SQL> select * from dba_sys_privs where grantee in (select proxy from dba_proxies) and
privilege not in ('CREATE SESSION');
SQL> select * from dba_tab_privs where grantee in (select proxy from dba_proxies);
Remediation:
SQL> revoke privilege from <proxy_user>;
4.9 Revoke execute any procedure from user OUTLN (Scored)

Description:
106 | P a g e
Remove unneeded privileges from OUTLN
Rationale:
Migrated OUTLN users have more privileges than required.
Audit:
SQL> SELECT * FROM DBA_SYS_PRIVS where privilege='EXECUTE ANY PROCEDURE' and

grantee='OUTLN';
Remediation:
SQL> revoke EXECUTE ANY PROCEDURE from OUTLN;
4.10 Revoke execute any procedure from user DBSNMP (Scored)

Description:
Remove unneeded privileges from DBSNMP
Rationale:
Migrated DBSNMP users have more privileges than required.
Audit:
SQL> SELECT * FROM DBA_SYS_PRIVS where privilege='EXECUTE ANY PROCEDURE' and

grantee='DBSNMP';
Remediation:
SQL> revoke EXECUTE ANY PROCEDURE from DBSNMP;
107 | P a g e
5 Audit/Logging Policies and Procedures
The ability to audit system logs, to determine the result of user actions that have
potentially resulted in the loss or violations of availability, confidentiality, and/or integrity
is among the most important of all database security features. Decisions must be made
regarding the breadth/depth of the logging activity, as greater detail produces larger log
files. Measures must also be taken to protect the log files themselves, for these may be
targeted for alteration or destruction to hide unauthorized activity. There are numerous
command sequences for AUDIT, some of which are applicable to most database objects,
such as CREATE, ALTER, DROP, while others are limited to a few database objects, such as
GRANT,TRUNCATE,SET,SYSTEM AUDIT, and SYSTEM GRANT. The commands that apply to
larger numbers of objects will be addressed object by object after the primary connection
commands are dealt with.
5.1 Audit all CREATE SESSION (logon/logoff) activities (Scored)

Description:
The logging of all CREATE SESSION activities, the logon/logoff equivalent to remote
database access , will provide an audit trail of user connection; this is the minimum
privilege required to request access to run operations against the database.
Rationale:
As the logging of user connections to the database via logon/logoff activity can provide
forensic evidence of the initiation of a pattern of unauthorized activities, this capability
Audit:
SQL> SELECT USER_NAME, SUCCESS, FAILURE FROM DBA_PRIV_AUDIT_OPTS WHERE

PRIVILEGE='CREATE SESSION';
Remediation:
SQL> AUDIT CREATE SESSION;
5.2 Audit all CREATE USER object activities/requests (Scored)

108 | P a g e
Description:
The USER object for the Oracle database is a specification of an object which is an account
through which either a human or an application can connect to, via a JDBC or log into, via a
CLI, and interact with the database instance according to the roles and privileges allotted to
account.
Rationale:
As the logging of user activities involving the creation, alteration, or dropping of a USER
can provide forensic evidence about a pattern of suspect/unauthorized activities, the audit
capability should be set according to the needs of the organization.
Audit:
SQL> select USER_NAME, SUCCESS, FAILURE from DBA_STMT_AUDIT_OPTS where AUDIT_OPTION in

('CREATE USER','USER');
Remediation:
SQL> AUDIT CREATE USER;
5.3 Audit all ALTER USER object activities/requests (Scored)

Description:
account.
Rationale:
Audit:
109 | P a g e
('ALTER USER', 'USER');
Remediation:
SQL> AUDIT ALTER USER;
5.4 Audit all DROP USER object activities/requests (Scored)

Description:
account.
Rationale:
Audit:

('DROP USER','USER');
Remediation:
SQL> AUDIT DROP USER;
5.5 Audit all user ROLE activities/requests (Scored)


110 | P a g e
Description:
The ROLE object allows for the creation of a set of privileges that can be granted to users/
other roles, both for application connection and database administrative purposes.
Rationale:
As the logging of user activities involving the creation, alteration, setting or dropping of a
ROLE can provide forensic evidence about a pattern of suspect/unauthorized activities,
the audit capability should be set according to the needs of the organization.
Audit:

('ROLE');
Remediation:
SQL> AUDIT ROLE;
5.6 Audit all user GRANT ROLE activities/requests (Scored)

Description:
The system grant allows to audit all type of grants and revokes.
Rationale:
As the logging of all grant and revokes (roles and system privileges) can provide forensic
evidence about a pattern of suspect/unauthorized activities, the audit capability should be
set according to the needs of the organization.
Audit:
SQL> select USER_NAME, SUCCESS, FAILURE from DBA_STMT_AUDIT_OPTS where

AUDIT_OPTION='SYSTEM GRANT';
Remediation:
111 | P a g e
SQL> AUDIT SYSTEM GRANT;
5.7 Audit all user CREATE PROFILE activities/requests (Scored)

Description:
The PROFILE object allows for the creation of a set of database resource limits that can be
assigned to a user, so that that user cannot exceed those resource limitations.
Rationale:
As the logging of user activities involving the creation, alteration, or dropping of a PROFILE
can provide forensic evidence about a pattern of unauthorized activities, the audit
Audit:

('CREATE PROFILE','PROFILE');
Remediation:
SQL> AUDIT CREATE PROFILE;
5.8 Audit all user ALTER PROFILE activities/requests (Scored)

Description:
Rationale:
Audit:
112 | P a g e
('ALTER PROFILE','PROFILE');
Remediation:
SQL> AUDIT ALTER PROFILE;
5.9 Audit all user DROP PROFILE activities/requests (Scored)

Description:
Rationale:
Audit:

('DROP PROFILE','PROFILE');
Remediation:
SQL> AUDIT DROP PROFILE;
5.10 Audit all DATABASE LINK activities/requests (Scored)

113 | P a g e
Description:
All activities on database links should be audited.
Rationale:
As the logging of user activities involving the creation or dropping of a DATABASE LINK can
provide forensic evidence about a pattern of unauthorized activities, the audit capability
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option='DATABASE LINK';
Remediation:
SQL> AUDIT DATABASE LINK;
References:
SQLRF01107
5.11 Audit all PUBLIC DATABASE LINK activities/requests (Scored)

Description:
The PUBLIC DATABASE LINK object allows for the creation of a public link for an
application-based "user" to access the database for connections/session creation .
Rationale:
As the logging of user activities involving the creation, alteration, or dropping of a PUBLIC
DATABASE LINK can provide forensic evidence about a pattern of unauthorized activities,
the audit capability should be set according to the needs of the organization.
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option='PUBLIC DATABASE LINK';
Remediation:
114 | P a g e
SQL> audit public database link;
5.12 Audit all PUBLIC SYNONYM activities/requests (Scored)

Description:
The PUBLIC SYNONYM object allows for the creation of an alternate description of an object
and public synonyms are accessible by all users that have the appropriate privileges to the
underlying object.
Rationale:
As the logging of user activities involving the creation or dropping of a PUBLIC SYNONYM
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option='PUBLIC SYNONYM';
Remediation:
SQL> AUDIT PUBLIC SYNONYM;
5.13 Audit all user SYNONYM activities/requests (Scored)

Description:
The SYNONYM operation allows for the creation of a an alternative name for a database
object such as a Java class schema object, materialized view, operator, package, procedure,
sequence, stored function, table, view, user-defined object type, even another synonym;
this synonym puts a dependency on its target and is rendered invalid if the target object is
changed/dropped.
115 | P a g e
Rationale:
As the logging of user activities involving the creation or dropping of a SYNONYM can
provide forensic evidence about a pattern of suspect/unauthorized activities, the audit
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option='SYNONYM';
Remediation:
SQL> AUDIT SYNONYM;
References:
SQLRF01107
5.14 Audit all grants and revokes of privileges on directories (Scored)

Description:
The DIRECTORY object allows for the creation of a directory object that specifies an alias for
a directory on the server file system, where the external binary file LOBs (BFILEs)/ table
data are located.
Rationale:
As the logging of user activities involving the creation or dropping of a DIRECTORY can
provide forensic evidence about a pattern of unauthorized activities, the audit capability
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option='GRANT DIRECTORY';
Remediation:
SQL> AUDIT GRANT DIRECTORY;
References:
116 | P a g e
SQLRF01107
5.15 Audit all user SELECT ANY DICTIONARY activities/requests (Scored)

Description:
The SELECT ANY DICTIONARY capability allows the user to view the definitions of all schema
objects in the database.
Rationale:
As the logging of user activities involving the capability to access the description of all
schema objects in the database can provide forensic evidence about a pattern of
unauthorized activities, the audit capability should be set according to the needs o f the
organization.
Audit:
SQL> SELECT * FROM DBA_STMT_AUDIT_OPTS WHERE AUDIT_OPTION='SELECT ANY DICTIONARY';
Remediation:
SQL> AUDIT SELECT ANY DICTIONARY;
References:
SQLRF01107
5.16 Audit all user GRANT ANY OBJECT PRIVILEGE activities/requests

(Scored)
Description:
The GRANT ANY OBJECT PRIVILEGE allows for the granting of any OBJECT privilege, which
includes directories, flashbacks, mining models, etc.
117 | P a g e
Rationale:
As the logging of privilege grants that can lead to the creation, alteration, or dropping
of tables, users and other critical system components is critical to forensic investigations,
this audit capability should be set according to the needs of the organization.
Audit:
SQL> select * from DBA_PRIV_AUDIT_OPTS where privilege='GRANT ANY OBJECT PRIVILEGE';
Remediation:
SQL> AUDIT GRANT ANY OBJECT PRIVILEGE;
References:
SQLRF01107
5.17 Audit all user GRANT ANY PRIVILEGE activities/requests (Not

Scored)
Description:
The GRANT ANY PRIVILEGE allows for the granting of any privilege, including those at the
DBA level, so that the entire range of DBA capabilities is open to to the grantee.
Rationale:
As the logging of privilege grants that can lead to the creation, alteration, or dropping of
tables, users and other critical system components, this audit capability should be set
Audit:
SQL> select * from DBA_PRIV_AUDIT_OPTS where privilege='GRANT ANY PRIVILEGE';
Remediation:
SQL> AUDIT GRANT ANY PRIVILEGE;
References:
118 | P a g e
SQLRF01107
5.18 Audit all user CREATE PROCEDURE activities/requests (Scored)

Description:
The AUDIT PROCEDURE audit command allows for the tracking a number of user activities,
including the:
FUNCTION, the creation/dropping of a standalone stored function or a "Call specification"

that is like a procedure, except functions return values to its original environment and can
be in Java or other 3GL languages;
LIBRARY, which is the creation/dropping of a schema object associated with an operating-

system shared library;
PACKAGE, which is the creation/dropping of a locally stored collection of related

procedures, functions, and potentially other program objects stored together; and
PROCEDURE, which is the creation/dropping of a procedure--this is a subprogram that

performs a specified action that is stored in the database.
Rationale:
As the logging of user activities involving the creation, alteration, or dropping of a

PROCEDURE and its related activities can provide forensic evidence about a pattern of
unauthorized activities, this audit capability should be set according to the needs of the
organization.
Audit:

PRIVILEGE='CREATE PROCEDURE';
Remediation:
SQL> AUDIT CREATE PROCEDURE;
119 | P a g e
5.19 Audit all user CREATE ANY PROCEDURE activities/requests (Scored)
Description:
The AUDIT CREATE ANY PROCEDURE command is auditing the creation of procedures in
other schema.
Rationale:

organization.
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option = 'CREATE ANY PROCEDURE';
Remediation:
SQL> AUDIT CREATE ANY PROCEDURE;
5.20 Audit all user ALTER ANY PROCEDURE activities/requests (Scored)

Description:
The AUDIT ALTER ANY PROCEDURE command is auditing the alteration of procedures in
other schema.
Rationale:

120 | P a g e
organization.
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option = 'ALTER ANY PROCEDURE';
Remediation:
SQL> AUDIT ALTER ANY PROCEDURE;
5.21 Audit all user DROP ANY PROCEDURE activities/requests (Scored)

Description:
The AUDIT DROP ANY PROCEDURE command is auditing the creation of procedures in other
schema.
Rationale:
Dropping procedures of another user could be part of an privilege escalation exploit

and should be audited.
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option = 'DROP ANY PROCEDURE';
Remediation:
SQL> AUDIT DROP ANY PROCEDURE;
5.22 Audit all user CREATE ANY LIBRARY activities/requests (Scored)

Description:
The AUDIT CREATE ANY LIBRARY command is auditing the creation of libraries.
Rationale:
121 | P a g e
organization.
Audit:
SQL> select * from dba_stmt_audit_opts where audit_option='PROCEDURE' or audit_option

= 'CREATE ANY LIBRARY' or audit_option = 'CREATE LIBRARY';
Remediation:
SQL> AUDIT CREATE ANY LIBRARY;
5.23 Audit all user DROP ANY LIBRARY activities/requests (Scored)

Description:
The AUDIT PROCEDURE audit command allows for the tracking a number of user activities,
including the:
FUNCTION, the creation/dropping of a standalone stored function or a "Call specification"

that is like a procedure, except functions return values to its original environment and can
be in Java or other 3GL languages;
LIBRARY, which is the creation/dropping of a schema object associated with an operating-

system shared library;
PACKAGE, which is the creation/dropping of a locally stored collection of related

procedures, functions, and potentially other program objects stored together; and
PROCEDURE, which is the creation/dropping of a procedure--this is a subprogram that

performs a specified action that is stored in the database.
Rationale:
122 | P a g e
organization.
Audit:
SQL> SELECT USER_NAME, SUCCESS, FAILURE FROM DBA_PRIV_AUDIT_OPTS WHERE PRIVILEGE='DROP

ANY LIBRARY';
Remediation:
SQL> AUDIT DROP ANY LIBRARY;
5.24 Audit all user CREATE ANY TRIGGER activities/requests (Scored)

Description:
Auditing CREATE ANY TRIGGER allows to monitor who is creating trigger in other schema.
Rationale:
Trigger in other schema can be used to escalate privileges.
Audit:

PRIVILEGE='CREATE ANY TRIGGER';
Remediation:
SQL> AUDIT CREATE ANY TRIGGER;
5.25 Audit all user ALTER ANY TRIGGER activities/requests (Scored)

123 | P a g e
Description:
Auditing ALTER ANY TRIGGER allows to monitor who is altering trigger code in other
schema.
Rationale:
Trigger in other schema can be used to escalate privileges.
Audit:

PRIVILEGE='ALTER ANY TRIGGER';
Remediation:
SQL> AUDIT ALTER ANY TRIGGER;
5.26 Audit all user DROP ANY TRIGGER activities/requests (Scored)

Description:
Auditing DROP ANY TRIGGER allows to monitor who is dropping trigger in other schema.
Rationale:
Dropping Trigger in other schema can be used to remove restrictions on a schema or an

object.
Audit:
SQL> SELECT USER_NAME, SUCCESS, FAILURE FROM DBA_PRIV_AUDIT_OPTS WHERE PRIVILEGE='DROP

ANY TRIGGER';
Remediation:
SQL> AUDIT DROP ANY TRIGGER BY ACCESS;
5.27 Set AUDIT ALL ON SYS.AUD$ activities (Scored)

124 | P a g e
Description:
The logging of attempts to alter the audit trail in the SYS.AUD$ table (open for
read/update/delete/view) will provide a record of any activities that may indicate
unauthorized attempts to access the audit trail.
Rationale:
As the logging of attempts to alter the SYS.AUD$ table can provide forensic evidence of the
initiation of a pattern of unauthorized activities, this logging capability should be set
Audit:
SQL> SELECT * from DBA_OBJ_AUDIT_OPTS where OBJECT_NAME='AUD$';
Remediation:
SQL> AUDIT ALL on SYS.AUD$;
5.28 Audit all user ALTER SYSTEM activities/requests (Scored)

Description:
Auditing ALTER SYSTEM allows to modify the database settings.
Rationale:
Alter system allows one to change instance settings, including security settings and
auditing options. Additionally alter system can be used to run operating system commands
using undocumented Oracle functionality.
Audit:

PRIVILEGE='ALTER SYSTEM';
Remediation:
SQL> AUDIT ALTER SYSTEM;
125 | P a g e
126 | P a g e
Appendix: Change History
Date Version Changes for this version
12-11-2012 1.0.0 Initial release.
127 | P a g e

CIS Oracle Database Server 11 - 11g R2 Benchmark v1.0.0

Uploaded by

Copyright:

Available Formats

CIS Oracle Database Server 11 - 11g R2 Benchmark v1.0.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CIS Oracle Database Server 11 - 11g R2 Benchmark v1.0.0

Uploaded by

Copyright:

Available Formats

CIS Oracle Database Server 11 - 11g R2

Export Date 12-11-2012

CIS SECURITY BENCHMARKS TERMS OF USE

UNDER THE FOLLOWING TERMS AND CONDITIONS:

To obtain the latest version of this guide, please visit http://benchmarks.cisecurity.org. If

Level 1 - 11.x on any platform

o be practical and prudent;

Items in this profile intend to:

o be practical and prudent;

1.1 Change the Oracle default account passwords

1.1.1 Change the default password for 'APEX_040000' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice:

1.1.2 Change the default password for 'APPQOSSYS' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice:

1.1.3 Change the default password for 'CTXSYS' (Scored)

Level 1 - 11.x on any platform

The CTXSYS is used to administer Oracle Text.

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice:

1.1.4 Change the default password for 'DBSNMP' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

1.1.5 Change the default password for 'DIP' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice:

1.1.6 Change the default password for 'EXFSYS' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice:

1.1.7 Change the default password for 'MDDATA' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice:

1.1.8 Change the default password for 'MDSYS' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice:

1.1.9 Change the default password for 'LBACSYS' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice:

1.1.10 Change the default password for 'OLAPSYS' (Scored)

Level 1 - 11.x on any platform

select 'defaultpwd' as defaultpassword

Execute the following command to change the password

Enter the new password twice: