Detections
Analytics
O19C-00-001000 - Oracle Database must enforce approved authorizations for logical access to the system in accordance with applicable policy.
Warning! Audit Deprecated
This audit has been deprecated and will be removed in a future update.
View Next Audit VersionInformation
Authentication with a DOD-approved public key infrastructure (PKI) certificate does not necessarily imply authorization to access the database management system (DBMS). To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems, including databases, must be properly configured to implement access control policies.Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.
Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.
This requirement is applicable to access control enforcement applications, a category that includes database management systems. If the DBMS does not follow applicable policy when approving access, it may be in conflict with networks or other applications in the information system. This may result in users either gaining or being denied access inappropriately and in conflict with applicable policy.
Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000340-DB-000304
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
If Oracle Database Vault is in use, use it to configure the correct access privileges for each type of user.If Oracle Database Vault is not in use, configure the correct access privileges for each type of user using Roles and Profiles.
For more information on the configuration of Database Vault, refer to the Database Vault Administrator's Guide:
https://docs.oracle.com/en/database/oracle/oracle-database/19/dvadm/database-vault-administrators-guide.pdf.
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_Database_19c_V1R1_STIG.zip
Item Details
Audit Name: DISA Oracle Database 19c STIG v1r1 Database
References: CAT|I, CCI|CCI-000213, CCI|CCI-002235, Rule-ID|SV-270500r1064778_rule, STIG-ID|O19C-00-001000, Vuln-ID|V-270500
Plugin: OracleDB
Control ID: c4ceb33c3334a1b614c436b424c16bbc2998a2d6481d10655af702b1149d4bec