UCF STIG Viewer Logo

Oracle Database 11.2g Security Technical Implementation Guide


Overview

Date Finding Count (142)
2021-04-05 CAT I (High): 11 CAT II (Med): 129 CAT III (Low): 2
STIG Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Available Profiles



Findings (MAC III - Administrative Sensitive)

Finding ID Severity Title
V-219710 High The Oracle Listener must be configured to require administration authentication.
V-219787 High Applications must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
V-219788 High When using command-line tools such as Oracle SQL*Plus, which can accept a plain-text password, users must use an alternative login method that does not expose the password.
V-238458 High The DBMS must use multifactor authentication for access to user accounts.
V-219747 High The DBMS, when using PKI-based authentication, must enforce authorized access to the corresponding private key.
V-238434 High The DBMS must employ cryptographic mechanisms preventing the unauthorized disclosure of information during transmission unless the transmitted data is otherwise protected by alternative physical measures.
V-238433 High DBMS default accounts must be assigned custom passwords.
V-238432 High Vendor-supported software must be evaluated and patched against newly found vulnerabilities.
V-238431 High DBA OS accounts must be granted only those host system privileges necessary for the administration of the DBMS.
V-219702 High The Oracle REMOTE_OS_AUTHENT parameter must be set to FALSE.
V-219703 High The Oracle REMOTE_OS_ROLES parameter must be set to FALSE.
V-219719 Medium Only authorized system accounts must have the SYSTEM tablespace specified as the default tablespace.
V-219713 Medium Connections by mid-tier web and application systems to the Oracle DBMS from a DMZ or external network must be encrypted.
V-219712 Medium Oracle application administration roles must be disabled if not required and authorized.
V-219711 Medium Application role permissions must not be assigned to the Oracle PUBLIC role.
V-219716 Medium Sensitive information from production database exports must be modified before being imported into a development database.
V-219715 Medium Unauthorized database links must not be defined and active.
V-219714 Medium Database job/batch queues must be reviewed regularly to detect unauthorized database job submissions.
V-219754 Medium The DBMS must produce audit records containing sufficient information to establish what type of events occurred.
V-238448 Medium The DBMS must specify an account lockout duration that is greater than or equal to the organization-approved minimum.
V-238449 Medium The DBMS must have the capability to limit the number of failed login attempts based upon an organization-defined number of consecutive invalid attempts occurring within an organization-defined time period.
V-238446 Medium The DBA role must not be assigned excessive or unauthorized privileges.
V-238447 Medium OS accounts utilized to run external procedures called by the DBMS must have limited privileges.
V-238444 Medium Administrative privileges must be assigned to database accounts via database roles.
V-238445 Medium Administrators must utilize a separate, distinct administrative account when performing administrative activities, accessing database security functions, or accessing security-relevant information.
V-238442 Medium The DBMS must be protected from unauthorized access by developers on shared production/development host systems.
V-238443 Medium The DBMS must restrict access to system tables and other configuration information or metadata to DBAs or other authorized users.
V-238440 Medium A single database connection configuration file must not be used to configure all database clients.
V-238441 Medium The DBMS must be protected from unauthorized access by developers.
V-219780 Medium The DBMS must preserve any organization-defined system state information in the event of a system failure.
V-219781 Medium The DBMS must take needed steps to protect data at rest and ensure confidentiality and integrity of application data.
V-219782 Medium The DBMS must isolate security functions from non-security functions by means of separate security domains.
V-219783 Medium The DBMS must prevent unauthorized and unintended information transfer via shared system resources.
V-219784 Medium The DBMS must check the validity of data inputs.
V-219785 Medium The DBMS must only generate error messages that provide information necessary for corrective actions without revealing organization-defined sensitive or potentially harmful information in error logs and administrative messages that could be exploited.
V-219786 Medium The DBMS must restrict error messages, so only authorized personnel may view them.
V-219789 Medium Disk space used by audit trail(s) must be monitored; audit records must be regularly or continuously offloaded to a centralized log management system.
V-219724 Medium DBMS production application and data directories must be protected from developers on shared production/development DBMS host systems.
V-219725 Medium Use of the DBMS installation account must be logged.
V-219722 Medium The Oracle _TRACE_FILES_PUBLIC parameter if present must be set to FALSE.
V-219723 Medium Application object owner accounts must be disabled when not performing installation or maintenance actions.
V-219720 Medium Application owner accounts must have a dedicated application tablespace.
V-219721 Medium The directories assigned to the LOG_ARCHIVE_DEST* parameters must be protected from unauthorized access.
V-238451 Medium A DBMS utilizing Discretionary Access Control (DAC) must enforce a policy that includes or excludes access to the granularity of a single user.
V-238450 Medium Databases utilizing Discretionary Access Control (DAC) must enforce a policy that limits propagation of access rights.
V-238453 Medium The DBMS must provide a real-time alert when organization-defined audit failure events occur.
V-238452 Medium The DBMS itself, or the logging or alerting mechanism the application utilizes, must provide a warning when allocated audit record storage volume reaches an organization-defined percentage of maximum audit record storage capacity.
V-238455 Medium Database backup procedures must be defined, documented, and implemented.
V-238454 Medium The DBMS must support enforcement of logical access restrictions associated with changes to the DBMS configuration and to the database itself.
V-238457 Medium DBMS backup and restoration files must be protected from unauthorized access.
V-238456 Medium Database recovery procedures must be developed, documented, implemented, and periodically tested.
V-238459 Medium The DBMS must ensure users are authenticated with an individual authenticator prior to using a group authenticator.
V-219793 Medium Database software directories, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.
V-219792 Medium The DBMS software installation account must be restricted to authorized users.
V-219791 Medium Logic modules within the database (to include packages, procedures, functions and triggers) must be monitored to discover unauthorized changes.
V-219790 Medium Database software, applications, and configuration files must be monitored to discover unauthorized changes.
V-219796 Medium The DBMS must separate user functionality (including user interface services) from database management functionality.
V-219795 Medium The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
V-219794 Medium The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
V-219733 Medium The directory assigned to the AUDIT_FILE_DEST parameter must be protected from unauthorized access and must be stored in a dedicated directory or disk partition separate from software or other application files.
V-237753 Medium Oracle database products must be a version supported by the vendor.
V-219737 Medium Replication accounts must not be granted DBA privileges.
V-219736 Medium Access to DBMS software files and directories must not be granted to unauthorized users.
V-219739 Medium Changes to configuration options must be audited.
V-219738 Medium Network access to the DBMS must be restricted to authorized personnel.
V-219744 Medium The /diag subdirectory under the directory assigned to the DIAGNOSTIC_DEST parameter must be protected from unauthorized access.
V-219745 Medium Remote administration must be disabled for the Oracle connection manager.
V-219746 Medium The SQLNet SQLNET.ALLOWED_LOGON_VERSION parameter must be set to a value of 12 or higher.
V-219742 Medium Changes to DBMS security labels must be audited.
V-219743 Medium Remote database or other external access must use fully-qualified names.
V-219748 Medium The DBMS must limit the number of concurrent sessions for each system account to an organization-defined number of sessions.
V-219749 Medium The system must employ automated mechanisms for supporting Oracle user account management.
V-238437 Medium The DBMS must provide a mechanism to automatically terminate accounts designated as temporary or emergency accounts after an organization-defined time period.
V-238436 Medium The DBMS must provide a mechanism to automatically identify accounts designated as temporary or emergency accounts.
V-238435 Medium The DBMS must support the disabling of network protocols deemed by the organization to be non-secure.
V-219755 Medium The DBMS must produce audit records containing sufficient information to establish when (date and time) the events occurred.
V-238439 Medium The DBMS must restrict grants to sensitive information to authorized user roles.
V-238438 Medium The DBMS must enforce Discretionary Access Control (DAC) policy allowing users to specify and control sharing by named individuals, groups of individuals, or by both, limiting propagation of access rights and includes or excludes access to the granularity of a single user.
V-219757 Medium The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events.
V-219756 Medium The DBMS must produce audit records containing sufficient information to establish where the events occurred.
V-238480 Medium Use of the DBMS software installation account must be restricted.
V-238481 Medium The OS must limit privileges to change the DBMS software resident within software libraries (including privileged programs).
V-219753 Medium The DBMS must generate audit records for the DoD-selected list of auditable events, to the extent such information is available.
V-219752 Medium The DBMS must allow designated organizational personnel to select which auditable events are to be audited by the database.
V-219751 Medium The DBMS must provide audit record generation capability for organization-defined auditable events within the database.
V-219750 Medium The DBMS must enforce approved authorizations for logical access to the system in accordance with applicable policy.
V-219759 Medium The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
V-219758 Medium The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
V-219696 Medium Oracle instance names must not contain Oracle version numbers.
V-219697 Medium Fixed user and public database links must be authorized for use.
V-219695 Medium Access to default accounts used to support replication must be restricted to authorized DBAs.
V-219699 Medium A minimum of two Oracle redo log groups/files must be defined and configured to be stored on separate, archived physical disks or archived directories on a RAID device.
V-238468 Medium Procedures for establishing temporary passwords that meet DoD password requirements for new accounts must be defined, documented, and implemented.
V-238469 Medium DBMS passwords must not be stored in compiled, encoded, or encrypted batch jobs or compiled, encoded, or encrypted application source code.
V-238460 Medium The DBMS must disable user accounts after 35 days of inactivity.
V-238461 Medium The DBMS must support organizational requirements to enforce minimum password length.
V-238462 Medium The DBMS must support organizational requirements to prohibit password reuse for the organization-defined number of generations.
V-238463 Medium The DBMS must support organizational requirements to enforce password complexity by the number of upper-case characters used.
V-238464 Medium The DBMS must support organizational requirements to enforce password complexity by the number of lower-case characters used.
V-238465 Medium The DBMS must support organizational requirements to enforce password complexity by the number of numeric characters used.
V-238466 Medium The DBMS must support organizational requirements to enforce password complexity by the number of special characters used.
V-238467 Medium The DBMS must support organizational requirements to enforce the number of characters that get changed when passwords are changed.
V-219768 Medium Default demonstration and sample databases, database objects, and applications must be removed.
V-219769 Medium Unused database components, DBMS software, and database objects must be removed.
V-219762 Medium The DBMS must protect audit information from unauthorized modification.
V-219763 Medium The DBMS must protect audit information from unauthorized deletion.
V-219760 Medium The DBMS must include organization-defined additional, more detailed information in the audit records for audit events identified by type, location, or subject.
V-219761 Medium The DBMS must protect audit information from any type of unauthorized access.
V-219766 Medium The DBMS must protect audit tools from unauthorized deletion.
V-219767 Medium Database objects must be owned by accounts authorized for ownership.
V-219764 Medium The DBMS must protect audit tools from unauthorized access.
V-219765 Medium The DBMS must protect audit tools from unauthorized modification.
V-219708 Medium Oracle roles granted using the WITH ADMIN OPTION must not be granted to unauthorized accounts.
V-219709 Medium Object permissions granted to PUBLIC must be restricted.
V-219700 Medium The Oracle WITH GRANT OPTION privilege must not be granted to non-DBA or non-Application administrator user accounts.
V-219701 Medium Execute permission must be revoked from PUBLIC for restricted Oracle packages.
V-219704 Medium The Oracle SQL92_SECURITY parameter must be set to TRUE.
V-219705 Medium The Oracle password file ownership and permissions should be limited and the REMOTE_LOGIN_PASSWORDFILE parameter must be set to EXCLUSIVE or NONE.
V-219706 Medium System privileges granted using the WITH ADMIN OPTION must not be granted to unauthorized user accounts.
V-219707 Medium System Privileges must not be granted to PUBLIC.
V-238479 Medium The DBMS must support taking organization-defined list of least disruptive actions to terminate suspicious events.
V-238478 Medium The DBMS must verify there have not been unauthorized changes to the DBMS software and information.
V-238473 Medium The DBMS must terminate the network connection associated with a communications session at the end of the session or after 15 minutes of inactivity.
V-238472 Medium The DBMS must employ strong identification and authentication techniques when establishing non-local maintenance and diagnostic sessions.
V-238471 Medium The DBMS must employ cryptographic mechanisms to protect the integrity and confidentiality of non-local maintenance and diagnostic communications.
V-238470 Medium The DBMS must enforce password maximum lifetime restrictions.
V-238477 Medium The DBMS must protect against or limit the effects of the organization-defined types of Denial of Service (DoS) attacks.
V-238476 Medium The DBMS must automatically terminate emergency accounts after an organization-defined time period for each type of account.
V-238475 Medium Database data files containing sensitive information must be encrypted.
V-238474 Medium The DBMS must implement required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
V-219779 Medium The DBMS must terminate user sessions upon user logout or any other organization or policy-defined session termination events, such as idle time limit exceeded.
V-219778 Medium The DBMS must use NIST-validated FIPS 140-2-compliant cryptography for authentication mechanisms.
V-219775 Medium The DBMS, when utilizing PKI-based authentication, must validate certificates by constructing a certification path with status information to an accepted trust anchor.
V-219774 Medium The DBMS must support organizational requirements to enforce password encryption for storage.
V-219777 Medium Processes (services, applications, etc.) that connect to the DBMS independently of individual users, must use valid, current DoD-issued PKI certificates for authentication to the DBMS.
V-219776 Medium The DBMS must ensure that PKI-based authentication maps the authenticated identity to the user account.
V-219771 Medium Use of external executables must be authorized.
V-219770 Medium Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.
V-219773 Medium The DBMS must support the organizational requirements to specifically prohibit or restrict the use of unauthorized functions, ports, protocols, and/or services.
V-219772 Medium Access to external executables must be disabled or restricted.
V-219797 Low The DBMS must protect against an individual using a group account from falsely denying having performed a particular action.
V-219698 Low A minimum of two Oracle control files must be defined and configured to be stored on separate, archived disks (physical or virtual) or archived partitions on a RAID device.