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

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Exploiting Google Cloud Platform With Ease
Dark Reading Staff 8/6/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-8720
PUBLISHED: 2020-08-13
Buffer overflow in a subsystem for some Intel(R) Server Boards, Server Systems and Compute Modules before version 1.59 may allow a privileged user to potentially enable denial of service via local access.
CVE-2020-12300
PUBLISHED: 2020-08-13
Uninitialized pointer in BIOS firmware for Intel(R) Server Board Families S2600CW, S2600KP, S2600TP, and S2600WT may allow a privileged user to potentially enable escalation of privilege via local access.
CVE-2020-12301
PUBLISHED: 2020-08-13
Improper initialization in BIOS firmware for Intel(R) Server Board Families S2600ST, S2600BP and S2600WF may allow a privileged user to potentially enable escalation of privilege via local access.
CVE-2020-7307
PUBLISHED: 2020-08-13
Unprotected Storage of Credentials vulnerability in McAfee Data Loss Prevention (DLP) for Mac prior to 11.5.2 allows local users to gain access to the RiskDB username and password via unprotected log files containing plain text credentials.
CVE-2020-8679
PUBLISHED: 2020-08-13
Out-of-bounds write in Kernel Mode Driver for some Intel(R) Graphics Drivers before version 26.20.100.7755 may allow an authenticated user to potentially enable denial of service via local access.