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

6/24/2009
07:56 PM
Dark Reading
Dark Reading
Products and Releases
50%
50%

PCI SSC Council Announces Feedback Period For PCI DSS

Between July 1 and Nov. 1, 2009, merchants, processors, financial institutions, and other key stakeholders can provide detailed and actionable feedback in an effort to revise future editions of the Council's standards to improve payment data security

WAKEFIELD, Mass., June 24, 2009 —The PCI Security Standards Council (PCI SSC), a global, open industry standards body providing management of the Payment Card Industry Data Security Standard (PCI DSS), PIN Entry Device (PED) Security Requirements and the Payment Application Data Security Standard (PA-DSS), today announced upcoming feedback opportunities that are part of the Council's transparent, standards management lifecycle process. During phase two of the lifecycle process, between July 1 and November 1, 2009, merchants, processors, financial institutions and other key stakeholders have the opportunity to provide detailed and actionable feedback in an effort to revise future editions of the Council's standards to improve payment data security.

This year the Council will roll out an online feedback tool to make it easier for organizations to prepare feedback on the PCI DSS and PA-DSS standards on up to five key areas of their choosing. This form will be distributed electronically on July 1 to the Council's more than 600 Participating Organizations. As part of the ongoing feedback process, the Council is also announcing the dates and locations for its annual Community Meetings, where stakeholders, such as retailers and banks, have an opportunity to proactively propose and discuss revisions to the next iteration of the Council's standards. The Council will host two events, one in North America and one in Europe, ensuring broad global discussion of the PCI security standards among stakeholders. Event dates and locations are:

North America: September 22-24, 2009 Mandalay Bay Las Vegas, Nevada Europe: October 26-28, 2009 Prague Marriott Prague, Czech Republic

The Community Meetings play a significant role in the Council's standards lifecycle management process and help foster broad debate on the evolution of PCI Standards. At the Community Meetings, attendees can participate in sessions focused on different industry, technology and geographical challenges to share their views and provide guidance. Attendees will also hear from industry experts on the latest issues surrounding payment card security and receive updates from the Council, as well as the Board of Advisors and the Council's Special Interest Groups, both made up of members chosen by the Council's Participating Organizations. The meetings will also include special sessions for Qualified Security Assessors (QSAs) and Approved Scanning Vendors (ASVs) as part of a pre-conference workshop on September 22 in North America and a post-conference workshop October 28 in Europe.

"The Community Meetings are the highlight of our year, where stakeholders from across the globe partner to evolve the PCI standards and work together toward a more secure payment environment," said Bob Russo, General Manager of the PCI Security Standards Council. "For the PCI Security Standards to continue to be effective in protecting cardholder data, we must continue to solicit and represent the voices of payment chain stakeholders worldwide. We do this through a structured, but flexible, lifecycle and feedback process that provides critical input on future PCI security standards."

During the Council's first feedback period, 150 organizations from around the world participated. Now, with more than 600 Participating Organizations, the Council expects a significant increase in global participants and a lively and thorough examination and discussion on the next version of PCI DSS and PA-DSS. This feedback will be managed in accordance with the PCI DSS Lifecycle, which ensures a planned and structured introduction of new standards and provides lead time for stakeholders to make any necessary changes to their systems. More information about the PCI DSS Lifecycle is available on the Council's Web site at https://www.pcisecuritystandards.org/pdfs/OS_PCI_Lifecycle.pdf.

Attendance at the PCI SSC sponsored Community Meetings is open to all current Participating Organizations, QSAs, ASVs and PED laboratories. Registration is complimentary for up to two named contacts at Participating Organizations and one complimentary registration for all others. Registration details for both meetings will be communicated to Council Participating Organizations in early July.

For More Information: For more information on the PCI Security Standards Council, please visit www.pcisecuritystandards.org or contact the PCI SSC Secretariat for any questions or concerns regarding the Community Meetings at [email protected]

About the PCI Security Standards Council The mission of the PCI Security Standards Council is to enhance payment account security by driving education and awareness of the PCI Data Security Standard and other standards that increase payment data security.

The PCI Security Standards Council was formed by the major payment card brands American Express, Discover Financial Services, JCB International, MasterCard Worldwide and Visa Inc. to provide a transparent forum in which all stakeholders can provide input into the ongoing development, enhancement and dissemination of the PCI Data Security Standard (DSS), PIN Entry Device (PED) Security Requirements and the Payment Application Data Security Standard (PA-DSS). Merchants, banks, processors and other vendors are encouraged to join as participating organizations.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15570
PUBLISHED: 2020-07-06
The parse_report() function in whoopsie.c in Whoopsie through 0.2.69 mishandles memory allocation failures, which allows an attacker to cause a denial of service via a malformed crash file.
CVE-2020-15569
PUBLISHED: 2020-07-06
PlayerGeneric.cpp in MilkyTracker through 1.02.00 has a use-after-free in the PlayerGeneric destructor.
CVE-2020-7690
PUBLISHED: 2020-07-06
It's possible to inject JavaScript code via the html method.
CVE-2020-7691
PUBLISHED: 2020-07-06
It's possible to use <<script>script> in order to go over the filtering regex.
CVE-2020-15562
PUBLISHED: 2020-07-06
An issue was discovered in Roundcube Webmail before 1.2.11, 1.3.x before 1.3.14, and 1.4.x before 1.4.7. It allows XSS via a crafted HTML e-mail message, as demonstrated by a JavaScript payload in the xmlns (aka XML namespace) attribute of a HEAD element when an SVG element exists.