From Oracle Database 12c Security Technical Implementation Guide
Part of SRG-APP-000026-DB-000005
Associated with: CCI-000018
Once an attacker establishes initial access to a system, they often attempt to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account.
Check Oracle settings (and also OS settings and/or enterprise-level authentication/access mechanisms settings) to determine if account creation is being audited. If account creation is not being audited by Oracle, this is a finding. If Standard Auditing is used: To see if Oracle is configured to capture audit data, enter the following SQL*Plus command: SHOW PARAMETER AUDIT_TRAIL or the following SQL query: SELECT * FROM SYS.V$PARAMETER WHERE NAME = 'audit_trail'; If Oracle returns the value 'NONE', this is a finding. If Unified Auditing is used: To see if Oracle is configured to capture audit data including account creation, enter the following SQL*Plus command: SELECT ' Account creation is not being audited. ' FROM dual WHERE (SELECT Count(*) FROM (select policy_name , audit_option from audit_unified_policies WHERE audit_option = 'CREATE USER' and policy_name in (select policy_name from audit_unified_enabled_policies where user_name='ALL USERS'))) = 0 OR (SELECT value FROM v$option WHERE parameter = 'Unified Auditing') != 'TRUE'; If Oracle returns "no rows selected", this is not a finding.
Configure Oracle to audit account creation activities.
If Standard Auditing is used:
Use this process to ensure auditable events are captured:
ALTER SYSTEM SET AUDIT_TRAIL=
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer