DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

POSitouch mfgr responds to lawsuit threat claims

Posted on May 28, 2010 by Dissent

Earlier this week, I posted a press release about a potential lawsuit against POSitouch and its New Jersey reseller, CC Productions. I contacted both POSitouch and the reseller to ask for a response, and POSitouch has just sent me a press release that they issued today. I have not heard back from their reseller.

I will have more to report on this case next week, as I am in the process of talking to parties on both sides of the dispute, but for now, here is POSitouch’s press release:

Facts Not Hype Will Prevail for Popular POS Software Manufacturer

Restaurant Data Concepts, Inc. will vigorously defend itself if pending litigation comes to fruition. The company and its product have been PCI certified since the inception of these industry standards.

The credit card industry has been imposing new PCI standards for protecting cardholder data from theft over 5 years. Card processors have added provisions to their contracts with merchants that require them to secure cardholder data in all forms and also makes the merchant responsible for stolen card numbers.

In response to the emerging PCI standards for protecting cardholder data, Restaurant Data Concepts changed its approach to handling credit cards in 2005. “We got completely out of the business of storing cardholder data permanently. We simply stopped storing any card processing information altogether,” says Peter Lipman, CTO of RDC, the manufacturer of the POSitouch restaurant POS application. For users of the POSitouch application that purchased prior to the existence of PCI standards, updates have been available to meet these requirements.

However, installing PCI compliant software is only one small piece of the merchant’s responsibility to meet their contracted obligation with their card processor. Securing their computer system’s network with commercial grade firewalls, using properly supported operating systems, vigorous password controls and cleaning data accumulated from the pre-PCI era would be some of the more important steps the merchant must implement.

According to Mr. Lipman, “as a software manufacturer we are required not only to make our software PCI compliant, but to provide documentation and tools to help a merchant comply with the new requirements.” RDC has been an early adopter of these PCI requirements and has even taken the level of security it offers beyond the scope imposed to meet these regulations. “We worked with our PCI auditor to create documentation for our resellers and their end users to assist in implementing these upgrades. As part of our certification, we also provide tools that can be used to purge pre-existing cardholder data.” Restaurant Data Concepts and its POSitouch application are certified as PCI compliant and continue with that designation.

Ultimately the requirement for PCI compliance is spelled out in the contract between the merchant and the card processor. It is not overly difficult or expensive for a merchant to protect themselves against theft of cardholder information, but they should contract with a qualified professional to assist them. A small expenditure to upgrade and secure their system can stave off significant costs and penalties from their card processor should they be subject to a breach. It is hoped that the card processing industry will find better ways to inform their merchants of the seriousness of the situation and help them obtain the technical assistance they may need to meet the requirements that they have placed upon their merchant/customer.

Category: Breach IncidentsU.S.

Post navigation

← FTC Extends Enforcement Deadline for Identity Theft Red Flags Rule
IN: Clinic owner filing suit against doctor-registration law →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • AT&T gets preliminary approval for $177 million data breach settlement
  • Aflac notifies SEC of breach suspected to be work of Scattered Spider
  • Former JBLM soldier pleads guilty to attempting to share military secrets with China
  • No, the 16 billion credentials leak is not a new data breach — a wake-up call about fake news
  • Tonga’s health system hit by cyberattack (1)
  • Russia Expert Falls Prey to Elite Hackers Disguised as US Officials
  • Proposed class action settlement in In re Netgain Technology litigation
  • Qilin Offers “Call a lawyer” Button For Affiliates Attempting To Extort Ransoms From Victims Who Won’t Pay
  • Ireland’s Data Protection Commission publishes 2024 Annual Report
  • The headlines suggested Freedman Healthcare suffered a ransomware attack that affected patient data. The reality was quite different.

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data
  • US Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.