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

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
 

Recommended Reading:

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/30/2020
'Act of War' Clause Could Nix Cyber Insurance Payouts
Robert Lemos, Contributing Writer,  10/29/2020
6 Ways Passwords Fail Basic Security Tests
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How to Measure and Reduce Cybersecurity Risk in Your Organization
In this Tech Digest, we examine the difficult practice of measuring cyber-risk that has long been an elusive target for enterprises. Download it today!
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5425
PUBLISHED: 2020-10-31
Single Sign-On for Vmware Tanzu all versions prior to 1.11.3 ,1.12.x versions prior to 1.12.4 and 1.13.x prior to 1.13.1 are vulnerable to user impersonation attack.If two users are logged in to the SSO operator dashboard at the same time, with the same username, from two different identity provider...
CVE-2020-15703
PUBLISHED: 2020-10-31
There is no input validation on the Locale property in an apt transaction. An unprivileged user can supply a full path to a writable directory, which lets aptd read a file as root. Having a symlink in place results in an error message if the file exists, and no error otherwise. This way an unprivile...
CVE-2020-5991
PUBLISHED: 2020-10-30
NVIDIA CUDA Toolkit, all versions prior to 11.1.1, contains a vulnerability in the NVJPEG library in which an out-of-bounds read or write operation may lead to code execution, denial of service, or information disclosure.
CVE-2020-15273
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. The issue affects the following components: Edit feed settings, Edit widget area, Sub site new registration, New category registration. Arbitrary JavaScript may be executed by entering specific characters in the account that can ac...
CVE-2020-15276
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. Arbitrary JavaScript may be executed by entering a crafted nickname in blog comments. The issue affects the blog comment component. It is fixed in version 4.4.1.