Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-3404: Configuring additional password blocking capability in DirectAudit

Centrify DirectAudit ,  

17 January,17 at 01:13 AM

Applies to: Centrify DirectAudit 3.0.x and 3.1.0 on RHEL/Fedora platforms
 
Problem:
 
There are some occasions where the "Export Session with User Inputs" report may show user passwords in the clear.
 
Consider the following scenario:
  1. Centrify DirectAudit and Centrify DirectControl is installed on RHEL 5.7 x86_64 and configured.
     
  2. The parameter "dash.auditstdin" is set to true in /etc/centrifyda/centrifyda.conf.  This allows the capture of keyboard input.
     
  3. The command "useradd u111" is executed to add a new local user and password was changed with "password"
     
  4. The local user "u111" logs in and runs the "date" command
     
    ************************** 
    [u111@rhel57x64v3 ~]$ date
    Tue Aug  6 09:53:48 CST 2013
    **************************
     
  5. The example command "sudo adinfo" is run and the password entered.
     
    ============================
    A new session is generated.   <-- This is expected behavior.
    ============================
     
  6. The session generated at Step 5 is exported with user input, and the exported file opened.

    The password entered at Step 5 is seen when it should have been replaced with "xxxxxx". 
 
Cause:
 
Centrify DirectAudit v3.0 and beyond has the capability to capture all user keyboard input as an option; It will detect if the user enters a password in response to a password prompt, and automatically masks out the password. The password information is not sent to the Collector and is not stored in the AuditStore databases. This prevents the auditor from accessing other users' passwords.
 
To detect the password prompt, Centrify DA uses a default regular expression. The Administrator should use the dash.auditstdin.except parameter in /etc/centrifyda/centrifyda.conf to define additional regular expressions that may be needed for the environment. 
 
The current default regular expression is:
 
dash.auditstdin.except: (password[a-zA-Z \t]*:[[:space:]]*$)|(verify[a-zA-Z \t]*:[[:space:]]*$)
 
This checks for the words "password" or "verify", followed by alphabetic characters, space or tab, and then a colon, and any number of whitespace characters. 
This pattern covers the most common use cases.
 
It was found that the above regular expression does not work when a user with a non-alphabetic user name uses dzdo/sudo and then goes through a password authentication; or in other situations where the password prompt does not match the above regular expression. 
 
Workaround:
 
The dash.auditstdin.except in /etc/centrifydc/centrifyda.conf parameter can be set with the following line instead:
 
dash.auditstdin.except: (password[[:alnum:][:blank:][:punct:]]*:[[:space:]]*$)|(verify[[:alnum:][:blank:][:punct:]]*:[[:space:]]*$)
 
Resolution:
 
The workaround regex will be used as the default regular expression in the next release of DirectAudit.
 
If there are other applications where the password prompt does not match the above regular expression, then can add the additional patterns to the same parameter.
 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.