From Oracle Database 12c Security Technical Implementation Guide
Part of SRG-APP-000292-DB-000138
Associated with: CCI-001684
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 modify an existing account for later use.
Check DBMS settings to determine whether it will notify appropriate individuals when accounts are modified. If the DBMS does not notify appropriate individuals when accounts are modified, this is a finding.
Working with the DBA and site management, determine the appropriate individuals (by job role) to be notified. If Oracle Audit Vault is available, configure it to notify the appropriate individuals when accounts are modified. If Oracle Audit Vault is not available, configure the Oracle DBMS's auditing feature to record account-modification activity. If Standard Auditing is used: Create and deploy a mechanism, such as a frequently-run job, to monitor the SYS.AUD$ table for these records and notify the appropriate individuals. If unified Auditing is used: Create and deploy a mechanism, such as a frequently-run job, to monitor the SYS.UNIFIED_AUDIT_TRAIL view for these records and notify the appropriate individuals.
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