While I'm able to mask 16 digit numbers I would like a more sophisticated approach as there are some numbers in that range that are not credit card numbers that I don't want to mask, such as error codes. Is anyone utilizing the Luhn Algorithm (http://rosettacode.org/wiki/Luhn_test_of_credit_card_numbers) or something better than my current approach?
The venerable old-skool Splunk forums are now closed. Feel free to search for old content here, but new posts are no longer supported.
Instead, please visit the thriving community at answers.splunk.com to ask and answer questions about your Splunk deployment and how to get the most out of it.
Forums: SplunkGeneral: Masking credit card numbers
Next Topic: Live tail
Posts 1–1 of 1