| Checked | Name | Title |
|---|
| ☐ | SV-219824r533013_rule | Access to default accounts used to support replication must be restricted to authorized DBAs. |
| ☐ | SV-219825r533016_rule | Oracle instance names must not contain Oracle version numbers. |
| ☐ | SV-219826r533019_rule | Fixed user and public database links must be authorized for use. |
| ☐ | SV-219827r533022_rule | 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. |
| ☐ | SV-219828r533025_rule | 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. |
| ☐ | SV-219829r533028_rule | The Oracle WITH GRANT OPTION privilege must not be granted to non-DBA or non-Application administrator user accounts. |
| ☐ | SV-219830r533031_rule | The Oracle REMOTE_OS_AUTHENT parameter must be set to FALSE. |
| ☐ | SV-219831r533034_rule | The Oracle REMOTE_OS_ROLES parameter must be set to FALSE. |
| ☐ | SV-219832r533037_rule | The Oracle SQL92_SECURITY parameter must be set to TRUE. |
| ☐ | SV-219833r533040_rule | The Oracle password file ownership and permissions should be limited and the REMOTE_LOGIN_PASSWORDFILE parameter must be set to EXCLUSIVE or NONE. |
| ☐ | SV-219834r666930_rule | System privileges granted using the WITH ADMIN OPTION must not be granted to unauthorized user accounts. |
| ☐ | SV-219835r533046_rule | System Privileges must not be granted to PUBLIC. |
| ☐ | SV-219836r666928_rule | Oracle roles granted using the WITH ADMIN OPTION must not be granted to unauthorized accounts. |
| ☐ | SV-219837r666932_rule | Object permissions granted to PUBLIC must be restricted. |
| ☐ | SV-219838r533055_rule | The Oracle Listener must be configured to require administration authentication. |
| ☐ | SV-219839r533058_rule | Application role permissions must not be assigned to the Oracle PUBLIC role. |
| ☐ | SV-219840r533061_rule | Oracle application administration roles must be disabled if not required and authorized. |
| ☐ | SV-219841r533064_rule | Connections by mid-tier web and application systems to the Oracle DBMS from a DMZ or external network must be encrypted. |
| ☐ | SV-219842r533067_rule | Database job/batch queues must be reviewed regularly to detect unauthorized database job submissions. |
| ☐ | SV-219843r533070_rule | Unauthorized database links must not be defined and active. |
| ☐ | SV-219844r533073_rule | Sensitive information from production database exports must be modified before import to a development database. |
| ☐ | SV-219847r401224_rule | Only authorized system accounts must have the SYSTEM tablespace specified as the default tablespace. |
| ☐ | SV-219848r401224_rule | Application owner accounts must have a dedicated application tablespace. |
| ☐ | SV-219849r401224_rule | The directories assigned to the LOG_ARCHIVE_DEST* parameters must be protected from unauthorized access. |
| ☐ | SV-219850r401224_rule | The Oracle _TRACE_FILES_PUBLIC parameter if present must be set to FALSE. |
| ☐ | SV-219851r401224_rule | Application object owner accounts must be disabled when not performing installation or maintenance actions. |
| ☐ | SV-219852r401224_rule | DBMS production application and data directories must be protected from developers on shared production/development DBMS host systems. |
| ☐ | SV-219853r401224_rule | Use of the DBMS installation account must be logged. |
| ☐ | SV-219861r401224_rule | The 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-219862r401224_rule | 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. |
| ☐ | SV-219865r401224_rule | Access to DBMS software files and directories must not be granted to unauthorized users. |
| ☐ | SV-219866r401224_rule | Replication accounts must not be granted DBA privileges. |
| ☐ | SV-219867r401224_rule | Network access to the DBMS must be restricted to authorized personnel. |
| ☐ | SV-219868r401224_rule | Changes to configuration options must be audited. |
| ☐ | SV-219871r401224_rule | Changes to DBMS security labels must be audited. |
| ☐ | SV-219872r401224_rule | Remote database or other external access must use fully-qualified names. |
| ☐ | SV-219873r401224_rule | The /diag subdirectory under the directory assigned to the DIAGNOSTIC_DEST parameter must be protected from unauthorized access. |
| ☐ | SV-219874r401224_rule | Remote administration must be disabled for the Oracle connection manager. |
| ☐ | SV-219875r401224_rule | Network client connections must be restricted to supported versions. |
| ☐ | SV-220263r397597_rule | The DBMS, when using PKI-based authentication, must enforce authorized access to the corresponding private key. |
| ☐ | SV-220264r395442_rule | The DBMS must limit the number of concurrent sessions for each system account to an organization-defined number of sessions. |
| ☐ | SV-220265r395475_rule | The system must employ automated mechanisms for supporting Oracle user account management. |
| ☐ | SV-220266r395499_rule | The DBMS must enforce approved authorizations for logical access to the system in accordance with applicable policy. |
| ☐ | SV-220267r395706_rule | The DBMS must provide audit record generation capability for organization-defined auditable events within the database. |
| ☐ | SV-220268r395709_rule | The DBMS must allow designated organizational personnel to select which auditable events are to be audited by the database. |
| ☐ | SV-220269r395712_rule | The DBMS must generate audit records for the DoD-selected list of auditable events, to the extent such information is available. |
| ☐ | SV-220270r395721_rule | The DBMS must produce audit records containing sufficient information to establish what type of events occurred. |
| ☐ | SV-220271r395724_rule | The DBMS must produce audit records containing sufficient information to establish when (date and time) the events occurred. |
| ☐ | SV-220272r666961_rule | The DBMS must produce audit records containing sufficient information to establish where the events occurred. |
| ☐ | SV-220273r395730_rule | The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events. |
| ☐ | SV-220274r395733_rule | The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. |
| ☐ | SV-220275r395736_rule | The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. |
| ☐ | SV-220276r395739_rule | The DBMS must include organization-defined additional, more detailed information in the audit records for audit events identified by type, location, or subject. |
| ☐ | SV-220277r395820_rule | The system must protect audit information from any type of unauthorized access. |
| ☐ | SV-220278r395823_rule | The system must protect audit information from unauthorized modification. |
| ☐ | SV-220279r395826_rule | The system must protect audit information from unauthorized deletion. |
| ☐ | SV-220280r395829_rule | The system must protect audit tools from unauthorized access. |
| ☐ | SV-220281r395832_rule | The system must protect audit tools from unauthorized modification. |
| ☐ | SV-220282r395835_rule | The system must protect audit tools from unauthorized deletion. |
| ☐ | SV-220283r395850_rule | Database objects must be owned by accounts authorized for ownership. |
| ☐ | SV-220284r395853_rule | Default demonstration and sample databases, database objects, and applications must be removed. |
| ☐ | SV-220285r395853_rule | Unused database components, DBMS software, and database objects must be removed. |
| ☐ | SV-220286r395853_rule | Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled. |
| ☐ | SV-220287r395853_rule | Use of external executables must be authorized. |
| ☐ | SV-220288r395853_rule | Access to external executables must be disabled or restricted. |
| ☐ | SV-220289r395856_rule | The DBMS must support the organizational requirements to specifically prohibit or restrict the use of unauthorized functions, ports, protocols, and/or services. |
| ☐ | SV-220290r397522_rule | The DBMS must support organizational requirements to enforce password encryption for storage. |
| ☐ | SV-220291r397594_rule | The DBMS, when utilizing PKI-based authentication, must validate certificates by constructing a certification path with status information to an accepted trust anchor. |
| ☐ | SV-220292r397600_rule | The DBMS must map the authenticated identity to the user account using PKI-based authentication. |
| ☐ | SV-220293r666959_rule | Processes (services, applications, etc.) that connect to the DBMS independently of individual users, must use valid, current DoD approved PKI certificates for authentication to the DBMS. |
| ☐ | SV-220294r397606_rule | The DBMS must use NIST-validated FIPS 140-2-compliant cryptography for authentication mechanisms. |
| ☐ | SV-220295r397729_rule | The 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-220296r397741_rule | The DBMS must preserve any organization-defined system state information in the event of a system failure. |
| ☐ | SV-220297r397744_rule | The DBMS must take needed steps to protect data at rest and ensure confidentiality and integrity of application data. |
| ☐ | SV-220298r397747_rule | The DBMS must isolate security functions from nonsecurity functions by means of separate security domains. |
| ☐ | SV-220299r397765_rule | The DBMS must prevent unauthorized and unintended information transfer via shared system resources. |
| ☐ | SV-220300r397834_rule | The DBMS must check the validity of data inputs. |
| ☐ | SV-220301r397843_rule | 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. |
| ☐ | SV-220302r397846_rule | The DBMS must restrict error messages so only authorized personnel may view them. |
| ☐ | SV-220303r397603_rule | Applications must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-220304r397603_rule | When 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-220305r708413_rule | The DBMS must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-220306r395850_rule | Database software, applications, and configuration files must be monitored to discover unauthorized changes. |
| ☐ | SV-220307r395850_rule | Logic modules within the database (to include packages, procedures, functions and triggers) must be monitored to discover unauthorized changes. |
| ☐ | SV-220308r395850_rule | The DBMS software installation account must be restricted to authorized users. |
| ☐ | SV-220309r395850_rule | Database software directories, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. |
| ☐ | SV-220310r395859_rule | The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-220311r397609_rule | The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). |
| ☐ | SV-220312r397711_rule | The DBMS must separate user functionality (including user interface services) from database management functionality. |
| ☐ | SV-220313r395691_rule | The DBMS must protect against an individual who uses a shared account falsely denying having performed a particular action. |
| ☐ | SV-237696r667120_rule | DBA OS accounts must be granted only those host system privileges necessary for the administration of the DBMS. |
| ☐ | SV-237697r667123_rule | Oracle software must be evaluated and patched against newly found vulnerabilities. |
| ☐ | SV-237698r667126_rule | DBMS default accounts must be assigned custom passwords. |
| ☐ | SV-237699r667129_rule | 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. |
| ☐ | SV-237700r667132_rule | The DBMS must support the disabling of network protocols deemed by the organization to be nonsecure. |
| ☐ | SV-237701r667135_rule | The DBMS must provide a mechanism to automatically identify accounts designated as temporary or emergency accounts. |
| ☐ | SV-237702r667138_rule | The DBMS must provide a mechanism to automatically remove or disable temporary user accounts after 72 hours. |
| ☐ | SV-237703r667141_rule | 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 including or excluding access to the granularity of a single user. |
| ☐ | SV-237704r667144_rule | The DBMS must restrict grants to sensitive information to authorized user roles. |
| ☐ | SV-237705r667147_rule | A single database connection configuration file must not be used to configure all database clients. |
| ☐ | SV-237706r667150_rule | The DBMS must be protected from unauthorized access by developers. |
| ☐ | SV-237707r667153_rule | The DBMS must be protected from unauthorized access by developers on shared production/development host systems. |
| ☐ | SV-237708r667156_rule | The DBMS must restrict access to system tables and other configuration information or metadata to DBAs or other authorized users. |
| ☐ | SV-237709r667159_rule | Administrative privileges must be assigned to database accounts via database roles. |
| ☐ | SV-237710r667162_rule | Administrators must utilize a separate, distinct administrative account when performing administrative activities, accessing database security functions, or accessing security-relevant information. |
| ☐ | SV-237711r667165_rule | The DBA role must not be assigned excessive or unauthorized privileges. |
| ☐ | SV-237712r667168_rule | OS accounts utilized to run external procedures called by the DBMS must have limited privileges. |
| ☐ | SV-237713r667171_rule | The DBMS must verify account lockouts persist until reset by an administrator. |
| ☐ | SV-237714r667174_rule | The DBMS must set the maximum number of consecutive invalid logon attempts to three. |
| ☐ | SV-237715r667177_rule | Databases utilizing Discretionary Access Control (DAC) must enforce a policy that limits propagation of access rights. |
| ☐ | SV-237716r667180_rule | A DBMS utilizing Discretionary Access Control (DAC) must enforce a policy that includes or excludes access to the granularity of a single user. |
| ☐ | SV-237717r667183_rule | 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. |
| ☐ | SV-237718r667186_rule | The system must provide a real-time alert when organization-defined audit failure events occur. |
| ☐ | SV-237719r667189_rule | The DBMS must support enforcement of logical access restrictions associated with changes to the DBMS configuration and to the database itself. |
| ☐ | SV-237720r667192_rule | Database backup procedures must be defined, documented, and implemented. |
| ☐ | SV-237721r667195_rule | Database recovery procedures must be developed, documented, implemented, and periodically tested. |
| ☐ | SV-237722r667198_rule | DBMS backup and restoration files must be protected from unauthorized access. |
| ☐ | SV-237723r667201_rule | The DBMS must use multifactor authentication for access to user accounts. |
| ☐ | SV-237724r667204_rule | The DBMS must ensure users are authenticated with an individual authenticator prior to using a shared authenticator. |
| ☐ | SV-237725r667207_rule | The DBMS must disable user accounts after 35 days of inactivity. |
| ☐ | SV-237726r667210_rule | The DBMS must support organizational requirements to enforce minimum password length. |
| ☐ | SV-237727r667213_rule | The DBMS must support organizational requirements to prohibit password reuse for the organization-defined number of generations. |
| ☐ | SV-237728r667216_rule | The DBMS must support organizational requirements to enforce password complexity by the number of upper-case characters used. |
| ☐ | SV-237729r667219_rule | The DBMS must support organizational requirements to enforce password complexity by the number of lower-case characters used. |
| ☐ | SV-237730r667222_rule | The DBMS must support organizational requirements to enforce password complexity by the number of numeric characters used. |
| ☐ | SV-237731r667225_rule | The DBMS must support organizational requirements to enforce password complexity by the number of special characters used. |
| ☐ | SV-237732r667228_rule | The DBMS must support organizational requirements to enforce the number of characters that get changed when passwords are changed. |
| ☐ | SV-237733r667231_rule | Procedures for establishing temporary passwords that meet DoD password requirements for new accounts must be defined, documented, and implemented. |
| ☐ | SV-237734r667234_rule | DBMS passwords must not be stored in compiled, encoded, or encrypted batch jobs or compiled, encoded, or encrypted application source code. |
| ☐ | SV-237735r708389_rule | The DBMS must enforce password maximum lifetime restrictions. |
| ☐ | SV-237736r667240_rule | The DBMS must employ cryptographic mechanisms to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications. |
| ☐ | SV-237737r667243_rule | The DBMS must employ strong identification and authentication techniques when establishing nonlocal maintenance and diagnostic sessions. |
| ☐ | SV-237738r667246_rule | The DBMS must terminate the network connection associated with a communications session at the end of the session or 15 minutes of inactivity. |
| ☐ | SV-237739r667249_rule | The DBMS must implement required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. |
| ☐ | SV-237740r667252_rule | Database data files containing sensitive information must be encrypted. |
| ☐ | SV-237741r667255_rule | The DBMS must automatically terminate emergency accounts after an organization-defined time period for each type of account. |
| ☐ | SV-237742r667258_rule | The DBMS must protect against or limit the effects of organization-defined types of Denial of Service (DoS) attacks. |
| ☐ | SV-237743r667261_rule | The system must verify there have not been unauthorized changes to the DBMS software and information. |
| ☐ | SV-237744r667264_rule | The DBMS must support taking organization-defined list of least disruptive actions to terminate suspicious events. |
| ☐ | SV-237745r667267_rule | Use of the DBMS software installation account must be restricted. |
| ☐ | SV-237746r667270_rule | The OS must limit privileges to change the DBMS software resident within software libraries (including privileged programs). |
| ☐ | SV-237747r667273_rule | Oracle Database must off-load audit data to a separate log management facility; this must be continuous and in near-real-time for systems with a network connection to the storage facility, and weekly or more often for stand-alone systems. |
| ☐ | SV-237748r667280_rule | Oracle database products must be a version supported by the vendor. |
STIGQter: STIG Summary: