asked on Java client app and PCI compliance
I am trying hard to find a way to automate some calculations on a credit card merchant statement. But I must be 100% within the letter and the intent of the rules which define PCI compliance.
Writing a Java app to run on all platforms was a great suggestion to "pre-process" the data, redacting private data, before upload to my site for further processing. But, I wonder, why not do ALL the processing via a downloadable Java App?
Is that a guarantee that I am 100% PCI compliant?
The problem will be when it fails a user and they need it debugged...I would need that PDF file sent to me for debugging. BUT, isn't that a much safer route to take than putting it on a website?
I would certainly have a high security bar to maintain regarding how I handle my PC, and maybe the methodology I use when choosing a password for that email account. But NOT having a website where any Credit Card info resides seems like a smarter way to go.
So, I am now imaging a simple website, probably WordPress. I would post a current version of the Java App for download and explanation of what it does, etc.
Users could download it and privately process their merchant account report on their own PC's. In the LIKELY event they have an unsupported report format, they could email me their full report. (Redacting private data from a PDF itself seems like a pretty high bar for users to handle)
On receipt of the PDF, I would redact all private data for that statement, and delete all un-redacted versions.
Once I have that report working, I would email the final report to that merchant and push an update of the Java App.
Any problems with this approach??
For those who work with PCI, is this PCI compliant?
Thanks.
Writing a Java app to run on all platforms was a great suggestion to "pre-process" the data, redacting private data, before upload to my site for further processing. But, I wonder, why not do ALL the processing via a downloadable Java App?
Is that a guarantee that I am 100% PCI compliant?
The problem will be when it fails a user and they need it debugged...I would need that PDF file sent to me for debugging. BUT, isn't that a much safer route to take than putting it on a website?
I would certainly have a high security bar to maintain regarding how I handle my PC, and maybe the methodology I use when choosing a password for that email account. But NOT having a website where any Credit Card info resides seems like a smarter way to go.
So, I am now imaging a simple website, probably WordPress. I would post a current version of the Java App for download and explanation of what it does, etc.
Users could download it and privately process their merchant account report on their own PC's. In the LIKELY event they have an unsupported report format, they could email me their full report. (Redacting private data from a PDF itself seems like a pretty high bar for users to handle)
On receipt of the PDF, I would redact all private data for that statement, and delete all un-redacted versions.
Once I have that report working, I would email the final report to that merchant and push an update of the Java App.
Any problems with this approach??
For those who work with PCI, is this PCI compliant?
Thanks.
ProgrammingJavaE-CommerceTax / Financial SoftwareSecurity
Last Comment
gr8gonzo
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Once again, thanks a lot. There is plenty for me to ponder!
You're welcome.
Big thing about PCI Compliance is also, once you chose your Compliance company, their scanner will be unique.
So if you change companies (therefore scanner changes too), likely you may have to clean up some other minor things.
And again, all this will be at the server level, so your App should have no effect on your compliance.
Big thing about PCI Compliance is also, once you chose your Compliance company, their scanner will be unique.
So if you change companies (therefore scanner changes too), likely you may have to clean up some other minor things.
And again, all this will be at the server level, so your App should have no effect on your compliance.
David, I have to disagree on the Java thing. Java has so many libraries today that it's far easier to write and maintain compared to Perl (and I write in both). I actually find it to be somewhere between object-oriented PHP and C#. And so many people have Java running nowadays or have installed it before that it shouldn't be a big deal for downloads. Take a look at the popularity of Minecraft or something like Universal Media Server - both Java apps that have extremely simple setups (and probably do more than necessary).
2. A server-side app can definitely impact PCI compliance if it's not securing data properly.
3. I agree it's still not a good idea to not send sensitive data over email but I would just add that things are dramatically improving in server email security. Almost every major email provider and most popular email server distributions support TLS nowadays. I could send an email from any of my servers to my Gmail account and know that it would be safely transmitted.
If you're not certain about the mail servers involved, it's definitely safer to use https.
2. A server-side app can definitely impact PCI compliance if it's not securing data properly.
3. I agree it's still not a good idea to not send sensitive data over email but I would just add that things are dramatically improving in server email security. Almost every major email provider and most popular email server distributions support TLS nowadays. I could send an email from any of my servers to my Gmail account and know that it would be safely transmitted.
If you're not certain about the mail servers involved, it's definitely safer to use https.