Detections
Analytics
O112-C2-013300 - The DBMS must ensure users are authenticated with an individual authenticator prior to using a group authenticator.
Information
To assure individual accountability and prevent unauthorized access, application users (and any processes acting on behalf of users) must be individually identified and authenticated.A group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. An example of a group authenticator is the UNIX OS 'root' user account, a Windows 'administrator' account, an 'SA' account, or a 'helpdesk' account.
For example, the UNIX and Windows operating systems offer a 'switch user' capability allowing users to authenticate with their individual credentials and, when needed, 'switch' to the administrator role. This method provides for unique individual authentication prior to using a group authenticator.
Some applications may not have the need to provide a group authenticator; this is considered a matter of application design. In those instances where the application design includes the use of a group authenticator, this requirement will apply.
There may also be instances when specific user actions need to be performed on the information system without unique user identification or authentication. An example of this type of access is a web server which contains publicly releasable information. These types of accesses are allowed but must be explicitly identified and documented by the organization.
When group accounts are utilized without another means of identifying individual users, users may deny having performed a particular action.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Configure DBMS, OS and/or enterprise-level authentication/access mechanism to require individual authentication prior to authentication for group account access.If appropriate, install Oracle Access Manager to provide multifactor authentication of applications front-ending Oracle Databases and using group accounts. After installation, use x509 Authentication modules provided out of the box.
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_Database_11-2g_V2R3_STIG.zip
Item Details
Audit Name: DISA STIG Oracle 11.2g v2r3 Database
Category: IDENTIFICATION AND AUTHENTICATION
References: 800-53|IA-2, CAT|II, CCI|CCI-000764, Rule-ID|SV-238459r667551_rule, STIG-ID|O112-C2-013300, STIG-Legacy|SV-66479, STIG-Legacy|V-52263, Vuln-ID|V-238459
Plugin: OracleDB
Control ID: 3821b716b10b8212b903aafffea1fe25a6e10c4a1306782e2089f0c176f98b20