From Oracle Database 11.2g Security Technical Implementation Guide
Part of SRG-APP-000168-DB-000072
Associated with: CCI-000194
Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
If all user accounts are authenticated by the OS or an enterprise-level authentication/access mechanism, and not by Oracle, stop here: this is not a finding against the DBMS.
For each profile that can be applied to accounts where authentication is under Oracle's control, determine the password verification function, if any, that is in use:
SELECT * FROM SYS.DBA_PROFILES
WHERE RESOURCE_NAME = 'PASSWORD_VERIFY_FUNCTION'
[AND PROFILE NOT IN ()]
ORDER BY PROFILE;
Bearing in mind that a profile can inherit from another profile, and the root profile is called DEFAULT, determine the name of the password verification function effective for each profile.
If, for any profile, the function name is null, this is a finding.
For each password verification function, examine its source code. If it does not enforce the organization-defined minimum number of numeric characters (1 unless otherwise specified), this is a finding.
If all user accounts are authenticated by the OS or an enterprise-level authentication/access mechanism, and not by Oracle, no fix to the DBMS is required.
If any user accounts are managed by Oracle: Develop, test and implement a password verification function that enforces DoD requirements.
(Oracle supplies a sample function called verify_function_11G, in the script file
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