When you work with SAS Fraud Management Technical support, SAS logs are often required for troubleshooting issues. Some logs contain rule code that might contain sensitive information that must be masked before you send it to SAS. The rule deployment file also contains the rule code. To simplify the task, you can remove all of the rule code from the file rather then searching for sensitive data and masking it manually.
To do that:
- Log on the the UNIX server where the log file is located and navigate to the directory that contains the file.
- Submit the following command after you substitute the actual log file name for sas-log-filename:
sed '/Begin_Rule/,/End_Rule/d' sas-log-filename > clean_sas-log-filename
- Review the resulting clean_sas-log-filename file for any additional sensitive information. If you find any such information, mask it. For example, you can replace the text with asterisks.
- After you remove or mask all sensitive information, you can send the file as an attachment to an email response in your support track. As a second option, you can upload the file to your secure file transfer account at SAS. If the file is too large for an email attachment, you must use this second method. If you do upload the log to the secure site, update your support track with the name of the file that you sent.
The following table lists the log files that contain rule code:
| Area | SAS Log File Name or Pattern | SAS FM Versions |
|---|
| Estimation log | estimate.log | All |
| Rule deployment file | A.sas | All |
| OnDemand Decision Engine SAS log | sas_num.log | 4.2M1 and higher |
| Java OnDemand Scoring Engine SAS log | sas_ose_type_date_time.log | 4.1M0 and lower |
| Alert Generation Server SAS log | sas_date_time_Instancenum_*.log | 4.1M0 and lower |