OnDemand Users Group

Support Forums => CMOD for Multiplatforms => Topic started by: rstockton on June 11, 2014, 03:23:35 PM

Title: PCI Security in OnDemand
Post by: rstockton on June 11, 2014, 03:23:35 PM
Is anyone doing anything with OnDemand to encrypt or use other methods to secure PCI information?



Thanks,
Russell
Title: Re: PCI Security in OnDemand
Post by: Justin Derrick on June 12, 2014, 11:34:53 AM
Years ago, IBM bought Vormetric. 

Neither CMOD, DB2, or TSM support encryption of data (although tape drives that support encryption are compatible with TSM), so it's up to something at the operating system layer -- that something is Vormetric, although I don't know what IBM is calling it today.

-JD.
Title: Re: PCI Security in OnDemand
Post by: rstockton on June 12, 2014, 12:34:53 PM
Thanks Justin.
Title: Re: PCI Security in OnDemand
Post by: Mike on June 26, 2014, 10:56:43 PM
We're undergoing a project for it right now, and essentially each vendor has a bunch of products that they can throw at it and still have gaps, but there seems to be no one button fix.

That being said, I think TSM does have encryption in V6 now, but we're just going to encrypt the source data since TSM doesn't really care what you send it.
Title: Re: PCI Security in OnDemand
Post by: ewirtz on June 30, 2014, 07:17:07 AM
Hi Mike,
for PCI it's not required to encrypt everything. It's anough mask the creditcard numbers with tokens in your docunments. Additionally you need an encrypted table, which allows you to get the creditcard number for a given token and the token for a given creditcard number. By this technique you can do nesarly everything with your documents without doing any encription / decription. Only if you need the original card number you need to decrypt the token. This technique is a general approach that works as well in IT in general.

regards

Egon