O121-C1-015000 - DBMS default accounts must be assigned custom passwords.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Password maximum lifetime is the maximum period of time, (typically in days) a user's password may be in effect before the user is forced to change it.

Passwords need to be changed at specific policy-based intervals as per policy. Any password, no matter how complex, can eventually be cracked.

One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the system and/or application passwords could be compromised.

DBMS default passwords provide a commonly known and exploited means for unauthorized access to database installations.

Solution

Change passwords for DBMS accounts to non-default values. Where necessary, unlock or enable accounts to change the password, and then return the account to disabled or locked status.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_Database_12c_V2R8_STIG.zip

Item Details

References: CAT|I, CCI|CCI-000366, Rule-ID|SV-237698r879887_rule, STIG-ID|O121-C1-015000, STIG-Legacy|SV-76031, STIG-Legacy|V-61541, Vuln-ID|V-237698

Plugin: OracleDB

Control ID: 6033bd20060bff3a6fb49c992eb97d72f97cbc8668c5c73a2b1bd383bbadf23b