With the Winter 16 release, salesforce released a feature that allows admins to block certain patterns from being captured by Live Agent chats. This was really the first time salesforce had released a feature to address what happens if you accidentally capture sensitive information from your customers. The fact is that your customer’s are not always particularity smart about keeping their personal data – such as social security numbers of even credit card numbers safe and very easily can make this your problem by sending this information to you by email, chat or web. Potentially even worse, your customer facing agents may accidentally capture this information within a Lead or a Case when the customer gives it to them over the phone. Either way, if that data is captured in your salesforce in an non-encrypted field, you are responsible for it.
Prior to GearsDataMask, we had built custom apex triggers to recognize patterns and automatically obfuscate those patterns when they were detected similar to how the Winter 16 feature handles live chats. Now, with GearsDataMask’s we no longer have to build a trigger for each pattern. Now, with an app you can maintain without code, you can look for any pattern on any field on any object and when that pattern is identified you can determine how it should be handled. Want to look for a pattern like ###-##-#### and then turn each number into an asterisk? That comes out of the box. Looking for an easy solution for credit card masking in salesforce? We’ve included all of the major US credit card patterns and US Social Security Number pattern automatically, so instead of having to plugin all of the credit card patterns, you are ready to use the app as soon as you install it. GearsDataMask is now available on the AppExchange!
Overall, this allows you to easily and automatically mask credit card data in salesforce, as well as to seek out and remove any other sensitive data that has a pattern on any object. For more information, including a Free Trial, Contact Us.