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-7943: Can DirectAudit be Configured to Prevent Auditing of Specific Commands Using dash.cmd.audit.blacklist?

Centrify DirectAudit ,  

29 December,16 at 10:29 PM

Applies to:
  
All versions of Centrify DirectAudit 

Question:
  
There are some commands that can produce lengthy output or output that is not desirable to capture on the video playback of a audited session.  An SQL select statement is an example of such a command that may take a long time to execute.  Another example is the output of a command that exposes data that is protected due to industry regulations such as HIPPA. Can the centrifyda.conf parameter:
  
dash.cmd.audit.blacklist

be used to prevent auditing and video capture of specific commands?

Answer:
  
No. With session auditing, the direct audit will capture all the commands in a session in both video and command index format by default.  The centrifyda.conf parameter:
  
dash.cmd.audit.blacklist
  
is only applicable for command line auditing.

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