After collecting diagnostic trace from a server running under a cell, a system administrator noticed that the trace files contained sensitive information.
To avoid this issue in the future, what can the administrator do?
A. Configure entries in the ras.rawtracelist.properties.
B. Configure suppressSensitiveTrace in the bootstrap.properties file.
C. Clear the “Disable logging and tracing of potentially sensitive data” checkbox.
D. Add the entry com.ibm.websphere.logging.RawTraceList=off to the end of the trace string.
You can either enable or disable the sensitive log and trace guard to help control whether loggers write sensitive information in your log and trace files.
Use the administrative console to enable or disable the sensitive log and trace guard.
Procedure
Log on to the administrative console.
If you are using an administrative agent topology, then select a node that you want to manage, and navigate to it.
From the navigation section in the console, choose Troubleshooting > Logs and trace.
Select the server that you want to enable or disable with sensitive log and trace guard.
Click Change log detail levels.
Select the Disable logging and tracing of potentially sensitive data check box to enable sensitive log and trace guard. To disable sensitive log and trace guard, clear the Disable logging and tracing of potentially sensitive data check box.
Click OK
Save the changes.