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

5 Updates from PCI SSC That You Need to Know

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

Programs Open for Software Security Framework Assessors in October

Starting October, the PCI Security Standards Council will start accepting applications from companies and individuals that are interested in becoming payment software security assessors under the Council's new Software Security Framework (SSF).
The assessors will be responsible for ensuring that vendors are compliant with the requirements of the Secure Software Lifecycle standard and that their software meets the requirements of the Secure Software standard.

PCI SSF is a set of standards and programs for payment card security that will replace the current Payment Application Data Security Standard (PA DSS) in 2022. The SSF will incorporate elements of PA DSS as well as standards and approaches for a broader array of payment software, technologies, and development methods. The Council has described the SSF as embodying a new approach for ensuring the security of new and emerging payment software and channels.

'Goals for the Software Security Framework include allowing for more agility in the security testing, expanding the potential types of applications that go through validation, increasing application developer awareness of payment security design and accountability,' says Troy Leach, CTO of PCI SSC, in comments to Dark Reading.

Covered entities will eventually need to ensure their software is validated to SSF requirements if they want to remain compliant with PCI requirements. But that won't happen immediately. To minimize disruption, the Council will run the SSF in parallel with PA-DSS for some time. Applications will continue to be accepted for PA-DSS validation through mid-2021, according to the Council.



Image source: Troy Leach, CTO, PCI SSC

Programs Open for Software Security Framework Assessors in October

Starting October, the PCI Security Standards Council will start accepting applications from companies and individuals that are interested in becoming payment software security assessors under the Council's new Software Security Framework (SSF).

The assessors will be responsible for ensuring that vendors are compliant with the requirements of the Secure Software Lifecycle standard and that their software meets the requirements of the Secure Software standard.

PCI SSF is a set of standards and programs for payment card security that will replace the current Payment Application Data Security Standard (PA DSS) in 2022. The SSF will incorporate elements of PA DSS as well as standards and approaches for a broader array of payment software, technologies, and development methods. The Council has described the SSF as embodying a new approach for ensuring the security of new and emerging payment software and channels.

"Goals for the Software Security Framework include allowing for more agility in the security testing, expanding the potential types of applications that go through validation, increasing application developer awareness of payment security design and accountability," says Troy Leach, CTO of PCI SSC, in comments to Dark Reading.

Covered entities will eventually need to ensure their software is validated to SSF requirements if they want to remain compliant with PCI requirements. But that won't happen immediately. To minimize disruption, the Council will run the SSF in parallel with PA-DSS for some time. Applications will continue to be accepted for PA-DSS validation through mid-2021, according to the Council.

Image source: Troy Leach, CTO, PCI SSC

2 of 6
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...