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.

Application Security

9/25/2019
12:00 PM
Jai Vijayan
Jai Vijayan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

5 Updates from PCI SSC That You Need to Know

As payment technologies evolve, so do the requirements for securing cardholder data.
Previous
1 of 6
Next

Image source: PCI SSC

Image source: PCI SSC

More than 1,300 stakeholders from across the payments industry convened in Vancouver this month for the Payment Card Industry Security Standards Council's (PCI SSC) North America Community Meeting.

Key topics on the agenda included a new security standard for contactless payments on off-the-shelf mobile devices, development of the next major version of the PCI Data Security Standard, and a soon-to-be released new version of the PCI standard for point-to-point encryption (P2PE). Also announced at the Vancouver event was a new Security Framework that will guide the PCI Security Council's standards and decision-making processes in the years ahead.

Much of the focus of the initiatives is on extending PCI security standards to new and emerging payment technologies such as contactless payments on mobile devices. Under the new Strategic Framework, stakeholders will have more of a say in how standards for payments security evolve in coming years. Increasingly, the focus is on ensuring organizations meet the intent and objectives of the PCI security standard and not just on whether they have the recommended controls in place or not.

For well more than a decade, all organizations handling payment card data, both directly and indirectly, have had to comply with PCI DSS. The standard — developed by MasterCard, Visa, American Express, Discover, and JCB — prescribes a set of security requirements for protecting credit and debit card data.

The controls are designed to ensure that organizations handling payment card data have secure networks and systems, secure payment applications, strong access control mechanisms, and a robust vulnerability management program and that they regularly test and monitor their networks for security issues. Numerous companies that have experienced payment card data breaches in recent years have had to pay fines and face other consequences for failing to comply with PCI requirements.

Here are five items that were on top of the agenda at the North America Community meeting in Vancouver.

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
I 'Hacked' My Accounts Using My Mobile Number: Here's What I Learned
Nicole Sette, Director in the Cyber Risk practice of Kroll, a division of Duff & Phelps,  11/19/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-13157
PUBLISHED: 2019-11-22
nsGreen.dll in Naver Vaccine 2.1.4 allows remote attackers to overwrite arbitary files via directory traversal sequences in a filename within nsz archive.
CVE-2012-2079
PUBLISHED: 2019-11-22
A cross-site request forgery (CSRF) vulnerability in the Activity module 6.x-1.x for Drupal.
CVE-2019-11325
PUBLISHED: 2019-11-21
An issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.
CVE-2019-18887
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. The UriSigner was subject to timing attacks. This is related to symfony/http-kernel.
CVE-2019-18888
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. T...