Custom filters and masking sensitive data in logs.

Answer

Sterling Order Management provides a capability to filter and mask the sensitive data from the logs. The custom filter enables you to match the message against regular expressions and mask the message, if the message matches.

NOTE:
If filtering is enabled, logging will be slower because it results in the execution of one or more regular expressions against every log message. Each debug statement which is suppose to put in log file will check for the pattern. If there is any pattern which match the Credit card like format system will filter the pattern.

Selling and Fulfillment Foundation provides a custom layout, SCIFilteredPatternLayout, to handle message modification. You must change the layout class name in your custom logging configuration to SCIFilteredPatternLayout,

For example:
<layout class=”com.sterlingcommerce.woodstock.util.frame.logex.SCIFilteredPatternLayout”>
<param name=”ConversionPattern” value=”%d:%-7p:%t: %-60m[%X{AppUserId}]: %-25c{1}%n”/>
<param name=”FilterSet” value=”common-filter”/> <!-- Optional -->
</layout>

Selling and Fulfillment Foundation provides a custom filter, SCIPatternFilter, to filter out any messages that match certain regular expressions. You must change the filter class name in your custom logging configuration,

For example:
<filter class=”com.sterlingcommerce.woodstock.util.frame.logex.SCIPatternFilter” >
<param name=”FilterSet” value=”suppress” /> <!-- Optional -->
</filter>

NOTE:
Filter will not be invoked when agent Server/integration server are generating the logs.