This documentation is archived and is not being maintained.

Sensitive Log Data

Speech Server 2007

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The Speech Server??Analytics and Tuning Studio uses a Microsoft SQL??Server 2005 database to store and manage call data derived from Windows Evnet Trace Log (ETL) files. ETL files contain raw call data, which can include sensitive information about callers, such as social security numbers or credit card numbers. Sensitive information can be suppressed from the call data by the application when collected data is marked as confidential. For more information, see Collecting Confidential Data. Marking data as confidential is dependent on the application designer implementing the feature within the code. Regardless of whether it is done, you should consider safeguards to ensure that the privacy of sensitive caller information.

ETL files are generated by Speech Server and written to a predefined location based on the logging configuration. For more information, see Logging Administration. By default, the ETL files are written to %ProgramFiles%\Microsoft Office Communications Server 2007 Speech Server\Logs. If you decide to change this location, the NETWORK SERVICE account (the account Speech Server uses to create the ETL files), should have write permission in the new directory. Also, if you specify a shared directory, privileges for other users should be minimal to help protect the ETL log data.

Data from ETL files must be imported to the database to be used by Analytics and Tuning Studio. Typically, Analytics and Tuning Studio is installed on a separate computer so it does not impact Speech Server performance with tuning activities. Therefore, to import the ETL files, they must be moved to the computer running Analytics and Tuning Studio. When the files are moved, call data can be vulnerable to unwanted access. You should use a trustworthy network when you move the ETL files or use an encrypted file transfer method, such as File Transfer Protocol/Secure Sockets Layer, Secure Copy, or Secure Shell FTP.