We have added a series of security measures and features to make the software successfully pass PCI compliance testing. For example, the CVV2 has an option not to be saved in the store database, the Credit Card Number can be encoded and truncated if required and all Control Panel activity is logged (2 of the requirements for PCI compliance).
However, please note that PCI compliance is also dependant on other elements that are an essential part of your e-commerce system. You need to sign up for PCI compliance testing with one of the companies that offer such kind of service. As far as we are aware there are a lot of such companies.
The software application, like ViArt Shop, cannot be PCI compliant by itself and therefore cannot automatically grant the status of "PCI Compliant" to a Web store with ViArt Shop. That is because PCI compliance refers to the entire e-commerce system that powers your store, including your Web hosting
environment and the payment gateway that is used for a credit card processing. The PCI compliance testing service that you sign up with will ask you questions about your entire e-commerce system (e.g. where you are hosted, which payment gateway you are using, etc.) and will take care of ensuring that
everything is compliant.
With kind regards,
ViArt Support Team
Greg (Guest)
15 Nov 2007 3:54 PM
Hello Anjula. At what level are all of the built-in security features available? I'm at 3.2 at this point. Were all your software changes present at release, or do I need to upgrade to 3.3 or add additional fixes? Thanks.
Denis (Guest)
21 Nov 2007 10:38 AM
Hello,
As you well understand, security issues need permanent control and development, as well as prompt reaction to new threats which appear worldwide every day.
We are doing our best to comply with the highest possible security standards. Our latest release 3.3.2 contains all up-to-date security improvements, and we recommend to always use the latest versions to face all software-dependent security requirements.
