Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

12/6/2007
12:00 PM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

Credit Card Security: 'Tis The Season To Be Compliant

When it comes to customers' credit card information, how much should small and midsize businesses be worrying about compliance this holiday season? The same as every other season -- a lot.

When it comes to customers' credit card information, how much should small and midsize businesses be worrying about compliance this holiday season? The same as every other season -- a lot.While the credit card information compliance standards, requirements and regs have traditionally been seen as most applicable to bigbiz retailers, the rules are increasingly being extended (and interpreted) to cover small and midsize businesses.

Not long ago in bMighty, Matthew Schwartz named regulatory/standards compliance as one of the Top 10 Emerging Security Trends. Admittedly, he placed compliance at number 10 -- but also made clear that achieving compliance when handling credit card information was going to move up the small and midsize business concerns list pretty quickly.

Which implies if not requires that you start getting your compliance act together now, if you haven't already.

Problem is, the Payment Card Industry Data Security Standard (PCI DSS) was clearly -- and admittedly -- put together by some of the biggest names in the banking, credit and financial industries, and it shows in the bureaucratic prose that spells out what the standard requires of companies accepting credit card transactions. Just reading your way through the various elements of the standard can take awhile -- implementing them can take awhile longer.

But if you take a look at this outline of those PCI DSS requirements you'll see that most of them involve measures and technologies that you (and your credit transaction processing firm even more so) should already have in-place and in-practice: firewalls, data protection and encryption, antivirus software that's regularly updated, restricted access to credit card data, a written security policy.

Those last two may be where you and your business need to raise your guard even higher: we've talked about here before, and often, lax (and, too often, nonexistent) access standards and requirements, not to mention unwritten security policies.

Yet of all the PCI DSS requirements these two are the most easily -- not effortlessly -- implemented. And if you put teeth in your policy -- requiring employee signatures as well as adherence, backing the policy with promise of termination or, if necessary, prosecution -- you'll have taken a large step toward both compliance and better business practice.

The point, I think, for small and midsize businesses isn't whether or not compliance requirements and regulations apply to you. We all live in the same world, where it's a fairly safe bet that if a reg or compliance stadard doesn't apply now it will tomorrow.

The point is that PCI DSS is, at heart, a set of commonsense rules and security tools that any serious business of any size should put in place, regularly monitor and update, and stay on top of for business reasons, not "fear of compliance violation" reasons.

Of course, if fear of violations actually gets some businesses to take action on the policy and access front, well, it won't be the first time that compliance was pursued for reasons of self-protection as well as customer protection.

The PCI Security Council's homepage is here.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7029
PUBLISHED: 2020-08-11
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging. This vulnerability could allow an unauthenticated remote attacker to perform Web administration actions with the privileged ...
CVE-2020-17489
PUBLISHED: 2020-08-11
An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible f...
CVE-2020-17495
PUBLISHED: 2020-08-11
django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.
CVE-2020-0260
PUBLISHED: 2020-08-11
There is a possible out of bounds read due to an incorrect bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-152225183
CVE-2020-16170
PUBLISHED: 2020-08-11
The Temi application 1.3.3 through 1.3.7931 for Android has hard-coded credentials.