STIGQter STIGQter: STIG Summary: Oracle Database 12c Security Technical Implementation Guide

Version: 1

Release: 16 Benchmark Date: 24 Jan 2020

CheckedNameTitle
SV-75899r1_ruleAudit trail data must be retained for at least one year.
SV-75901r1_ruleAccess to default accounts used to support replication must be restricted to authorized DBAs.
SV-75903r1_ruleOracle instance names must not contain Oracle version numbers.
SV-75905r2_ruleFixed user and public database links must be authorized for use.
SV-75907r3_ruleA 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.
SV-75909r1_ruleA 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.
SV-75911r2_ruleThe Oracle WITH GRANT OPTION privilege must not be granted to non-DBA or non-Application administrator user accounts.
SV-75915r1_ruleThe Oracle REMOTE_OS_AUTHENT parameter must be set to FALSE.
SV-75917r1_ruleThe Oracle REMOTE_OS_ROLES parameter must be set to FALSE.
SV-75919r1_ruleThe Oracle SQL92_SECURITY parameter must be set to TRUE.
SV-75921r3_ruleThe Oracle password file ownership and permissions should be limited to the Oracle installation account and the REMOTE_LOGIN_PASSWORDFILE parameter must be set to EXCLUSIVE or NONE.
SV-75923r4_ruleSystem privileges granted using the WITH ADMIN OPTION must not be granted to unauthorized user accounts.
SV-75925r1_ruleSystem Privileges must not be granted to PUBLIC.
SV-75927r4_ruleOracle roles granted using the WITH ADMIN OPTION must not be granted to unauthorized accounts.
SV-75929r4_ruleObject permissions granted to PUBLIC must be restricted.
SV-75931r2_ruleThe Oracle Listener must be configured to require administration authentication.
SV-75933r1_ruleApplication role permissions must not be assigned to the Oracle PUBLIC role.
SV-75935r2_ruleOracle application administration roles must be disabled if not required and authorized.
SV-75937r2_ruleConnections by mid-tier web and application systems to the Oracle DBMS from a DMZ or external network must be encrypted.
SV-75939r3_ruleDatabase job/batch queues must be reviewed regularly to detect unauthorized database job submissions.
SV-75941r1_ruleUnauthorized database links must not be defined and active.
SV-75943r2_ruleSensitive information from production database exports must be modified before import to a development database.
SV-75945r1_ruleApplication user privilege assignment must be reviewed monthly or more frequently to ensure compliance with least privilege and documented policy.
SV-75947r1_ruleAudit trail data must be reviewed daily or more frequently.
SV-75949r3_ruleOnly authorized system accounts must have the SYSTEM tablespace specified as the default tablespace.
SV-75951r3_ruleApplication owner accounts must have a dedicated application tablespace.
SV-75953r1_ruleThe directories assigned to the LOG_ARCHIVE_DEST* parameters must be protected from unauthorized access.
SV-75955r1_ruleThe Oracle _TRACE_FILES_PUBLIC parameter if present must be set to FALSE.
SV-75957r4_ruleApplication object owner accounts must be disabled when not performing installation or maintenance actions.
SV-75977r1_ruleDBMS production application and data directories must be protected from developers on shared production/development DBMS host systems.
SV-75979r1_ruleUse of the DBMS installation account must be logged.
SV-75981r1_ruleThe DBMS host platform and other dependent applications must be configured in compliance with applicable STIG requirements.
SV-75983r1_ruleRemote administrative access to the database must be monitored by the ISSO or ISSM.
SV-75985r1_ruleThe database must not be directly accessible from public or unauthorized networks.
SV-75987r1_ruleThe ISSM must review changes to DBA role assignments.
SV-75989r1_rulePlans and procedures for testing DBMS installations, upgrades and patches must be defined and followed prior to production implementation.
SV-75991r1_ruleProcedures and restrictions for import of production data to development databases must be documented, implemented and followed.
SV-75993r1_ruleSensitive data stored in the database must be identified in the System Security Plan and AIS Functional Architecture documentation.
SV-75997r1_ruleCredentials stored and used by the DBMS to access remote databases or applications must be authorized and restricted to authorized users.
SV-75999r1_ruleThe DBMS must not share a host supporting an independent security service.
SV-76001r1_ruleAccess to DBMS software files and directories must not be granted to unauthorized users.
SV-76003r1_ruleReplication accounts must not be granted DBA privileges.
SV-76005r2_ruleNetwork access to the DBMS must be restricted to authorized personnel.
SV-76009r1_ruleChanges to configuration options must be audited.
SV-76013r3_ruleRemote DBMS administration must be documented and authorized or disabled.
SV-76015r1_ruleDBMS symmetric keys must be protected in accordance with NSA or NIST-approved key management technology or processes.
SV-76017r4_ruleChanges to DBMS security labels must be audited.
SV-76019r1_ruleRemote database or other external access must use fully-qualified names.
SV-76021r2_ruleThe /diag subdirectory under the directory assigned to the DIAGNOSTIC_DEST parameter must be protected from unauthorized access.
SV-76023r1_ruleRemote administration must be disabled for the Oracle connection manager.
SV-76025r4_ruleNetwork client connections must be restricted to supported versions.
SV-76027r1_ruleDBA OS accounts must be granted only those host system privileges necessary for the administration of the DBMS.
SV-76029r2_ruleOracle software must be evaluated and patched against newly found vulnerabilities.
SV-76031r1_ruleDBMS default accounts must be assigned custom passwords.
SV-76033r4_ruleThe DBMS, when using PKI-based authentication, must enforce authorized access to the corresponding private key.
SV-76035r5_ruleThe DBMS must employ cryptographic mechanisms preventing the unauthorized disclosure of information during transmission unless the transmitted data is otherwise protected by alternative physical measures.
SV-76043r1_ruleThe DBMS must ensure remote sessions that access an organization-defined list of security functions and security-relevant information are audited.
SV-76045r1_ruleThe DBMS must support the disabling of network protocols deemed by the organization to be nonsecure.
SV-76047r2_ruleThe system must employ automated mechanisms for supporting Oracle user account management.
SV-76049r2_ruleThe DBMS must provide a mechanism to automatically identify accounts designated as temporary or emergency accounts.
SV-76051r3_ruleThe DBMS must provide a mechanism to automatically terminate accounts designated as temporary or emergency accounts after an organization-defined time period.
SV-76055r2_ruleThe DBMS must automatically audit account creation.
SV-76059r2_ruleThe DBMS must automatically audit account modification.
SV-76061r4_ruleThe DBMS must automatically audit account disabling actions, to the extent such information is available.
SV-76063r2_ruleThe DBMS must automatically audit account termination.
SV-76065r1_ruleThe DBMS must enforce approved authorizations for logical access to the system in accordance with applicable policy.
SV-76067r1_ruleThe 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 including or excluding access to the granularity of a single user.
SV-76069r2_ruleDBMS processes or services must run under custom, dedicated OS accounts.
SV-76071r1_ruleThe DBMS must restrict grants to sensitive information to authorized user roles.
SV-76073r1_ruleA single database connection configuration file must not be used to configure all database clients.
SV-76075r1_ruleThe DBMS must be protected from unauthorized access by developers.
SV-76077r1_ruleThe DBMS must be protected from unauthorized access by developers on shared production/development host systems.
SV-76079r2_ruleThe DBMS must restrict access to system tables and other configuration information or metadata to DBAs or other authorized users.
SV-76081r3_ruleAdministrative privileges must be assigned to database accounts via database roles.
SV-76083r2_ruleAdministrators must utilize a separate, distinct administrative account when performing administrative activities, accessing database security functions, or accessing security-relevant information.
SV-76085r2_ruleAll use of privileged accounts must be audited.
SV-76087r1_ruleOwners of privileged accounts must use non-privileged accounts for non-administrative activities.
SV-76089r2_ruleThe DBA role must not be assigned excessive or unauthorized privileges.
SV-76091r2_ruleOS accounts utilized to run external procedures called by the DBMS must have limited privileges.
SV-76093r2_ruleThe DBMS must verify account lockouts persist until reset by an administrator.
SV-76095r3_ruleThe DBMS must set the maximum number of consecutive invalid logon attempts to three.
SV-76103r1_ruleThe DBMS must have its auditing configured to reduce the likelihood of storage capacity being exceeded.
SV-76105r1_ruleThe DBMS must have allocated audit record storage capacity.
SV-76107r1_ruleDatabases utilizing Discretionary Access Control (DAC) must enforce a policy that limits propagation of access rights.
SV-76109r1_ruleA DBMS utilizing Discretionary Access Control (DAC) must enforce a policy that includes or excludes access to the granularity of a single user.
SV-76111r1_ruleThe DBMS must provide audit record generation capability for organization-defined auditable events within the database.
SV-76113r1_ruleThe DBMS must allow designated organizational personnel to select which auditable events are to be audited by the database.
SV-76115r3_ruleThe DBMS must generate audit records for the DoD-selected list of auditable events, to the extent such information is available.
SV-76117r2_ruleThe DBMS must produce audit records containing sufficient information to establish what type of events occurred.
SV-76121r1_ruleThe DBMS must produce audit records containing sufficient information to establish when (date and time) the events occurred.
SV-76123r2_ruleThe DBMS must produce audit records containing sufficient information to establish where the events occurred.
SV-76125r2_ruleThe DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events.
SV-76127r1_ruleThe DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
SV-76129r1_ruleThe DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
SV-76131r2_ruleThe DBMS must include organization-defined additional, more detailed information in the audit records for audit events identified by type, location, or subject.
SV-76133r2_ruleThe 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.
SV-76135r2_ruleThe system must provide a real-time alert when organization-defined audit failure events occur.
SV-76137r2_ruleThe system must alert designated organizational officials in the event of an audit processing failure.
SV-76139r2_ruleThe system must provide the capability to automatically process audit records for events of interest based upon selectable event criteria.
SV-76141r1_ruleAttempts to bypass access controls must be audited.
SV-76143r2_ruleThe system must protect audit information from any type of unauthorized access.
SV-76145r1_ruleThe system must protect audit information from unauthorized modification.
SV-76147r1_ruleThe system must protect audit information from unauthorized deletion.
SV-76149r1_ruleThe system must protect audit tools from unauthorized access.
SV-76151r1_ruleThe system must protect audit tools from unauthorized modification.
SV-76153r1_ruleThe system must protect audit tools from unauthorized deletion.
SV-76155r1_ruleThe DBMS must support the requirement to back up audit data and records onto a different system or media than the system being audited on an organization-defined frequency.
SV-76157r2_ruleThe DBMS must protect audit data records and integrity by using cryptographic mechanisms.
SV-76159r1_ruleThe DBMS must protect the audit records generated, as a result of remote access to privileged accounts, and the execution of privileged functions.
SV-76161r1_ruleThe DBMS must support enforcement of logical access restrictions associated with changes to the DBMS configuration and to the database itself.
SV-76163r2_ruleDatabase objects must be owned by accounts authorized for ownership.
SV-76165r1_ruleThe DBMS must enforce requirements for remote connections to the information system.
SV-76167r3_ruleDefault demonstration and sample databases, database objects, and applications must be removed.
SV-76169r2_ruleUnused database components, DBMS software, and database objects must be removed.
SV-76171r2_ruleUnused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.
SV-76173r2_ruleUse of external executables must be authorized.
SV-76175r2_ruleAccess to external executables must be disabled or restricted.
SV-76177r1_ruleThe DBMS must support the organizational requirements to specifically prohibit or restrict the use of unauthorized functions, ports, protocols, and/or services.
SV-76179r1_ruleRecovery procedures and technical system features must exist to ensure recovery is done in a secure and verifiable manner.
SV-76183r2_ruleOracle must back up user-level information per a defined frequency.
SV-76185r1_ruleDatabase backup procedures must be defined, documented, and implemented.
SV-76187r1_ruleDatabase recovery procedures must be developed, documented, implemented, and periodically tested.
SV-76189r1_ruleDBMS backup and restoration files must be protected from unauthorized access.
SV-76191r1_ruleDBMS must conduct backups of system-level information per organization-defined frequency that is consistent with recovery time and recovery point objectives.
SV-76193r3_ruleThe DBMS must use multifactor authentication for network access to privileged accounts.
SV-76195r3_ruleThe DBMS must use multifactor authentication for network access to non-privileged accounts.
SV-76197r3_ruleThe DBMS must use multifactor authentication for local access to privileged accounts.
SV-76199r4_ruleThe DBMS must use multifactor authentication for local access to non-privileged accounts.
SV-76201r1_ruleThe DBMS must ensure users are authenticated with an individual authenticator prior to using a shared authenticator.
SV-76203r4_ruleThe DBMS must use organization-defined replay-resistant authentication mechanisms for network access to privileged accounts.
SV-76205r4_ruleThe DBMS must use organization-defined replay-resistant authentication mechanisms for network access to non-privileged accounts.
SV-76207r2_ruleThe DBMS must disable user accounts after 35 days of inactivity.
SV-76209r2_ruleThe DBMS must support organizational requirements to enforce minimum password length.
SV-76211r2_ruleThe DBMS must support organizational requirements to prohibit password reuse for the organization-defined number of generations.
SV-76213r2_ruleThe DBMS must support organizational requirements to enforce password complexity by the number of upper-case characters used.
SV-76215r2_ruleThe DBMS must support organizational requirements to enforce password complexity by the number of lower-case characters used.
SV-76217r2_ruleThe DBMS must support organizational requirements to enforce password complexity by the number of numeric characters used.
SV-76219r2_ruleThe DBMS must support organizational requirements to enforce password complexity by the number of special characters used.
SV-76221r2_ruleThe DBMS must support organizational requirements to enforce the number of characters that get changed when passwords are changed.
SV-76223r3_ruleThe DBMS must support organizational requirements to enforce password encryption for storage.
SV-76225r1_ruleProcedures for establishing temporary passwords that meet DoD password requirements for new accounts must be defined, documented, and implemented.
SV-76227r4_ruleDBMS passwords must not be stored in compiled, encoded, or encrypted batch jobs or compiled, encoded, or encrypted application source code.
SV-76229r4_ruleThe DBMS must enforce password maximum lifetime restrictions.
SV-76231r4_ruleThe DBMS, when utilizing PKI-based authentication, must validate certificates by constructing a certification path with status information to an accepted trust anchor.
SV-76233r3_ruleThe DBMS must map the authenticated identity to the user account using PKI-based authentication.
SV-76235r2_ruleProcesses (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.
SV-76237r2_ruleThe DBMS must use NIST-validated FIPS 140-2-compliant cryptography for authentication mechanisms.
SV-76239r1_ruleThe DBMS must employ cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications.
SV-76241r1_ruleThe DBMS must employ strong identification and authentication techniques when establishing nonlocal maintenance and diagnostic sessions.
SV-76243r2_ruleDatabases employed to write data to portable digital media must use cryptographic mechanisms to protect and restrict access to information on portable digital media.
SV-76245r2_ruleThe DBMS must support organizational requirements to encrypt information stored in the database and information extracted or derived from the database and stored on digital media.
SV-76247r2_ruleThe DBMS must terminate the network connection associated with a communications session at the end of the session or 15 minutes of inactivity.
SV-76249r3_ruleThe DBMS must implement required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
SV-76251r1_ruleDatabase data files containing sensitive information must be encrypted.
SV-76253r1_ruleThe DBMS must protect the integrity of publicly available information and applications.
SV-76255r2_ruleThe DBMS must terminate user sessions upon user logoff or any other organization or policy-defined session termination events, such as idle time limit exceeded.
SV-76259r3_ruleThe DBMS must preserve any organization-defined system state information in the event of a system failure.
SV-76261r2_ruleThe DBMS must take needed steps to protect data at rest and ensure confidentiality and integrity of application data.
SV-76265r1_ruleThe DBMS must isolate security functions from nonsecurity functions by means of separate security domains.
SV-76267r1_ruleThe DBMS must automatically terminate emergency accounts after an organization-defined time period for each type of account.
SV-76269r1_ruleThe DBMS must employ automated mechanisms to alert security personnel of inappropriate or unusual activities with security implications.
SV-76271r1_ruleThe DBMS must prevent unauthorized and unintended information transfer via shared system resources.
SV-76273r1_ruleThe DBMS must protect against or limit the effects of organization-defined types of Denial of Service (DoS) attacks.
SV-76275r2_ruleThe DBMS must check the validity of data inputs.
SV-76277r1_ruleThe system must verify there have not been unauthorized changes to the DBMS software and information.
SV-76279r1_ruleThe DBMS must identify potentially security-relevant error conditions.
SV-76281r2_ruleThe 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.
SV-76283r2_ruleThe DBMS must restrict error messages so only authorized personnel may view them.
SV-76285r1_ruleThe DBMS must support taking organization-defined list of least disruptive actions to terminate suspicious events.
SV-76287r2_ruleThe DBMS must notify appropriate individuals when accounts are created.
SV-76289r2_ruleThe DBMS must notify appropriate individuals when accounts are modified.
SV-76291r2_ruleThe DBMS must notify appropriate individuals when account disabling actions are taken.
SV-76293r2_ruleThe DBMS must notify appropriate individuals when accounts are terminated.
SV-76299r3_ruleThe DBMS must implement separation of duties through assigned information access authorizations.
SV-76303r1_ruleThe system must provide an audit log reduction capability.
SV-76305r5_ruleThe DBMS must restrict the ability of users to launch Denial of Service (DoS) attacks against other information systems or networks.
SV-76307r3_ruleThe DBMS must manage resources to limit the effects of information flooding types of Denial of Service (DoS) incidents.
SV-76309r2_ruleThe DBMS must limit the use of resources by priority and not impede the host from servicing processes designated as a higher-priority.
SV-76333r2_ruleApplications must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
SV-76335r3_ruleWhen using command-line tools such as Oracle SQL*Plus, which can accept a plain-text password, users must use an alternative logon method that does not expose the password.
SV-76339r1_ruleDBMS default accounts must be protected from misuse.
SV-76343r1_ruleDisk space used by audit trail(s) must be monitored; audit records must be regularly or continuously off-loaded to a centralized log management system.
SV-76355r2_ruleUse of the DBMS software installation account must be restricted.
SV-76357r2_ruleDatabase software, applications, and configuration files must be monitored to discover unauthorized changes.
SV-76359r1_ruleThe OS must limit privileges to change the DBMS software resident within software libraries (including privileged programs).
SV-76361r1_ruleThe DBMS must provide the ability to write specified audit record content to a centralized audit log repository.
SV-76363r1_ruleThe DBMS software installation account must be restricted to authorized users.
SV-76365r1_ruleDatabase software directories, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.
SV-76367r1_ruleThe DBMS software libraries must be periodically backed up.
SV-76369r1_ruleThe DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
SV-76371r1_ruleThe DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
SV-76373r1_ruleThe DBMS must separate user functionality (including user interface services) from database management functionality.
SV-76375r1_ruleThe DBMS must prevent the presentation of information system management-related functionality at an interface utilized by general (i.e., non-privileged) users.
SV-76377r2_ruleThe DBMS must protect against an individual who uses a shared account falsely denying having performed a particular action.
SV-76453r3_ruleThe DBMS data files, transaction logs and audit files must be stored in dedicated directories or disk partitions separate from software or other application files.
SV-76455r3_ruleThe 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.
SV-76457r2_ruleThe DBMS must limit the number of concurrent sessions for each system account to an organization-defined number of sessions.
SV-76459r1_ruleThe system must provide a report generation capability for audit reduction data.
SV-83467r1_ruleLogic modules within the database (to include packages, procedures, functions and triggers) must be monitored to discover unauthorized changes.