O112-C2-004100 - Administrators must utilize a separate, distinct administrative account when performing administrative activities, accessing database security functions, or accessing security-relevant information.


This requirement is intended to limit exposure due to operating from within a privileged account or role. The inclusion of role is intended to address those situations where an access control policy, such as Role Based Access Control (RBAC), is being implemented and where a change of role provides the same degree of assurance in the change of access authorizations for both the user and all processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account.

To limit exposure when operating from within a privileged account or role, the application must support organizational requirements that users of information system accounts, or roles, with access to organization-defined lists of security functions or security-relevant information, use non-privileged accounts, or roles, when accessing other (non-security) system functions.

When privileged activities are not separated from non-privileged activities, the database can be subject to unauthorized changes to settings and data that a standard user would not normally have access to, outside of an authorized maintenance session.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.


Revoke DBA privileges, and privileges to administer DBA-owned objects, from non-DBA accounts.

Provide separate accounts to DBA for database administration.

See Also


Item Details


References: 800-53|SC-3, CAT|II, CCI|CCI-001084, Rule-ID|SV-238445r879643_rule, STIG-ID|O112-C2-004100, STIG-Legacy|SV-66603, STIG-Legacy|V-52387, Vuln-ID|V-238445

Plugin: OracleDB

Control ID: cce4886249125d64d5c20ea21b8743aaa9ed450d9a30a9ccf849b5680ae27cd9