Is being PCI DSS-compliant enough to protect customer data?

Even if your company is PCI DSS-compliant, it could still fall prey to hackers seeking to exploit customer info. Discuss how to keep data safe in this month's #GRCchat.

It's hard to muster more than a weary sigh when news of the latest large-scale credit-card breach breaks. But what's worse than seeing the news of another company's misfortune flash across your Twitter feed? When it's your own organization that's fallen prey to a data hack.

The Payment Card Industry Data Security Standard (PCI DSS) is a widely accepted set of procedures aimed at optimizing the security of credit and debit card transactions. It's intended to protect cardholders -- and the companies that maintain their payment data -- against the misuse of their personal information. But even companies in compliance with PCI DSS can still be victims of theft, as the recent hacks at Home Depot and Target have made clear. So beyond legal compliance, what more can your company do to keep its point-of-sale customer information safe?

Join SearchCompliance on Twitter Thursday, Oct. 16, at 12 p.m. EDT to whether PCI DSS compliance is enough to secure customer data and other strategies to protect personal information. SearchCompliance editors will lead the chat from the site's Twitter handle, @ITCompliance, joined by other TechTarget writers, editors and experts.


Date: Thursday, Oct. 16, 2014
Time: 12 p.m. EDT
Host: @ITCompliance
Hashtag: Use and follow #GRCchat

Is this your first #GRCchat? Whether you're a newbie or returning tweet jammer, read the following pointers before signing on:

To follow the conversation, type "#GRCchat" into Twitter's search bar. From this page, select "All" to view tweets in real time.

Your first #GRCchat tweet should be introductory, including your name, title and organization.

@ITCompliance will ask a series of questions related to PCI DSS and customer data, starting at 12 p.m. EDT (Q1, Q2, etc.). In your tweeted responses to each question, please preface with A1 (Answer 1), A2 and so on, then remember to include "#GRCchat". Each tweet sent during the chat should include the hashtag.

Please note that Twitter allows only 140 characters per tweet. You are welcome to tweet multiple responses to each question (consider using format "1 of 2" or "1/2" to identify there is more)

Throughout the discussion, retweet (RT) and favorite tweets you agree with and reply to those you don't.

Please direct questions, RSVPs or other concerns to SearchCompliance Editor Ben Cole. "See" you on Twitter!

Next Steps

Read recaps from recent tweet chats on how big data has affected e-discovery management and why new mobile data access points are complicating compliance strategies.

Dig Deeper on PCI compliance

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

Is being PCI DSS-compliant enough to protect customer data?