CIS Oracle Database 12c Benchmark v2.1.0
CIS Oracle Database 12c Benchmark v2.1.0
Terms of Use
Please see the below link for our current terms of use:
https://www.cisecurity.org/cis-securesuite/cis-securesuite-membership-terms-of-use/
1 | P a g e
Table of Contents
Terms of Use ................................................................................................................................................................... 1
Overview ........................................................................................................................................................................... 9
Intended Audience .................................................................................................................................................. 9
Consensus Guidance ............................................................................................................................................... 9
Typographical Conventions ............................................................................................................................. 10
Scoring Information ............................................................................................................................................ 10
Profile Definitions ................................................................................................................................................ 11
Acknowledgements ............................................................................................................................................. 13
Recommendations..................................................................................................................................................... 14
1 Oracle Database Installation and Patching Requirements ........................................................... 14
1.1 Ensure the Appropriate Version/Patches for Oracle Software Is Installed (Not
Scored) ............................................................................................................................................................. 14
1.2 Ensure All Default Passwords Are Changed (Scored) ....................................................... 16
1.3 Ensure All Sample Data And Users Have Been Removed (Scored)............................. 18
2 Oracle Parameter Settings ............................................................................................................................ 20
2.1 Listener Settings ....................................................................................................................................... 21
2.1.1 Ensure 'SECURE_CONTROL_' Is Set In 'listener.ora' (Scored) ................................... 21
2.1.2 Ensure 'extproc' Is Not Present in 'listener.ora' (Scored) ........................................... 23
2.1.3 Ensure 'ADMIN_RESTRICTIONS_' Is Set to 'ON' (Scored) ............................................ 25
2.1.4 Ensure 'SECURE_REGISTER_' Is Set to 'TCPS' or 'IPC' (Scored) ............................... 27
2.2 Database Settings ..................................................................................................................................... 29
2.2.1 Ensure 'AUDIT_SYS_OPERATIONS' Is Set to 'TRUE' (Scored) ................................... 29
2.2.2 Ensure 'AUDIT_TRAIL' Is Set to 'DB', 'XML', 'OS', 'DB,EXTENDED', or
'XML,EXTENDED' (Scored) .................................................................................................................... 31
2.2.3 Ensure 'GLOBAL_NAMES' Is Set to 'TRUE' (Scored)....................................................... 33
2.2.4 Ensure 'O7_DICTIONARY_ACCESSIBILITY' Is Set to 'FALSE' (Scored) .................. 34
2.2.5 Ensure 'OS_ROLES' Is Set to 'FALSE' (Scored) .................................................................. 36
2.2.6 Ensure 'REMOTE_LISTENER' Is Empty (Scored) ............................................................. 37
2.2.7 Ensure 'REMOTE_LOGIN_PASSWORDFILE' Is Set to 'NONE' (Scored) ................. 39
2 | P a g e
3 | P a g e
4 | P a g e
5 | P a g e
6 | P a g e
7 | P a g e
5.2.5 Ensure the 'ALTER ROLE’ Action Audit Is Enabled (Scored) .................................. 238
5.2.6 Ensure the 'DROP ROLE’ Action Audit Is Enabled (Scored) .................................... 240
5.2.7 Ensure the 'GRANT' Action Audit Is Enabled (Scored) .............................................. 242
5.2.8 Ensure the 'REVOKE' Action Audit Is Enabled (Scored) ........................................... 244
5.2.9 Ensure the 'CREATE PROFILE’ Action Audit Is Enabled (Scored) ........................ 246
5.2.10 Ensure the 'ALTER PROFILE’ Action Audit Is Enabled (Scored) ........................ 248
5.2.11 Ensure the 'DROP PROFILE’ Action Audit Is Enabled (Scored) .......................... 250
5.2.12 Ensure the 'CREATE DATABASE LINK’ Action Audit Is Enabled (Scored) .... 252
5.2.13 Ensure the 'ALTER DATABASE LINK’ Action Audit Is Enabled (Scored) ....... 254
5.2.14 Ensure the 'DROP DATABASE LINK’ Action Audit Is Enabled (Scored) ......... 256
5.2.15 Ensure the 'CREATE SYNONYM’ Action Audit Is Enabled (Scored) .................. 258
5.2.16 Ensure the 'ALTER SYNONYM’ Action Audit Is Enabled (Scored) ..................... 260
5.2.17 Ensure the 'DROP SYNONYM’ Action Audit Is Enabled (Scored) ....................... 262
5.2.18 Ensure the 'SELECT ANY DICTIONARY’ Privilege Audit Is Enabled (Scored)
.......................................................................................................................................................................... 264
5.2.19 Ensure the 'UNIFIED_AUDIT_TRAIL’ Access Audit Is Enabled (Scored) ........ 266
5.2.20 Ensure the 'CREATE PROCEDURE/FUNCTION/PACKAGE/PACKAGE BODY’
Action Audit Is Enabled (Scored) ..................................................................................................... 268
5.2.21 Ensure the 'ALTER PROCEDURE/FUNCTION/PACKAGE/PACKAGE BODY’
Action Audit Is Enabled (Scored) ..................................................................................................... 270
5.2.22 Ensure the 'DROP PROCEDURE/FUNCTION/PACKAGE/PACKAGE BODY’
Action Audit Is Enabled (Scored) ..................................................................................................... 272
5.2.23 Ensure the 'ALTER SYSTEM’ Privilege Audit Is Enabled (Scored) .................... 274
5.2.24 Ensure the 'CREATE TRIGGER’ Action Audit Is Enabled (Scored) .................... 276
5.2.25 Ensure the 'ALTER TRIGGER’ Action Audit IS Enabled (Scored) ....................... 278
5.2.26 Ensure the 'DROP TRIGGER’ Action Audit Is Enabled (Scored).......................... 280
5.2.27 Ensure the 'LOGON’ AND ‘LOGOFF’ Actions Audit Is Enabled (Scored) ......... 282
6 Appendix: Establishing an Audit/Scan User ..................................................................................... 284
Appendix: Summary Table ................................................................................................................................. 286
Appendix: Change History .................................................................................................................................. 293
8 | P a g e
Overview
This document is intended to address the recommended security settings for Oracle
Database 12c. This guide was tested against Oracle Database 12c (version 12.1.0.2)
installed without pluggable database support running on a Windows Server 2012 R2
instance as a stand-alone system and running on an Oracle Linux 7 instance also as a stand-
alone system. Future Oracle Database 12c critical patch updates (CPUs) may impact the
recommendations included in this document.
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 12c on Oracle Linux or
Microsoft Windows Server.
Consensus Guidance
This benchmark was created using a consensus review process comprised of 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 published. 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 process, please visit
https://workbench.cisecurity.org/.
9 | P a g e
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.
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.
10 | P a g e
Profile Definitions
The following configuration profiles are defined by this Benchmark:
Items in this profile apply to Oracle Database 12c configured to use Traditional
Auditing and intend to:
This profile extends the “RDBMS using Traditional Auditing” profile. Items in this
profile apply to RDBMS running on a Linux Host operating system with Oracle
Database 12c configured to use Traditional Auditing and intend to:
This profile extends the “RDBMS using Traditional Auditing” profile. Items in this
profile apply to RDBMS running on a Windows Server operating system with Oracle
Database 12c configured to use Traditional Auditing and intend to:
Items in this profile apply to Oracle Database 12c configured to use Unified Auditing
and intend to:
11 | P a g e
This profile extends the “RDBMS using Unified Auditing” profile. Items in this profile
apply to RDBMS running on a Linux Host operating system with Oracle Database
12c configured to use Unified and intend to:
This profile extends the “RDBMS using Unified Auditing” profile. Items in this profile
apply to RDBMS running on a Windows Server operating system with Oracle
Database 12c configured to use Unified and intend to:
12 | 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
Jay Mehta
Contributor
Alexander Kornbrust
S. Brian Suddeth
Pieter Van Puymbroeck
Arman Rawls
Adam Montville
Tung Bui Viet
Jignesh Patel
Than Thi Cham
Dean Lackey
Kyle Thomason
Justin Brown
Gijs Hasselman
Stephen Dufour
Philippe Langlois
Editor
Angelo Marcotullio
Tim Harrison CISSP, ICP, Center for Internet Security
Karen Scarfone
13 | 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. It is additionally prudent to remove Oracle sample data
from production environments.
Description:
The Oracle installation version and patches should be the most recent that are compatible
with the organization's operational needs.
Rationale:
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. Ensure you are using a release that is covered by a level of support that
includes the generation of Critical Patch Updates.
Audit:
To assess this recommendation, use the following example shell command as appropriate
for your environment.
14 | P a g e
Remediation:
Download and apply the latest quarterly Critical Patch Update patches.
References:
1. http://www.oracle.com/us/support/assurance/fixing-policies/index.html
2. http://www.oracle.com/technetwork/topics/security/alerts-086861.html
3. http://www.oracle.com/us/support/library/lifetime-support-technology-
069183.pdf
CIS Controls:
Version 6
15 | P a g e
Description:
Rationale:
Audit:
SELECT USERNAME
FROM DBA_USERS_WITH_DEFPWD
WHERE USERNAME NOT LIKE '%XS$NULL%';
The view called DBA_USERS_WITH_DEFPWD shows a list of all database users making use of
default passwords. The assessment fails if results are returned.
Note: Per Oracle Support Document 2173962.1, "after creation of a new 12c database, the
SYS and SYSTEM accounts are listed in DBA_USERS_WITH_DEFPWD even though the accounts
were created with non-default passwords. Setting the same passwords again with ALTER
USER correctly recognizes that the accounts do not have default passwords."
Remediation:
To remediate this recommendation, you may perform either of the following actions:
• Manually issue the following SQL statement for each USERNAME returned in the
Audit Procedure:
PASSWORD <username>
16 | P a g e
• Execute the following SQL script to assign a randomly generated password to each
account using a default password:
begin
for r_user in
(select username from dba_users_with_defpwd where username not
like '%XS$NULL%')
loop
DBMS_OUTPUT.PUT_LINE('Password for user '||r_user.username||'
will be changed.');
execute immediate 'alter user "'||r_user.username||'" identified
by "'||DBMS_RANDOM.string('a',16)||'"account lock password expire';
end loop;
end;
References:
1. http://docs.oracle.com/database/121/TDPSG/GUID-3EC7A894-D620-4497-AFB1-
64EB8C33D854.htm#TDPSG20021
2. https://support.oracle.com/epmos/faces/DocumentDisplay?id=2173962.1
CIS Controls:
Version 6
17 | P a g e
1.3 Ensure All Sample Data And Users Have Been Removed (Scored)
Profile Applicability:
Description:
Oracle sample schemas can be used to create sample users (BI,HR,IX,OE,PM,SCOTT,SH), with
well-known default passwords, particular views, and procedures/functions, in addition to
tables and fictitious data. The sample schemas should be removed.
Rationale:
The sample schemas are typically not required for production operations of the database.
The default users, views, and/or procedures/functions created by sample schemas could
be used to launch exploits against production environments.
Audit:
To assess this recommendation, check for the presence of Oracle sample users by executing
the following SQL statement.
SELECT USERNAME
FROM ALL_USERS
WHERE USERNAME IN ('BI','HR','IX','OE','PM','SCOTT','SH');"
Remediation:
Note: The recyclebin is not set to OFF within the default drop script, which means that the
data will still be present in your environment until the recyclebin is emptied.
Impact:
The Oracle sample usernames may be in use on a production basis. It is important that you
first verify that BI, HR, IX, OE, PM, SCOTT, and/or SH are not valid production usernames
18 | P a g e
before executing the dropping SQL scripts. This may be particularly true with the HR and BI
users. If any of these users are present, it is important to be cautious and confirm the
schemas present are, in fact, Oracle sample schemas and not production schemas
being relied upon by business operations.
References:
1. http://docs.oracle.com/database/121/COMSC/toc.htm
CIS Controls:
Version 6
19 | P a g e
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.
20 | P a g e
Description:
Rationale:
Audit:
For example:
LISTENER1 =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP) (HOST=sales-server)(PORT=1521))
(ADDRESS=(PROTOCOL=IPC) (KEY=REGISTER))
(ADDRESS=(PROTOCOL=TCPS) (HOST=sales-server)(PORT=1522)))
SECURE_CONTROL_LISTENER1=TCPS"
21 | P a g e
Remediation:
References:
1. http://docs.oracle.com/database/121/NETRF/listener.htm#NETRF327
CIS Controls:
Version 6
22 | P a g e
Description:
extproc should be removed from the listener.ora to mitigate the risk that OS libraries
can be invoked by the Oracle instance.
Rationale:
extproc allows the database to run procedures from OS libraries. These library calls can, in
turn, run any OS command.
Audit:
To audit this recommendation, execute the following shell commands as appropriate for
your Linux/Windows environment.
Linux environment:
grep -i extproc $ORACLE_HOME/network/admin/listener.ora
Windows environment:
find /I extproc %ORACLE_HOME%\network\admin\listener.ora
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/app_devs.htm#DBSEG656
23 | P a g e
CIS Controls:
Version 6
24 | P a g e
Description:
Rationale:
Blocking unprivileged users from making alterations of the listener.ora file, where
remote data/service settings are specified, will help protect data confidentiality.
Audit:
To audit this recommendation, execute the following shell commands as appropriate for
your Linux/Windows environment.
Linux environment:
grep -i admin_restrictions $ORACLE_HOME/network/admin/listener.ora
Windows environment:
find /I admin_restrictions %ORACLE_HOME%|\network\admin\listener.ora
Remediation:
Default Value:
25 | P a g e
Not set.
References:
1. http://docs.oracle.com/database/121/NETRF/listener.htm#NETRF310
CIS Controls:
Version 6
26 | P a g e
Description:
Rationale:
Audit:
To audit this recommendation, execute the following shell commands as appropriate for
your Linux/Windows environment.
Linux environment:
grep -i SECURE_REGISTER $ORACLE_HOME/network/admin/listener.ora
Windows environment:
find /I SECURE_REGISTER %ORACLE_HOME%\network\admin\listener.ora
Remediation:
27 | P a g e
References:
1. http://docs.oracle.com/database/121/NETRF/listener.htm#NETRF328
2. https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=145388
3.1
3. https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=134083
1.1
4. http://www.joxeankoret.com/download/tnspoison.pdf
Notes:
Oracle Real Application Cluster requires a different approach to fix the TNS Poisoning
problem. See Oracle support note 1453883.1 for details.
CIS Controls:
Version 6
28 | P a g e
Note: The remediation procedures assume the use of a server parameter file, which is often
a preferred method of storing server initialization parameters.
For your environment, leaving off the SCOPE = SPFILE directive or substituting it with
SCOPE = BOTH might be preferred depending on the recommendation.
Description:
The AUDIT_SYS_OPERATIONS setting provides for the auditing of all user activities conducted
under the SYSOPER and SYSDBA accounts. The setting should be set to TRUE to enable this
auditing.
Rationale:
Audit:
Remediation:
29 | P a g e
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-58176267-238C-40B5-B1F2-
BB8BB9518950.htm#REFRN10005
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
30 | P a g e
Description:
The audit_trail setting determines whether or not Oracle's basic audit features are
enabled. It can be set to "Operating System"(OS); DB; DB,EXTENDED; XML; or XML,EXTENDED.
The value should be set according to the needs of the organization.
Rationale:
Enabling the basic auditing features for the Oracle instance permits the collection of data to
troubleshoot problems, as well as provides valuable forensic logs in the case of a system
breach this value should be set according to the needs of the organization.
Audit:
Remediation:
31 | P a g e
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-BD86F593-B606-4367-9FB6-
8DAB2E47E7FA.htm#REFRN10006
2. http://www.oracle.com/technetwork/products/audit-vault/learnmore/twp-
security-auditperformance-166655.pdf
CIS Controls:
Version 6
32 | P a g e
Description:
The global_names setting requires that the name of a database link matches that of the
remote database it will connect to. This setting should have a value of TRUE.
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-221D0483-D814-4963-84E1-
7D39A25048ED.htm#REFRN10065
CIS Controls:
Version 6
33 | P a g e
Description:
Rationale:
Leaving the SYS schema so open to connection could permit unauthorized access to critical
data structures.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-1D1A88F1-B603-48FF-BD30-
E6099DB1A1ED.htm#REFRN10133
34 | P a g e
Notes:
The value for this is "O(oh)7" not "0(Zero)7" for O7. Also, for "Oracle Applications" up to
version 11.5.9, this setting is reversed; the O7_dictionary_accessibility=TRUE value is
required for correct operations.
CIS Controls:
Version 6
35 | P a g e
Description:
Rationale:
Allowing the OS to use external groups for database management could cause privilege
overlaps and generally weaken security.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-51CCE2D6-F841-4E02-A89D-
EA08FC110CF3.htm#REFRN10153
CIS Controls:
Version 6
36 | P a g e
Description:
The remote_listener setting determines whether or not a valid listener can be established
on a system separate from the database instance. This setting should be empty unless the
organization specifically needs a valid listener on a separate system.
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-FEE2E8B5-CE02-4158-A6B4-
030E59316756.htm#REFRN10183
Notes:
37 | P a g e
CIS Controls:
Version 6
38 | P a g e
Description:
Rationale:
The use of this sort of password login file could permit unsecured, privileged connections
to the database.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-6619299E-95E8-4821-B123-
3B5899F046C7.htm#REFRN10184
CIS Controls:
Version 6
39 | P a g e
Description:
The remote_os_authent setting determines whether or not OS 'roles' with the attendant
privileges are allowed for remote client connections. This setting should have a value of
FALSE.
Rationale:
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:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-AB66C849-FE5A-4E06-A6E1-
AEE775D55703.htm#REFRN10185
CIS Controls:
Version 6
40 | P a g e
Description:
Rationale:
Allowing remote clients OS roles to have permissions for database management could
cause privilege overlaps and generally weaken security.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-BAA83447-14C1-4BE7-BB5D-
806ED3E00AED.htm#REFRN10186
CIS Controls:
Version 6
41 | P a g e
Description:
Rationale:
Using the utl_file_dir to create directories allows the manipulation of files in these
directories.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-DCA8A942-ACE1-46D6-876E-
3244F390BCAE.htm#REFRN10230
CIS Controls:
Version 6
42 | P a g e
Description:
Rationale:
Oracle database password case-sensitivity increases the pool of characters that can be
chosen for the passwords, making brute-force password attacks quite difficult.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-F464653A-0D43-4A70-8F05-
0274A12C8578.htm#REFRN10299
CIS Controls:
Version 6
43 | P a g e
Description:
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-DEC2A3B2-F49B-499E-A3CF-
D097F3A5BA83.htm#REFRN10274
44 | P a g e
CIS Controls:
Version 6
45 | P a g e
Description:
Rationale:
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:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-1E8D3C6E-C919-4218-8117-
760D31BD0F95.htm#REFRN10282
46 | P a g e
CIS Controls:
Version 6
47 | P a g e
Description:
Rationale:
Bad packets received from the client can potentially indicate packet-based attacks on the
system, which could result in a denial-of-service condition.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-AE811BC1-8CED-4B21-B16C-
4B712B127535.htm#REFRN10283
48 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
49 | 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. This is sensitive
information that should not be revealed to anyone who requests it.
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-688102A0-11F5-4F06-8868-
934D65C4E878.htm#REFRN10275
50 | P a g e
CIS Controls:
Version 6
51 | P a g e
Description:
The SQL92_SECURITY parameter setting TRUE requires that a user must also be granted the
SELECT object privilege before being able to perform UPDATE or DELETE operations on tables
that have WHERE or SET clauses. The setting should have a value of TRUE.
Rationale:
A user without SELECT privilege can still infer the value stored in a column by referring to
that column in a DELETE or UPDATE statement. This setting prevents inadvertent information
disclosure by ensuring that only users who already have SELECT privilege can execute the
statements that would allow them to infer the stored values.
Audit:
Remediation:
Default Value:
FALSE
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-E41087C2-250E-4201-908B-
79E659B22A4B.htm#REFRN10210
52 | P a g e
CIS Controls:
Version 6
53 | P a g e
Description:
The _trace_files_public setting determines whether or not the system's trace file is
world readable. This setting should have a value of FALSE to restrict trace file access.
Rationale:
Making the file world readable means anyone can read the instance's trace file, which could
contain sensitive information about instance operations.
Audit:
Remediation:
References:
1. http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4295521
746131
CIS Controls:
Version 6
54 | P a g e
the information based on their need to access the information as a part of their
responsibilities.
55 | P a g e
Description:
Rationale:
If RESOURCE_LIMIT is set to FALSE, none of the system resource limits that are set in any
database profiles are enforced. If RESOURCE_LIMIT is set to TRUE, the limits set in database
profiles are enforced.
Audit:
Remediation:
Default Value:
FALSE
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-BB0AB177-3867-4D0D-8700-
A1AC8BDFEFC3.htm#REFRN10188
56 | P a g e
CIS Controls:
Version 6
57 | P a g e
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:
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 the Notes for a warning
on a known bug that can make this security measure backfire.)
Audit:
58 | P a g e
OR LIMIT > 5
);
Remediation:
Remediate this setting by executing the following SQL statement for each PROFILE returned
by the audit procedure.
Notes:
Warning: One great concern with the above is the possibility of this setting being exploited
to craft a DDoS attack by using the row-locking delay between failed login attempts (see
_Oracle Bug 7715339 – Logon failures causes “row cache lock” waits – Allow disable of
logon delay [ID 7715339.8], so the configuration of this setting depends on using the bug
workaround). Also, while the setting for the FAILED_LOGIN_ATTEMPTS value can also be set
in sqlnet.ora, this only applies to listed users. The similar setting used to block a DDoS,
the SEC_MAX_FAILED_LOGIN_ATTEMPTS initialization parameter, can be used to protect
unauthorized intruders from attacking the server processes for applications, but this
setting does not protect against unauthorized attempts via valid usernames.
CIS Controls:
Version 6
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. The
suggested value for this is one day or greater.
Rationale:
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.
Audit:
Remediation:
Remediate this setting by executing the following SQL statement for each PROFILE returned
by the audit procedure.
60 | P a g e
CIS Controls:
Version 6
61 | P a g e
Description:
The PASSWORD_LIFE_TIME setting determines how long a password may be used before the
user is required to be change it. The suggested value for this is 90 days or less.
Rationale:
Allowing passwords to remain unchanged for long periods makes the success of brute-
force login attacks more likely.
Audit:
Remediation:
Remediate this setting by executing the following SQL statement for each PROFILE
returned by the audit procedure.
CIS Controls:
Version 6
62 | P a g e
Description:
The PASSWORD_REUSE_MAX setting determines how many different passwords must be used
before the user is allowed to reuse a prior password. The suggested value for this is 20
passwords or greater.
Rationale:
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.
Audit:
Remediation:
Remediate this setting by executing the following SQL statement for each PROFILE returned
by the audit procedure.
Notes:
The above restriction should be applied along with the PASSWORD_REUSE_TIME setting.
63 | P a g e
CIS Controls:
Version 6
64 | P a g e
Description:
The PASSWORD_REUSE_TIME setting determines the amount of time in days that must pass
before the same password may be reused. The suggested value for this is 365 days or
greater.
Rationale:
Reusing the same password after only a short period of time has passed makes the success
of brute-force login attacks more likely.
Audit:
Remediation:
Remediate this setting by executing the following SQL statement for each PROFILE returned
by the audit procedure.
Notes:
The above restriction should be applied along with the PASSWORD_REUSE_MAX setting.
65 | P a g e
CIS Controls:
Version 6
66 | P a g e
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. The
suggested value for this is five days or less.
Rationale:
Locking the user account after the expiration of the password change requirement's grace
period can help prevent password-based attacks against any forgotten or disused accounts,
while still allowing the account and its information to be accessible by DBA intervention.
Audit:
Remediation:
Remediate this setting by executing the following SQL statement for each PROFILE returned
by the audit procedure.
67 | P a g e
CIS Controls:
Version 6
68 | P a g e
Description:
Rationale:
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.
Audit:
Remediation:
Notes:
The PASSWORD keyword (column) used in the SQL for prior Oracle versions has been
deprecated from version 11.2 onward in favor of the new AUTHENTICATION_TYPE keyword
(column) for the DBA_USERS table. However, the PASSWORD column has still been retained for
backward compatibility.
69 | P a g e
CIS Controls:
Version 6
70 | P a g e
Description:
Rationale:
Requiring users to apply the 12c security features in password creation, such as forcing
mixed-case complexity, blocking of simple combinations, and enforcing change/history
settings can potentially thwart logins by an unauthorized user.
Audit:
Remediation:
Create a custom password verification function which fulfills the password requirements of
the organization.
CIS Controls:
Version 6
71 | P a g e
Description:
The SESSIONS_PER_USER setting determines the maximum number of user sessions that are
allowed to be open concurrently. The suggested value for this is 10 or less.
Rationale:
Limiting the number of the SESSIONS_PER_USER can help prevent memory resource
exhaustion by poorly formed requests or intentional denial-of-service attacks.
Audit:
Remediation:
To remediate this setting, execute the following SQL statement for each PROFILE returned
by the audit procedure.
Notes:
72 | P a g e
CIS Controls:
Version 6
73 | P a g e
Description:
Upon creation database users are assigned to the DEFAULT profile unless otherwise
specified. No users should be assigned to that profile.
Rationale:
Users should be created with function-appropriate profiles. The DEFAULT profile, being
defined by Oracle, is subject to change at any time (e.g. by patch or version update). The
DEFAULT profile has unlimited settings that are often required by the SYS user when
patching; such unlimited settings should be tightly reserved and not applied to
unnecessary users.
Audit:
Remediation:
To remediate this recommendation, execute the following SQL statement for each user
returned by the audit query using a functional-appropriate profile.
74 | P a g e
CIS Controls:
Version 6
75 | P a g e
IMPORTANT: Use caution when revoking privileges from PUBLIC. Oracle and third-party
products explicitly require default grants to PUBLIC for commonly used functions, objects,
and in view definitions. After revoking any privilege from PUBLIC, verify that applications
keep running properly and recompile invalid database objects. Specific grants to users and
roles may be needed to make all objects valid. Please see the following Oracle support
document which provides further information and SQL statements that can be used to
determine dependencies that require explicit grants: Be Cautious When Revoking
Privileges Granted to PUBLIC (Doc ID 247093.1) Always test database changes in
development and test environments before making changes to production databases.
76 | P a g e
Description:
The Oracle database DBMS_ADVISOR package can be used to write files located on the server
where the Oracle instance is installed. The user PUBLIC should not be able to execute
DBMS_ADVISOR.
Rationale:
Use of the DBMS_ADVISOR package could allow an unauthorized user to corrupt operating
system files on the instance's host.
Audit:
SELECT PRIVILEGE
FROM DBA_TAB_PRIVS
WHERE GRANTEE='PUBLIC'
AND PRIVILEGE='EXECUTE'
AND TABLE_NAME='DBMS_ADVISOR';
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_advis.htm#ARPLS350
77 | P a g e
CIS Controls:
Version 6
78 | P a g e
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. The user PUBLIC should not be able to execute DBMS_CRYPTO.
Rationale:
Execution of these cryptography procedures by the user PUBLIC can potentially endanger
portions of or all of the data storage.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_crypto.htm#ARPLS664
79 | P a g e
CIS Controls:
Version 6
80 | P a g e
Description:
The Oracle database DBMS_JAVA package can run Java classes (e.g. OS commands) or grant
Java privileges. The user PUBLIC should not be able to execute DBMS_JAVA.
Rationale:
The DBMS_JAVA package could allow an attacker to run OS commands from the database.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/JJDEV/appendixa.htm#JJDEV13000
CIS Controls:
Version 6
81 | P a g e
data and scripts; unused libraries, components, debug code; or tools) are not
included in the deployed software, or accessible in the production environment.
82 | P a g e
Description:
The Oracle database DBMS_JAVA_TEST package can run Java classes (e.g. OS commands) or
grant Java privileges. The user PUBLIC should not be able to execute DBMS_JAVA_TEST.
Rationale:
The DBMS_JAVA_TEST package could allow an attacker to run operating system commands
from the database.
Audit:
Remediation:
Notes:
83 | P a g e
CIS Controls:
Version 6
84 | P a g e
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. The user PUBLIC should not be able to
execute DBMS_JOB.
Rationale:
Use of the DBMS_JOB package could allow an unauthorized user to disable or overload the
job queue. It has been superseded by the DBMS_SCHEDULER package.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_job.htm#ARPLS019
85 | P a g e
CIS Controls:
Version 6
86 | P a g e
Description:
The Oracle database DBMS_LDAP package contains functions and procedures that enable
programmers to access data from LDAP servers. The user PUBLIC should not be able to
execute DBMS_LDAP.
Rationale:
Use of the DBMS_LDAP package can be used to create specially crafted error messages or
send information via DNS to the outside.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_ldap.htm#ARPLS360
87 | P a g e
CIS Controls:
Version 6
88 | 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. The user PUBLIC should
not be able to execute DBMS_LOB.
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_lob.htm#ARPLS600
89 | P a g e
CIS Controls:
Version 6
90 | P a g e
Description:
The DBMS_OBFUSCATION_TOOLKIT provides 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. The user
PUBLIC should not be able to execute DBMS_OBFUSCATION_TOOLKIT.
Rationale:
Allowing the PUBLIC user privileges to access this capability can be potentially harm data
storage.
Audit:
SELECT PRIVILEGE
FROM DBA_TAB_PRIVS
WHERE GRANTEE='PUBLIC'
AND PRIVILEGE='EXECUTE'
AND TABLE_NAME='DBMS_OBFUSCATION_TOOLKIT';
Remediation:
CIS Controls:
Version 6
91 | P a g e
92 | P a g e
Description:
The Oracle database DBMS_RANDOM package is used for generating random numbers but
should not be used for cryptographic purposes. The user PUBLIC should not be able to
execute DBMS_RANDOM.
Rationale:
Use of the DBMS_RANDOM package can allow the unauthorized application of the random
number-generating function.
Audit:
Remediation:
References:
1. http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_random.htm
Notes:
The OEM cautions that removing this from PUBLIC may break certain applications.
93 | P a g e
CIS Controls:
Version 6
94 | P a g e
Description:
The Oracle database DBMS_SCHEDULER package schedules and manages the database and
operating system jobs. The user PUBLIC should not be able to execute DBMS_SCHEDULER.
Rationale:
Use of the DBMS_SCHEDULER package could allow an unauthorized user to run database or
operating system jobs.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_sched.htm#ARPLS72235
CIS Controls:
Version 6
95 | P a g e
96 | P a g e
Description:
The Oracle database DBMS_SQL package is used for running dynamic SQL statements. The
user PUBLIC should not be able to execute DBMS_SQL.
Rationale:
The DBMS_SQL package could allow privilege escalation if input validation is not done
properly.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_sql.htm#ARPLS058
CIS Controls:
Version 6
97 | P a g e
Description:
The DBMS_XMLGEN package takes an arbitrary SQL query as input, converts it to XML format,
and returns the result as a CLOB. The user PUBLIC should not be able to execute
DBMS_XMLGEN.
Rationale:
The package DBMS_XMLGEN can be used to search the entire database for sensitive
information like credit card numbers.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_xmlgen.htm#ARPLS374
2. http://www.red-database-security.com/wp/confidence2009.pdf
98 | P a g e
CIS Controls:
Version 6
13 Data Protection
Data Protection
99 | P a g e
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. The user PUBLIC
should not be able to execute DBMS_XMLQUERY.
Rationale:
The package DBMS_XMLQUERY can be used to search the entire database for sensitive
information like credit card numbers. Malicious users may be able to exploit this package
as an auxiliary inject function in a SQL injection attack.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_xmlque.htm#ARPLS376
100 | P a g e
CIS Controls:
Version 6
13 Data Protection
Data Protection
101 | P a g e
Description:
The Oracle database UTL_FILE package can be used to read/write files located on the
server where the Oracle instance is installed. The user PUBLIC should not be able to execute
UTL_FILE.
Rationale:
Use of the UTL_FILE package could allow an user to read OS files. These files could contain
sensitive information (e.g. passwords in .bash_history).
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/u_file.htm#ARPLS069
CIS Controls:
Version 6
102 | P a g e
Description:
The Oracle database UTL_INADDR package can be used to create specially crafted error
messages or send information via DNS to the outside. The user PUBLIC should not be able to
execute UTL_INADDR.
Rationale:
The UTL_INADDR package is often used in SQL injection attacks from the web it should be
revoked from public.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/u_inaddr.htm#ARPLS071
103 | P a g e
CIS Controls:
Version 6
104 | P a g e
Description:
The Oracle database UTL_TCP package can be used to read/write file to TCP sockets on the
server where the Oracle instance is installed. The user PUBLIC should not be able to execute
UTL_TCP.
Rationale:
The UTL_TCP package could allow an unauthorized user to corrupt the TCP stream used to
carry the protocols that communicate with the instance's external communications.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/u_tcp.htm#ARPLS075
CIS Controls:
Version 6
105 | P a g e
Description:
The Oracle database UTL_MAIL package can be used to send email from the server where
the Oracle instance is installed. The user PUBLIC should not be able to execute UTL_MAIL.
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/u_mail.htm#ARPLS384
106 | P a g e
CIS Controls:
Version 6
107 | P a g e
Description:
The Oracle database UTL_SMTP package can be used to send email from the server where
the Oracle instance is installed. The user PUBLIC should not be able to execute UTL_SMTP.
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/u_smtp.htm#ARPLS074
108 | P a g e
CIS Controls:
Version 6
109 | P a g e
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. This package is not
automatically installed for security reasons. The user PUBLIC should not be able to execute
UTL_DBWS.
Rationale:
The UTL_DBWS package could allow an unauthorized user to corrupt the HTTP stream used
to carry the protocols that communicate for the instance's web-based external
communications.
Audit:
Remediation:
References:
1. https://docs.oracle.com/database/121/JJPUB/intro.htm#BHCIBFGJ
CIS Controls:
110 | P a g e
Version 6
111 | P a g e
Description:
The Oracle database UTL_ORAMTS package can be used to perform HTTP requests. This
could be used to send information to the outside. The user PUBLIC should not be able to
execute UTL_ORAMTS.
Rationale:
Audit:
SELECT PRIVILEGE
FROM DBA_TAB_PRIVS
WHERE GRANTEE='PUBLIC'
AND PRIVILEGE='EXECUTE'
AND TABLE_NAME='UTL_ORAMTS';
Remediation:
References:
1. http://docs.oracle.com/database/121/NTMTS/recovery.htm#sthref73
112 | P a g e
CIS Controls:
Version 6
113 | P a g e
Description:
The Oracle database UTL_HTTP package can be used to perform HTTP requests. This could
be used to send information to the outside. The user PUBLIC should not be able to execute
UTL_HTTP.
Rationale:
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:
SELECT PRIVILEGE
FROM DBA_TAB_PRIVS
WHERE GRANTEE='PUBLIC'
AND PRIVILEGE='EXECUTE'
AND TABLE_NAME='UTL_HTTP';
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/u_http.htm#ARPLS070
114 | P a g e
CIS Controls:
Version 6
115 | P a g e
Description:
The Oracle database HTTPURITYPE object type can be used to perform HTTP requests. The
user PUBLIC should not be able to execute HTTPURITYPE.
Rationale:
The ability to perform HTTP requests could be used to leak information from the database
to an external destination.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/t_dburi.htm#ARPLS71705
CIS Controls:
Version 6
116 | P a g e
Description:
The DBMS_XLMSTORE package provides XML functionality. It accepts a table name and XML
as input to perform DML operations against the table. The user PUBLIC should not be able
to execute DBMS_XLMSTORE.
Rationale:
Malicious users may be able to exploit this package as an auxiliary inject function in a SQL
injection attack.
Audit:
Remediation:
References:
1. http://www.davidlitchfield.com/DBMS_XMLSTORE_PLSQL_Injection.pdf
117 | P a g e
CIS Controls:
Version 6
118 | P a g e
Description:
The DBMS_XLMSTORE package provides XML functionality. It accepts a table name and XML
as input and then inserts into or updates that table. The user PUBLIC should not be able to
execute DBMS_XLMSAVE.
Rationale:
Malicious users may be able to exploit this package as an auxiliary inject function in a SQL
injection attack.
Audit:
SELECT GRANTEE
FROM DBA_TAB_PRIVS
WHERE TABLE_NAME = 'DBMS_XMLSAVE'
AND GRANTEE = 'PUBLIC'
AND PRIVILEGE = 'EXECUTE';
Lack of results implies compliance.
Remediation:
References:
1. http://www.davidlitchfield.com/DBMS_XMLSTORE_PLSQL_Injection.pdf
CIS Controls:
Version 6
and documented for all input, including for size, data type, and acceptable ranges
or formats.
120 | P a g e
Description:
The DBMS_REDACT package provides an interface to Oracle Data Redaction, which enables
you to mask (redact) data that is returned from queries issued by low-privileged users or
an application. The user PUBLIC should not be able to execute DBMS_REDACT.
Rationale:
Malicious users may be able to exploit this package as an auxiliary inject function in a SQL
injection attack.
Audit:
SELECT GRANTEE
FROM DBA_TAB_PRIVS
WHERE TABLE_NAME = 'DBMS_REDACT'
AND GRANTEE = 'PUBLIC'
AND PRIVILEGE = 'EXECUTE';
Lack of results implies compliance.
Remediation:
CIS Controls:
Version 6
121 | P a g e
Description:
The Oracle database DBMS_SYS_SQL package is shipped as undocumented. The user PUBLIC
should not be able to execute DBMS_SYS_SQL.
Rationale:
The DBMS_SYS_SQL package could allow an user to run code as a different user without
entering valid credentials.
Audit:
Remediation:
122 | P a g e
References:
1. http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1325202
421535
CIS Controls:
Version 6
123 | P a g e
Description:
Rationale:
Audit:
Remediation:
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/
124 | P a g e
CIS Controls:
Version 6
125 | P a g e
Description:
Rationale:
Audit:
Remediation:
References:
1. http://securityvulns.ru/files/ohh-indirect-privilege-escalation.pdf
CIS Controls:
Version 6
126 | P a g e
Description:
Rationale:
Audit:
Remediation:
References:
1. http://securityvulns.ru/files/ohh-indirect-privilege-escalation.pdf
127 | P a g e
CIS Controls:
Version 6
128 | P a g e
Description:
The Oracle database INITJVMAUX package is shipped as undocumented and allows to run
SQL commands as user SYS. The user PUBLIC should not be able to execute INITJVMAUX.
Rationale:
The INITJVMAUX package could allow an unauthorized user to run SQL commands as user
SYS.
Audit:
Remediation:
References:
1. http://securityvulns.ru/files/ohh-indirect-privilege-escalation.pdf
CIS Controls:
Version 6
129 | P a g e
Description:
Rationale:
Audit:
Remediation:
References:
1. http://securityvulns.ru/files/ohh-indirect-privilege-escalation.pdf
130 | P a g e
CIS Controls:
Version 6
131 | P a g e
Description:
Rationale:
The DBMS_AQADM_SYS package could allow an unauthorized user to run SQL commands as
user SYS.
Audit:
Remediation:
CIS Controls:
Version 6
132 | P a g e
Description:
Rationale:
The DBMS_STREAMS_RPC package could allow an unauthorized user to run SQL commands as
user SYS.
Audit:
Remediation:
References:
1. http://securityvulns.ru/files/ohh-indirect-privilege-escalation.pdf
133 | P a g e
CIS Controls:
Version 6
134 | P a g e
Description:
Rationale:
Audit:
Remediation:
References:
1. http://securityvulns.ru/files/ohh-indirect-privilege-escalation.pdf
135 | P a g e
CIS Controls:
Version 6
136 | P a g e
Description:
Rationale:
The LTADM package could allow an unauthorized user to run any SQL command as user SYS.
Audit:
Remediation:
References:
1. http://securityvulns.ru/files/ohh-indirect-privilege-escalation.pdf
CIS Controls:
Version 6
137 | P a g e
Description:
Rationale:
The WWV_DBMS_SQL package could allow an unauthorized user to run SQL statements as the
Application Express (APEX) user. The user PUBLIC should not be able to execute
WWV_DBMS_SQL.
Audit:
Remediation:
CIS Controls:
Version 6
138 | P a g e
Description:
Rationale:
Audit:
Remediation:
References:
1. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-1811
139 | P a g e
CIS Controls:
Version 6
140 | P a g e
Description:
Rationale:
The DBMS_IJOB package could allow an attacker to change identities by using a different
username to execute a database job.
Audit:
Remediation:
CIS Controls:
Version 6
141 | P a g e
Description:
The Oracle database DBMS_FILE_TRANSFER package allows a user to transfer files from one
database server to another. The user PUBLIC should not be able to execute
DBMS_FILE_TRANSFER.
Rationale:
The DBMS_FILE_TRANSFER package could allow to transfer files from one database server to
another without authorization to do so.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ARPLS/d_ftran.htm#ARPLS095
142 | P a g e
CIS Controls:
Version 6
143 | P a g e
Description:
The Oracle database SELECT ANY DICTIONARY privilege allows the designated user to access
SYS schema objects. Unauthorized grantees should not have that privilege.
Rationale:
The Oracle password hashes are part of the SYS schema and can be selected using SELECT
ANY DICTIONARY privileges.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#DBSEG99870
2. http://docs.oracle.com/database/121/REFRN/GUID-10024282-6729-4C66-8679-
FD653C9C7DE7.htm#REFRN-GUID-10024282-6729-4C66-8679-FD653C9C7DE7
144 | P a g e
3. http://arup.blogspot.de/2011/07/difference-between-select-any.html
CIS Controls:
Version 6
145 | P a g e
Description:
The Oracle database SELECT ANY TABLE privilege allows the designated user to open any
table, except SYS, to view it. Unauthorized grantees should not have that privilege.
Rationale:
Assignment of the SELECT ANY TABLE privilege can allow the unauthorized viewing of
sensitive data.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/SQLRF/statements_10002.htm#SQLRF0170
2
Notes:
146 | P a g e
CIS Controls:
Version 6
147 | P a g e
Description:
The Oracle database AUDIT SYSTEM privilege allows changes to auditing activities on the
system. Unauthorized grantees should not have that privilege.
Rationale:
The AUDIT SYSTEM privilege can allow the unauthorized alteration of system audit
activities, such as disabling the creation of audit trails.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/SQLRF/statements_4007.htm#SQLRF01107
2. http://docs.oracle.com/database/121/SQLRF/statements_4008.htm#SQLRF56110
148 | P a g e
CIS Controls:
Version 6
149 | P a g e
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. Unauthorized grantees
should not have that keyword assigned to them.
Rationale:
The EXEMPT ACCESS POLICY privilege can allow an unauthorized user to potentially access
and change data.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/audit_config.htm#DBSEG703
2. http://docs.oracle.com/database/121/DBSEG/vpd.htm#CIHEEAFJ
150 | P a g e
CIS Controls:
Version 6
151 | P a g e
Description:
The Oracle database BECOME USER privilege allows the designated user to inherit the rights
of another user. Unauthorized grantees should not have that privilege.
Rationale:
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:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/guidelines.htm#DBSEG499
CIS Controls:
Version 6
152 | P a g e
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. Unauthorized
grantees should not have that privilege.
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/guidelines.htm#DBSEG499
153 | P a g e
CIS Controls:
Version 6
154 | P a g e
Description:
The Oracle database ALTER SYSTEM privilege allows the designated user to dynamically
alter the instance's running operations. Unauthorized grantees should not have that
privilege.
Rationale:
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.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/guidelines.htm#DBSEG499
155 | P a g e
CIS Controls:
Version 6
156 | P a g e
Description:
The Oracle database CREATE ANY LIBRARY privilege allows the designated user to create
objects that are associated to the shared libraries. Unauthorized grantees should not have
that privilege.
Rationale:
The CREATE ANY LIBRARY privilege can allow the creation of numerous library-associated
objects and potentially corrupt the libraries' integrity.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/guidelines.htm#DBSEG499
2. http://docs.oracle.com/database/121/ADMIN/manproc.htm#ADMIN00501
Notes:
Oracle has two identical privileges: CREATE LIBRARY and CREATE ANY LIBRARY.
157 | P a g e
CIS Controls:
Version 6
158 | P a g e
Description:
The Oracle database CREATE LIBRARY privilege allows the designated user to create objects
that are associated to the shared libraries. Unauthorized grantees should not have that
privilege.
Rationale:
The CREATE LIBRARY privilege can allow the creation of numerous library-associated
objects and potentially corrupt the libraries' integrity.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/guidelines.htm#DBSEG499
2. http://docs.oracle.com/database/121/ADMIN/manproc.htm#ADMIN00501
Notes:
Oracle has two identical privileges: CREATE LIBRARY and CREATE ANY LIBRARY.
159 | P a g e
CIS Controls:
Version 6
160 | P a g e
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. Unauthorized grantees should not have that keyword
assigned to them.
Rationale:
The GRANT ANY OBJECT PRIVILEGE capability can allow an unauthorized user to potentially
access or change confidential data, or damage the data catalog due to potential complete
instance access.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#DBSEG99914
161 | P a g e
CIS Controls:
Version 6
162 | P a g e
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. Unauthorized grantees should
not have that keyword assigned to them.
Rationale:
The GRANT ANY ROLE capability can allow an unauthorized user to potentially access or
change confidential data or damage the data catalog due to potential complete instance
access.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#DBSEG99945
163 | P a g e
CIS Controls:
Version 6
164 | P a g e
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. Unauthorized grantees
should not have that privilege.
Rationale:
The GRANT ANY PRIVILEGE capability can allow an unauthorized user to potentially access
or change confidential data or damage the data catalog due to potential complete instance
access.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#DBSEG99945
165 | P a g e
CIS Controls:
Version 6
166 | P a g e
Description:
The Oracle database DELETE_CATALOG_ROLE provides DELETE privileges for the records in
the system's audit table (AUD$). Unauthorized grantees should not have that role.
Rationale:
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#BABFCAFH
167 | P a g e
CIS Controls:
Version 6
168 | P a g e
Description:
Rationale:
Permitting unauthorized access to the SELECT_CATALOG_ROLE can allow the disclosure of all
dictionary data.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#BABFCAFH
CIS Controls:
Version 6
169 | P a g e
170 | P a g e
Description:
Rationale:
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#BABFCAFH
171 | P a g e
CIS Controls:
Version 6
172 | P a g e
Description:
The Oracle database DBA role is the default database administrator role provided for the
allocation of administrative privileges. Unauthorized grantees should not have that role.
Rationale:
Assignment of the DBA role to an ordinary user can provide a great number of unnecessary
privileges to that user and open the door to data breaches, integrity violations, and denial-
of-service conditions.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#DBSEG4414
CIS Controls:
Version 6
173 | P a g e
174 | P a g e
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, and CREATE, and so
forth. (DML changes need trigger-based audit events to record data alterations.)
Unauthorized grantees should not have full access to that table.
Rationale:
Permitting non-privileged users the authorization to manipulate the SYS.AUD$ table can
allow distortion of the audit records, hiding unauthorized activities.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/audit_admin.htm#DBSEG629
175 | P a g e
CIS Controls:
Version 6
176 | 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 a password reuse limit set, e.g., PASSWORD_REUSE_TIME set to other
than UNLIMITED.) Unauthorized grantees should not have full access to that table.
Rationale:
Audit:
Remediation:
References:
1. http://marcel.vandewaters.nl/oracle/database-oracle/password-history-reusing-a-
password
Notes:
177 | P a g e
CIS Controls:
Version 6
178 | P a g e
Description:
The Oracle database SYS.LINK$ table contains all the user's password information and data
table link information. Unauthorized grantees should not have full access to that table.
Rationale:
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.
Audit:
Remediation:
CIS Controls:
Version 6
179 | P a g e
180 | P a g e
Description:
The Oracle database SYS.USER$ table contains the users' hashed password information.
Unauthorized grantees should not have full access to that table.
Rationale:
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.
Audit:
Remediation:
References:
1. http://dba.stackexchange.com/questions/17513/what-do-the-columns-in-sys-
user-represent
181 | P a g e
CIS Controls:
Version 6
182 | P a g e
Description:
The Oracle database DBA_ views show all information which is relevant to administrative
accounts. Unauthorized grantees should not have full access to those views.
Rationale:
Permitting users the authorization to manipulate the DBA_ views can expose sensitive data.
Audit:
Note: An organization should perform proper impact analysis before revoking grants on
DBA_ objects.
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:
183 | P a g e
References:
1. http://docs.oracle.com/database/121/REFRN/GUID-10024282-6729-4C66-8679-
FD653C9C7DE7.htm#REFRN-GUID-10024282-6729-4C66-8679-FD653C9C7DE7
CIS Controls:
Version 6
184 | P a g e
Description:
Rationale:
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/ADMIN/schedadmin.htm#ADMIN12073
2. http://berxblog.blogspot.de/2012/02/restore-dbmsschedulercreatecredential.html
Notes:
185 | P a g e
CIS Controls:
Version 6
186 | P a g e
Description:
The table sys.user$mig is created during migration and contains the Oracle password
hashes before the migration starts. This table should be dropped.
Rationale:
The table sys.user$mig is not deleted after the migration. An attacker could access the
table containing the Oracle password hashes.
Audit:
Remediation:
CIS Controls:
Version 6
187 | P a g e
Description:
The Oracle database ANY keyword provides the user the capability to alter any item in the
catalog of the database. Unauthorized grantees should not have that keyword assigned to
them.
Rationale:
Authorization to use the ANY expansion of a privilege can allow an unauthorized user to
potentially change confidential data or damage the data catalog.
Audit:
Remediation:
188 | P a g e
References:
1. http://docs.oracle.com/database/121/DBSEG/authorization.htm#DBSEG99877
CIS Controls:
Version 6
189 | P a g e
Description:
The Oracle database WITH_ADMIN privilege allows the designated user to grant another user
the same privileges. Unauthorized grantees should not have that privilege.
Rationale:
Assignment of the WITH_ADMIN privilege can allow the granting of a restricted privilege to
an unauthorized user.
Audit:
Remediation:
CIS Controls:
Version 6
190 | P a g e
Description:
Rationale:
A proxy user should only have the ability to connect to the database or based on the needs
of the organization.
Audit:
Remediation:
To remediate this setting execute the following SQL statement for each [PRIVILEGE]
returned (other than CONNECT) by running the audit procedure.
CIS Controls:
Version 6
191 | P a g e
Description:
Rationale:
Audit:
Remediation:
CIS Controls:
Version 6
192 | P a g e
Description:
Rationale:
Audit:
Remediation:
CIS Controls:
Version 6
193 | P a g e
Measures must be taken to protect the audit trail itself, for it may be targeted for alteration
or destruction to hide unauthorized activity. For an audit destination outside the database,
the recommendations are elsewhere in this document. Auditing recommendations for
potential database audit destinations are below.
Auditing "by session" typically creates fewer (until 11g) and slightly smaller audit records,
but is discouraged in most situations since there is some loss of fidelity (e.g. object privilege
GRANTEE). More detailed auditing creates larger audit records. The AUDIT_TRAIL
initialization parameter (for DB|XML, extended - or not) is the main determining factor for
the size of a given audit record - and a notable factor in the performance cost, although the
largest of the latter is DB versus OS or XML.
This section deals with standard Oracle auditing since auditing of privileged connections
(as sysdba or sysoper) is configured via the AUDIT_SYS_OPERATIONS initialization
parameter and is otherwise not configurable. The basic types of standard auditing are
object, statement and privilege auditing, and each behaves differently.
Object auditing applies to specific objects for which it is invoked and always applies to all
users. This type of auditing is usually employed to audit application-specific sensitive
objects, but can also be used to protect the audit trail in the database.
Privilege auditing audits the use of specific system privileges, but typically only if the user
actually possesses the audited privilege. Attempts that fail for lack of the audited privilege
are typically not audited. This is the main weakness of privilege auditing and why
statement auditing is usually preferred, if the option exists.
Statement auditing audits the issuance of certain types of statements, usually without
regard to privilege or lack thereof. Both privilege and statement audits may be specified for
specific users or all users (the default).
194 | P a g e
Description:
The USER object allows for creating accounts that can interact with the database according
to the roles and privileges allotted to the account. It may also own database objects.
Enabling the audit option causes auditing of all activities and requests to create, drop or
alter a user, including a user changing their own password. (The latter is not audited by
audit ALTER USER.)
Rationale:
Any unauthorized attempts to create, drop or alter a user should cause concern, whether
successful or not. Auditing can also be useful in forensics if an account is compromised, and
auditing is mandated by many common security initiatives. An abnormally high number of
these activities in a given period might be worth investigation. Any failed attempt to drop a
user or create a user may be worth further review.
Audit:
Remediation:
AUDIT USER;
195 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
196 | P a g e
Description:
The ROLE object allows for the creation of a set of privileges that can be granted to users or
other roles. Enabling the audit option causes auditing of all attempts, successful or not, to
create, drop, alter or set roles.
Rationale:
Roles are a key database security infrastructure component. Any attempt to create, drop or
alter a role should be audited. This statement auditing option also audits attempts,
successful or not, to set a role in a session. Any unauthorized attempts to create, drop or
alter a role may be worthy of investigation. Attempts to set a role by users without the role
privilege may warrant investigation.
Audit:
Remediation:
AUDIT ROLE;
Notes:
197 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
198 | P a g e
Description:
Enabling the audit option for the SYSTEM GRANT object causes auditing of any attempt,
successful or not, to grant or revoke any system privilege or role, regardless of privilege
held by the user attempting the operation.
Rationale:
Logging of all grant and revokes (roles and system privileges) can provide forensic
evidence about a pattern of suspect/unauthorized activities. Any unauthorized attempt
may be cause for further investigation.
Audit:
Remediation:
CIS Controls:
Version 6
199 | P a g e
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. Enabling the
audit option causes auditing of all attempts, successful or not, to create, drop or alter any
profile.
Rationale:
As profiles are part of the database security infrastructure, auditing the creation,
modification, and deletion of profiles is recommended.
Audit:
Remediation:
AUDIT PROFILE;
Notes:
The statement auditing option audit PROFILE audits everything that the three privilege
audits audit CREATE PROFILE, audit DROP PROFILE and audit ALTER PROFILE do, but also
audits:
1. Attempts to create a profile by a user without the CREATE PROFILE system privilege.
2. Attempts to drop a profile by a user without the DROP PROFILE system privilege
200 | P a g e
3. Attempts to alter a profile by a user without the ALTER PROFILE system privilege.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
201 | P a g e
Description:
Enabling the audit option for the DATABASE LINK object causes all activities on database
links to 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
should be enabled.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/audit_config.htm#DBSEG1115
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
202 | P a g e
203 | P a g e
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. Enabling
the audit option causes all user activities involving the creation, alteration, or dropping of
public links to be audited.
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 enabled.
Audit:
Remediation:
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
204 | P a g e
205 | P a g e
Description:
The PUBLIC SYNONYM object allows for the creation of an alternate description of an object.
Public synonyms are accessible by all users that have the appropriate privileges to the
underlying object. Enabling the audit option causes all user activities involving the creation
or dropping of public synonyms to be audited.
Rationale:
As the logging of user activities involving the creation or dropping of a PUBLIC SYNONYM can
provide forensic evidence about a pattern of unauthorized activities, the audit capability
should be enabled.
Audit:
Remediation:
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
206 | P a g e
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
207 | P a g e
Description:
The SYNONYM operation allows for the creation of 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, or even another synonym.
This synonym puts a dependency on its target and is rendered invalid if the target object is
changed/dropped. Enabling the audit option causes all user activities involving the creation
or dropping of synonyms to be audited.
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 capability
should be enabled.
Audit:
Remediation:
AUDIT SYNONYM;
References:
1. http://docs.oracle.com/database/121/DBSEG/audit_config.htm#DBSEG1115
208 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
209 | P a g e
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. Enabling this audit option causes all user activities involving the creation
or dropping of a directory alias to be audited.
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
should be enabled.
Audit:
Remediation:
AUDIT DIRECTORY;
References:
1. http://docs.oracle.com/database/121/SQLRF/statements_4007.htm#SQLRF01107
210 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
211 | P a g e
Description:
The SELECT ANY DICTIONARY capability allows the user to view the definitions of all schema
objects in the database. Enabling the audit option causes all user activities involving this
capability to be audited.
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 enabled.
Audit:
Remediation:
References:
1. http://docs.oracle.com/database/121/DBSEG/guidelines.htm#DBSEG500
212 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
213 | P a g e
Description:
GRANT ANY OBJECT PRIVILEGE allows the user to grant or revoke any object privilege,
which includes privileges on tables, directories, mining models, etc. Enabling this audit
option causes auditing of all uses of that privilege.
Rationale:
Logging of privilege grants that can lead to the creation, alteration, or deletion of critical
data, the modification of objects, object privilege propagation and other such activities can
be critical to forensic investigations.
Audit:
Remediation:
Notes:
This does NOT audit all attempts to grant or revoke object privileges since this can also be
done by anyone who was granted an object privilege with the grant option. Also, this never
creates an audit record for anyone who does not hold the GRANT ANY OBJECT PRIVILEGE
system privilege. Therefore, many attempts, successful or not, to grant and revoke object
privileges are not audited by this.
214 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
215 | P a g e
Description:
GRANT ANY PRIVILEGE allows a user to grant any system privilege, including the most
powerful privileges typically available only to administrators - to change the security
infrastructure, to drop/add/modify users and more.
Rationale:
Auditing the use of this privilege is part of a comprehensive auditing policy that can help in
detecting issues and can be useful in forensics.
Audit:
Remediation:
Notes:
This does NOT audit all attempts to grant or revoke system privileges since this can also be
done by anyone who was granted a system privilege with the admin option. Also, this never
creates an audit record for anyone who does not hold the GRANT ANY PRIVILEGE system
privilege. Thus, many attempts, successful or not, to grant and revoke system privileges are
not audited by this.
216 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
217 | P a g e
Description:
The AUDIT DROP ANY PROCEDURE command is auditing the dropping of procedures.
Enabling the option causes auditing of all such activities.
Rationale:
Dropping procedures of another user could be part of a privilege escalation exploit and
should be audited.
Audit:
Remediation:
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
218 | P a g e
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
219 | 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. Enabling the audit option will cause these
activities to be audited.
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 enabled.
Audit:
Remediation:
220 | P a g e
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
221 | P a g e
Description:
In this statement audit, PROCEDURE means any procedure, function, package or library.
Enabling this audit option causes any attempt, successful or not, to create or drop any of
these types of objects to be audited, regardless of privilege or lack thereof. Java schema
objects (sources, classes, and resources) are considered the same as procedures for the
purposes of auditing SQL statements.
Rationale:
Any unauthorized attempts to create or drop a procedure in another's schema should cause
concern, whether successful or not. Changes to critical stored code can dramatically change
the behavior of the application and produce serious security consequences, including
enabling privilege escalation and introducing SQL injection vulnerabilities. Audit records of
such changes can be helpful in forensics.
Audit:
Remediation:
AUDIT PROCEDURE;"
Notes:
Not all auditing options work alike. In particular, the statement auditing option audit
PROCEDURE does indeed audit create and drop library as well as all types of procedures and
222 | P a g e
java schema objects. However, privilege audits do not work this way. So, for example, none
of audit CREATE ANY PROCEDURE, audit DROP ANY PROCEDURE, or audit CREATE
PROCEDURE will audit create or drop library activities. In statement auditing, PROCEDURE has
a larger scope than in privilege auditing, where it is specific to functions, packages and
procedures, but excludes libraries and perhaps other object types.
Audit PROCEDURE does not audit altering procedures, either in your own schema or in
another via the ALTER ANY PROCEDURE system privilege. There seems to be no statement
audit that is a better replacement for Audit ALTER ANY PROCEDURE, but beware that will
not create any audit records for users that do not have the privilege. Thus, attempts to alter
procedures in one's own schema are never audited, and attempts to alter procedures in
another's schema that fail for lack of the ALTER ANY PROCEDURE privilege are not audited.
This is simply a weakness in the current state of Oracle auditing. Fortunately, though, all
that the ALTER command can be used for regarding procedures, functions, packages and
libraries is compile options, so the inability to comprehensively audit alter procedure
activities and requests is not as bad as it would be for other object types (USER, PROFILE,
etc.)
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
223 | P a g e
Description:
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. Enabling the audit option will audit
all attempts to perform ALTER SYSTEM, whether successful or not and regardless of whether
or not the ALTER SYSTEM privilege is held by the user attempting the action.
Rationale:
Any unauthorized attempt to alter the system should be cause for concern. Alterations
outside of some specified maintenance window may be of concern. In forensics, these audit
records could be quite useful.
Audit:
Remediation:
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
224 | P a g e
225 | P a g e
Description:
A TRIGGER may be used to modify DML actions or invoke other (recursive) actions when
some types of user-initiated actions occur. Enabling this audit option will cause auditing of
any attempt, successful or not, to create, drop, enable or disable any schema trigger in any
schema regardless of privilege or lack thereof. For enabling and disabling a trigger, it
covers both ALTER TRIGGER and ALTER TABLE.
Rationale:
Triggers are often part of schema security, data validation and other critical constraints
upon actions and data. A trigger in another schema may be used to escalate privileges,
redirect operations, transform data and perform other sorts of perhaps undesired actions.
Any unauthorized attempt to create, drop or alter a trigger in another schema may be cause
for investigation.
Audit:
Remediation:
AUDIT TRIGGER;
Notes:
There is no current CIS recommendation to audit the use of the system privilege CREATE
TRIGGER, as there is for CREATE SYNONYM, CREATE PROCEDURE and some other types of
226 | P a g e
objects, so this is actually a scope escalation also - to audit such actions in one's own
schema. However, this is the only way to comprehensively audit things like attempts to
create, drop or alter triggers in another's schema if the user attempting to operation does
not hold the required ANY privilege - and these are exactly the sorts of things that should
raise a large red flag.
The statement auditing option audit TRIGGER audits almost everything that the three
privilege audits audit CREATE ANY TRIGGER, audit ALTER ANY TRIGGER and audit DROP
ANY TRIGGER do, but also audits:
1. Statements to create, drop, enable or disable a trigger in the user's own schema.
2. Attempts to create a trigger by a user without the CREATE TRIGGER system privilege.
3. Attempts to create a trigger in another schema by users without the CREATE ANY
TRIGGER privilege.
4. Attempts to drop a trigger in another schema by users without the DROP ANY
TRIGGER privilege.
5. Attempts to disable or enable a trigger in another schema by users without the
ALTER ANY TRIGGER privilege.
The one thing is audited by any of the three privilege audits that is not audited by this is
ALTER TRIGGER ...COMPILE if the trigger is in another's schema, which is audited by audit
ALTER ANY TRIGGER, but only if the user attempting the alteration actually holds the ALTER
ANY TRIGGER system privilege. Audit TRIGGER only audits ALTER TABLE or ALTER TRIGGER
statements used to enable or disable triggers. It does not audit ALTER TRIGGER or ALTER
TABLE statements used only with compile options.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
227 | P a g e
Description:
Enabling this audit option will cause auditing of all attempts to connect to the database,
whether successful or not, as well as audit session disconnects/logoffs. The commands to
audit SESSION, CONNECT or CREATE SESSION all accomplish the same thing - they initiate
statement auditing of the connect statement used to create a database session.
Rationale:
Auditing attempts to connect to the database is basic and mandated by most security
initiatives. Any attempt to logon to a locked account, failed attempts to logon to default
accounts or an unusually high number of failed logon attempts of any sort, for any user, in a
particular time period may indicate an intrusion attempt. In forensics, the logon record
may be first in a chain of evidence and contain information found in no other type of audit
record for the session. Logon and logoff in the audit trail define the period and duration of
the session.
Audit:
Remediation:
AUDIT SESSION;
228 | P a g e
Notes:
Although listed in the documentation as a privilege audit, audit CREATE SESSION actually
audits the CONNECT statement. This is evidenced by the undocumented audit CONNECT
which has the same result as audit SESSION or audit CREATE SESSION. There is no system
privilege named either SESSION or CONNECT (CONNECT is a role, not a system privilege). Also,
it behaves as statement auditing rather than privilege auditing in that it audits all attempts
to create a session, even if the user does not hold the CREATE SESSION system privilege.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
229 | P a g e
Description:
The CREATE USER statement is used to create Oracle database accounts and assign database
properties to them. Enabling this unified action audit causes logging of all CREATE USER
statements, whether successful or unsuccessful, issued by the users regardless of the
privileges held by the users to issue such statements.
Rationale:
Logging and monitoring of all attempts to create user accounts, whether successful or
unsuccessful, may provide clues and forensic evidences about potential
suspicious/unauthorized activities. Any such activities may be a cause for further
investigation. In addition, organization security policies and industry/government
regulations may require logging of all activities involving CREATE USER.
Audit:
230 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
231 | P a g e
Description:
The ALTER USER statement is used to change database users’ password, lock accounts, and
expire passwords. In addition, this statement is used to change database properties of user
accounts such as database profiles, default and temporary tablespaces, and tablespace
quotas. This unified audit action enables logging of all ALTER USER statements, whether
successful or unsuccessful, issued by the users regardless of the privileges held by the users
to issue such statements.
Rationale:
Logging and monitoring of all attempts to alter user accounts, whether successful or
unsuccessful, may provide clues and forensic evidences about potential
suspicious/unauthorized activities. Any such activities may be a cause for further
investigation. In addition, organization security policies and industry/government
regulations may require logging of all activities involving ALTER USER.
Audit:
Remediation:
232 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
233 | P a g e
Description:
The DROP USER statement is used to drop Oracle database accounts and schemas associated
with them. Enabling this unified action audit enables logging of all DROP USER statements,
whether successful or unsuccessful, issued by the users regardless of the privileges held by
the users to issue such statements.
Rationale:
Logging and monitoring of all attempts to drop user, whether successful or unsuccessful,
may provide clues and forensic evidence about potential suspicious/unauthorized
activities. Any such activities may be a cause for further investigation. In addition,
organization security policies and industry/government regulations may require logging of
all activities involving DROP USER.
Audit:
Remediation:
234 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
235 | P a g e
Description:
An Oracle database role is a collection or set of privileges that can be granted to users or
other roles. Roles may include system privileges, object privileges or other roles. Enabling
this unified audit action enables logging of all CREATE ROLE statements, whether successful
or unsuccessful, issued by the users regardless of the privileges held by the users to issue
such statements.
Rationale:
Logging and monitoring of all attempts to create roles, whether successful or unsuccessful,
may provide clues and forensic evidence about potential suspicious/unauthorized
activities. Any such activities may be a cause for further investigation. In addition,
organization security policies and industry/government regulations may require logging of
all user activities involving CREATE ROLE.
Audit:
Remediation:
236 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
237 | P a g e
Description:
An Oracle database role is a collection or set of privileges that can be granted to users or
other roles. Roles may include system privileges, object privileges or other roles. The ALTER
ROLE statement is used to change the authorization needed to enable a role. Enabling this
unified action audit causes logging of all ALTER ROLE statements, whether successful or
unsuccessful, issued by the users regardless of the privileges held by the users to issue such
statements.
Rationale:
Logging and monitoring of all attempts to alter roles, whether successful or unsuccessful,
may provide clues and forensic evidence about potential suspicious/unauthorized
activities. Any such activities may be a cause for further investigation. In addition,
organization security policies and industry/government regulations may require logging of
all user activities involving alteration of roles.
Audit:
Remediation:
238 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
239 | P a g e
Description:
An Oracle database role is a collection or set of privileges that can be granted to users or
other roles. Roles may include system privileges, object privileges or other roles. Enabling
this unified audit action enables logging of all DROP ROLE statements, successful or
unsuccessful, issued by the users regardless of the privileges held by the users to issue such
statements.
Rationale:
Logging and monitoring of all attempts to drop roles, whether successful or unsuccessful,
may provide clues and forensic evidence about potential suspicious/unauthorized
activities. Any such activities may be a cause for further investigation. In addition,
organization security policies and industry/government regulations may require logging of
all user activities involving DROP ROLE.
Audit:
Remediation:
240 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
241 | P a g e
Description:
GRANT statements are used to grant privileges to Oracle database users and roles, including
the most powerful privileges and roles typically available to the database administrators.
Enabling this unified action audit enables logging of all GRANT statements, whether
successful or unsuccessful, issued by the users regardless of the privileges held by the users
to issue such statements.
Rationale:
With unauthorized grants and permissions, a malicious user may be able to change the
security of the database, access/update confidential data, or compromise the integrity of
the database. Logging and monitoring of all attempts to grant system privileges, object
privileges or roles, whether successful or unsuccessful, may provide forensic evidence
about potential suspicious/unauthorized activities as well as privilege escalation activities.
Any such activities may be a cause for further investigation. In addition, organization
security policies and industry/government regulations may require logging of all user
activities involving GRANT.
Audit:
Remediation:
242 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
243 | P a g e
Description:
REVOKE statements are used to revoke privileges from Oracle database users and roles.
Enabling this unified action audit enables logging of all REVOKE statements, successful or
unsuccessful, issued by the users regardless of the privileges held by the users to issue such
statements.
Rationale:
Logging and monitoring of all attempts to revoke system privileges, object privileges or
roles, whether successful or unsuccessful, may provide clues and forensic evidence about
potential suspicious/unauthorized activities. Any such activities may be a cause for further
investigation. In addition, organization security policies and industry/government
regulations may require logging of all user activities involving REVOKE.
Audit:
Remediation:
244 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
245 | P a g e
Description:
Oracle database profiles are used to enforce resource usage limits and implement
password policies such as password complexity rules and reuse restrictions. Enabling this
unified action audit enables logging of all CREATE PROFILE statements, whether successful
or unsuccessful, issued by the users regardless of the privileges held by the users to issue
such statements.
Rationale:
Audit:
Remediation:
246 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
247 | P a g e
Description:
Oracle database profiles are used to enforce resource usage limits and implement
password policies such as password complexity rules and reuse restrictions. Enabling this
unified action audit enables logging of all ALTER PROFILE statements, whether successful or
unsuccessful, issued by the users regardless of the privileges held by the users to issue such
statements.
Rationale:
Logging and monitoring of all attempts to alter profiles, whether successful or unsuccessful,
may provide forensic evidence about potential suspicious/unauthorized activities. Any
such activities may be a cause for further investigation. In addition, organization security
policies and industry/government regulations may require logging of all user activities
involving alteration of database profiles.
Audit:
Remediation:
248 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
249 | P a g e
Description:
Oracle database profiles are used to enforce resource usage limits and implement
password policies such as password complexity rules and reuse restrictions. Enabling this
unified action audit enables logging of all DROP PROFILE statements, whether successful or
unsuccessful, issued by the users regardless of the privileges held by the users to issue such
statements.
Rationale:
Audit:
Remediation:
250 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
251 | P a g e
Description:
Rationale:
Logging and monitoring of all attempts to create database links, whether successful or
unsuccessful, may provide forensic evidence about potential suspicious/unauthorized
activities. Any such activities may be a cause for further investigation. In addition,
organization security policies and industry/government regulations may require logging of
all user activities involving creation of database links.
Audit:
252 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
253 | P a g e
Description:
Rationale:
Logging and monitoring of all attempts to alter database links, whether successful or
unsuccessful, may provide forensic evidence about potential suspicious/unauthorized
activities. Any such activities may be a cause for further investigation. In addition,
organization security policies and industry/government regulations may require logging of
all user activities involving alteration of database links.
Audit:
254 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
255 | P a g e
Description:
Rationale:
Logging and monitoring of all attempts to drop database links, whether successful or
unsuccessful, may provide forensic evidence about potential suspicious/unauthorized
activities. Any such activities may be a cause for further investigation. In addition,
organization security policies and industry/government regulations may require logging of
all user activities involving dropping database links.
Audit:
256 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
257 | P a g e
Description:
An Oracle database synonym is used to create an alternative name for a database object
such as table, view, procedure, java object or even another synonym, etc. Enabling this
unified action audit causes logging of all CREATE SYNONYM and CREATE PUBLIC SYNONYM
statements, whether successful or unsuccessful, issued by the users regardless of the
privileges held by the users to issue such statements.
Rationale:
Audit:
Remediation:
258 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
259 | P a g e
Description:
An Oracle database synonym is used to create an alternative name for a database object
such as table, view, procedure, or java object, or even another synonym. Enabling this
unified action audit causes logging of all ALTER SYNONYM and ALTER PUBLIC SYNONYM
statements, whether successful or unsuccessful, issued by the users regardless of the
privileges held by the users to issue such statements.
Rationale:
Audit:
Remediation:
260 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
261 | P a g e
Description:
An Oracle database synonym is used to create an alternative name for a database object
such as table, view, procedure, or java object, or even another synonym. Enabling his
unified action audit causes logging of all DROP SYNONYM and DROP PUBLIC SYNONYM
statements, whether successful or unsuccessful, issued by the users regardless of the
privileges held by the users to issue such statements.
Rationale:
Audit:
Remediation:
262 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
263 | P a g e
Description:
The SELECT ANY DICTIONARY system privilege allows the user to view the definition of all
schema objects in the database. It grants SELECT privileges on the data dictionary objects to
the grantees, including SELECT on DBA_ views, V$ views, X$ views and underlying SYS tables
such as TAB$ and OBJ$. This privilege also allows grantees to create stored objects such as
procedures, packages and views on the underlying data dictionary objects. Please note that
this privilege does not grant SELECT on tables with password hashes such as USER$,
DEFAULT_PWD$, LINK$, and USER_HISTORY$. Enabling this audit causes logging of activities
that exercise this privilege.
Rationale:
Logging and monitoring of all attempts to access a data dictionary, whether successful or
unsuccessful, may provide clues and forensic evidence about potential
suspicious/unauthorized activities. Any such activities may be a cause for further
investigation. In addition, organization security policies and industry/government
regulations may require logging of all user activities involving access to the database.
Audit:
264 | P a g e
Remediation:
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
265 | P a g e
Description:
The UNIFIED_AUDIT_TRAIL view holds audit trail records generated by the database.
Enabling this audit action causes logging of all access attempts to the UNIFIED_AUDIT_TRAIL
view, whether successful or unsuccessful, regardless of the privileges held by the users to
issue such statements.
Rationale:
Logging and monitoring of all attempts to access the UNIFIED_AUDIT_TRAIL view, whether
successful or unsuccessful, may provide clues and forensic evidence about potential
suspicious/unauthorized activities. Any such activities may be a cause for further
investigation. In addition, organization security policies and industry/government
regulations may require logging of all user activities involving access to this view.
Audit:
266 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
267 | P a g e
Description:
Oracle database procedures, function, packages, and package bodies, which are stored
within the database, are created to perform business functions and access database as
defined by PL/SQL code and SQL statements contained within these objects. Enabling this
unified action audit causes logging of all CREATE PROCEDURE, CREATE FUNCTION, CREATE
PACKAGE and CREATE PACKAGE BODY statements, successful or unsuccessful, statements
issued by the users regardless of the privileges held by the users to issue such statements.
Rationale:
Audit:
268 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
269 | P a g e
Description:
Oracle database procedures, functions, packages, and package bodies, which are stored
within the database, are created to carry out business functions and access database as
defined by PL/SQL code and SQL statements contained within these objects. Enabling this
unified action audit causes logging of all ALTER PROCEDURE, ALTER FUNCTION, ALTER
PACKAGE and ALTER PACKAGE BODY statements, successful or unsuccessful, issued by the
users regardless of the privileges held by the users to issue such statements.
Rationale:
Audit:
270 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
271 | P a g e
Description:
Oracle database procedures, functions, packages, and package bodies, which are stored
within the database, are created to carry out business functions and access database as
defined by PL/SQL code and SQL statements contained within these objects. Enabling this
unified action audit causes logging of all DROP PROCEDURE, DROP FUNCTION, DROP PACKAGE or
DROP PACKAGE BODY statements, successful or unsuccessful, issued by the users regardless
of the privileges held by the users to issue such statements.
Rationale:
Audit:
272 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
273 | P a g e
Description:
The ALTER SYSTEM privilege allows the user to change instance settings which could impact
security posture, performance or normal operation of the database. Additionally, the ALTER
SYSTEM privilege may be used to run operating system commands using undocumented
Oracle functionality. Enabling this unified audit causes logging of activities that involve
exercise of this privilege, whether successful or unsuccessful, issued by the users
regardless of the privileges held by the users to issue such statements.
Rationale:
Logging and monitoring of all attempts to execute ALTER SYSTEM statements, whether
successful or unsuccessful, may provide forensic evidence about potential
suspicious/unauthorized activities. Any such activities may be a cause for further
investigation. In addition, organization security policies and industry/government
regulations may require logging of all user activities that involve ALTER SYSTEM statements.
Audit:
Remediation:
274 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
275 | P a g e
Description:
Oracle database triggers are executed automatically when specified conditions on the
underlying objects occur. Trigger bodies contain the code, quite often to perform data
validation, ensure data integrity/security or enforce critical constraints on allowable
actions on data. Enabling this unified audit causes logging of all CREATE TRIGGER
statements, whether successful or unsuccessful, issued by the users regardless of the
privileges held by the users to issue such statements.
Rationale:
Audit:
Remediation:
276 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
277 | P a g e
Description:
Oracle database triggers are executed automatically when specified conditions on the
underlying objects occur. Trigger bodies contain the code, quite often to perform data
validation, ensure data integrity/security or enforce critical constraints on allowable
actions on data. Enabling this unified audit causes logging of all ALTER TRIGGER statements,
whether successful or unsuccessful, issued by the users regardless of the privileges held by
the users to issue such statements.
Rationale:
Audit:
278 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
279 | P a g e
Description:
Oracle database triggers are executed automatically when specified conditions on the
underlying objects occur. Trigger bodies contain the code, quite often to perform data
validation, ensure data integrity/security or enforce critical constraints on allowable
actions on data. Enabling this unified audit causes logging of all DROP TRIGGER statements,
whether successful or unsuccessful, issued by the users regardless of the privileges held by
the users to issue such statements.
Rationale:
Audit:
Remediation:
280 | P a g e
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
281 | P a g e
Description:
Oracle database users log on to the database to perform their work. Enabling this unified
audit causes logging of all LOGON actions, whether successful or unsuccessful, issued by the
users regardless of the privileges held by the users to log into the database. In addition,
LOGOFF action audit captures logoff activities. This audit action also captures logon/logoff to
the open database by SYSDBA and SYSOPER.
Rationale:
Logging and monitoring of all attempts to logon to the database, whether successful or
unsuccessful, may provide forensic evidence about potential suspicious/unauthorized
activities. Any such activities may be a cause for further investigation. In addition,
organization security policies and industry/government regulations may require logging of
all user activities involving LOGON and LOGOFF.
Audit:
282 | P a g e
Remediation:
Note: If you do not have CIS_UNIFIED_AUDIT_POLICY, please create one using the CREATE
AUDIT POLICY statement.
CIS Controls:
Version 6
6.2 Ensure Audit Log Settings Support Appropriate Log Entry Formatting
Validate audit log settings for each hardware device and the software installed on it,
ensuring that logs include a date, timestamp, source addresses, destination
addresses, and various other useful elements of each packet and/or transaction.
Systems should record logs in a standardized format such as syslog entries or those
outlined by the Common Event Expression initiative. If systems cannot generate logs
in a standardized format, log normalization tools can be deployed to convert logs
into such a format.
283 | P a g e
The recommendations expressed in this document assume the presence of a role named
CISSCANROLE and a user named CISSCAN. This role and user should be created by executing
the following SQL statements, being careful to substitute an appropriate password for
<password>.
If you rely on similar roles and/or users, but they are not named CISSCANROLE or CISSCAN,
or if you have roles or users named CISSCANROLE or CISSCAN intended to be used for
different purposes, be aware that some recommendations herein explicitly name
CISSCANROLE and CISSCAN.
These are:
Note: Different organizations may wish to follow the instructions in this appendix in
different ways. For more permanent or regular assessment scans, it may be acceptable to
retain the CISSCANROLE and CISSCAN user indefinitely. However, in a consultative context
where an assessment is perhaps run at the outset of the consulting engagement and again
284 | P a g e
closer to the end, after any remediation has been performed, the CISSCANROLE role and
CISSCAN user may be dropped. Such a decision is ultimately left up to the implementing
organization.
285 | P a g e
286 | P a g e
287 | P a g e
288 | P a g e
289 | P a g e
290 | P a g e
291 | P a g e
292 | P a g e
Apr 29, 2015 1.1.0 Ticket #216: Updated remediation to reference [PRIVILEGE]
list
Apr 30, 2015 1.1.0 Ticket #204: Clarification in overview for benchmark non-
pluggable applicability
Jun 29, 2015 1.1.0 Ticket #209: Add workflow advice to appendix about scan user
Jun 29, 2015 1.1.0 Ticket #217: Corrected type of "repact" with "repcat"
Jun 29, 2015 1.1.0 Ticket #213: Updated audit query for regex on APEX users
Jun 29, 2015 1.1.0 Ticket #212: Corrected confusion between DBMS_RANDOM
and DBMS_BACKUP_RESTORE
Jun 29, 2015 1.1.0 Ticket #211: Corrected incorrect recommendation from
'FALSE' to 'TRUE'
Jun 29, 2015 1.1.0 Ticket #203: Updated references from 11g R2 to 12c where
possible
Mar 31, 2016 1.2.0 Ticket #259: Added SYSMAN to list of authorized grantees for
4.4.2
Mar 31, 2016 1.2.0 Ticket #256: Added SYSBACKUP and SYSDG to grantee list for
4.3.1
Mar 31, 2016 1.2.0 Ticket #254: Updated recommendation text to say 'Less than
or Equal to 10' on 2.13
293 | P a g e
Mar 31, 2016 1.2.0 Ticket #241: Added missing semicolon in audit query on 5.1
Mar 31, 2016 1.2.0 Ticket #253: Removed quotes from remediation command on
2.2.2
Mar 31, 2016 1.2.0 Ticket #261: Added SYS to table owners and SYSMAN to list of
authorized grantees for 4.5.4
Mar 31, 2016 1.2.0 Ticket #263: Added SYS to list of table owners
Mar 31, 2016 1.2.0 Ticket #225: Updated description and rationale for 2.2.17
Mar 31, 2016 1.2.0 Ticket #215: Revised LISTENER sections and included
LISTENER_HOME references
Mar 31, 2016 1.2.0 Ticket #242: Added missing semicolon to 4.1.4
Mar 31, 2016 1.2.0 Ticket #266: Updated audit query to check for all privileges,
not only roles
Mar 31, 2016 1.2.0 Ticket #265: Added APEX_050000 to list of authorized
grantees on 4.7
Mar 31, 2016 1.2.0 Ticket #252: Update profile text (minor)
Apr 1, 2016 2.0.0 Ticket #267: Added a caution statement about revoking
privileges from PUBLIC.
Oct 18, 2016 2.0.0 Ticket #207: Moved existing auditing recommendations to a
subsection named Traditional Auditing (5.1) and added unified
auditing recommendations under a sibling subsection called
Unified Auditing (5.2).
Oct 18, 2016 2.0.0 Ticket #275: Corrected reference included for 2.2.2
294 | P a g e
Oct 18, 2016 2.0.0 Ticket #276: Added ‘DB’ and ‘XML’ as valid parameter values
for 2.2.2
Dec 1, 2016 2.0.0 Ticket #262: Updated Grantee list and added a not regarding
PUBLIC grants for 4.5.5
Dec 1, 2016 2.0.0 Ticket #282: Corrected typo in 2.2.11 where it specified
UTIL_FILE_DIR instead of UTL_FILE_DIR
Dec 1, 2016 2.0.0 Ticket #284: Added “and OWNER=’SYS’” to the query for 4.5.2
Dec 1, 2016 2.0.0 Ticket #285: Added “and OWNER=’SYS’” to the query for 4.5.3
Dec 1, 2016 2.0.0 Ticket #286: Added “and OWNER=’SYS’” to the query for 4.5.4
Dec 1, 2016 2.0.0 Ticket #287: Added “and OWNER=’SYS’” to the query for 4.5.6
Jan 18, 2017 2.1.0 Ticket #3934: #292 4.3.12 - Typo in audit procedure
Jun 22, 2017 2.1.0 Ticket #3937: #295 Remove "Level 1 - RDBMS using Unified
Auditing" from 2.2.1
Sep 14, 2017 2.1.0 Ticket #3938: #296 1.2 Ensure All Default Passwords Are
Changed (Scored) - Add comment
Sep 14, 2017 2.1.0 Ticket #3936: #294 Title of 2.2.2 is inconsistent
Sep 14, 2017 2.1.0 Ticket #3935: #293 Change upper(value) from audit SQL
query to value
Sep 28, 2017 2.1.0 Ticket #3932: #290 Revise profile descriptions to remove any
ambiguity
295 | P a g e
Feb 1, 2018 2.1.0 Ticket #3928: #247 Revoke dangerous public privileges
Feb 1, 2018 2.1.0 Ticket #3930: #250 Check for latest Patch Update using new
naming format
Jul 10, 2018 2.1.0 Edited to the entire benchmark to address errors and clarify
recommendations
296 | P a g e