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 //

Compliance

11/12/2019
05:15 PM
50%
50%

Companies Increasingly Fail Interim Security Test, But Gap Narrows

Stability of PCI DSS helps companies cope and create more mature security programs, but some parts of the Payment Card Industry's Data Secure Standard continue to cause headaches.

The share of companies passing their interim security tests under the Payment Card Industry's Data Security Standard (PCI DSS) — a practice run to help firms meet full compliance — dropped to 37% in 2018, the lowest level in five years, according to Verizon's "2019 Payment Security Report," published Nov. 12.

The decline in successful interim security audits is steep. In 2016, more than half of companies — 55% — taking a practice run through the painful compliance process mandated by PCI DSS passed the interim compliance audit. The ability to pass the assessment is a measure of the stability of a company's compliance processes and security controls, says Ciske Van Oosten, senior manager of global intelligence for Verizon's Security Assurance Consulting practice.

In the past, companies seemed on a path to improving their processes every year, but after 2016, companies started failing more often, Van Oosten says.

"We thought the growth was going to continue forever," he says. "But we now see that full compliance needs to be sustainable in the long term and not just at a point in time."

The news is not all bad. While a smaller share of companies maintained their security controls between compliance tests, the amount by which the average company fell out of compliance remained stable or declined. In 2018, the average gap between full compliance and the interim assessment for companies that failed to pass was about 10%, six percentage points less than four years ago, Van Oosten says.

The quarterly interim testing helps companies identify places where they have fallen out of compliance with security requirements and gives them a chance to fix the issues before the actual compliance testing.

"Organizations are required to not only achieve 100 percent full compliance with the PCI DSS, but also to maintain it," the report stated. "This means having all applicable security controls continuously in place and functioning as intended."

The Payment Card Industry's compliance regime has been a major headaches for companies, requiring significant amounts of investment and resources. Yet with breaches continuing to plague businesses and third-party risk becoming much more of a concern, PCI DSS has become the preferred way to test whether partners and vendors are meeting their security obligations, Van Oosten says.

"We had a lot of attention in the media [in the past], but that is not driving the attention on compliance," he says. "The driver for PCI DSS seems to be business to business, where a company will not do business with a partner unless they can show that they handle the data correctly."

The reason for the decline over the past two years in interim compliance is not obvious, says Van Oosten.

The PCI DSS requirements organizations most often failed to maintain include No. 11 ("Test Security Systems and Process"), No. 6 ("Develop and maintain secure systems"), and No. 8 ("Authenticate access"). A third of companies — the largest portion — failed to run regular network and vulnerability scans (requirement 11.2), according to Verizon's report. Twenty-eight percent of companies failed to protect software components and applications from known vulnerabilities (requirement 6.2), and 27% failed to recheck security control flagged by penetration testing to ensure that issues were fixed (requirement 11.3.3).

"The largest compliance drop occurred against Requirement 6, as organizations struggled to maintain effective vulnerability management, software development and change processes," the report stated. "It is then perhaps not too surprising that Requirement 11 remained the poorest performer—both in overall compliance and control gap—as organizations struggle to sustain compliance with security testing requirements year after year."

Van Oosten urged companies to have a security program in place to guide the implementation of necessary security controls. In addition, companies need to have a way of generating metrics to measure their progress in implementing the controls, he says.

"Security controls are all that stand between you and attackers out there on the Internet," Van Oosten says. "You need to manage PCI-DSS compliance as a program."

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "What a Security Products Blacklist Means for End Users and Integrators."

Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: George has not accepted that the technology age has come to an end.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-28466
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
CVE-2021-27364
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.
CVE-2021-27365
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length...
CVE-2021-27363
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. A kernel pointer leak can be used to determine the address of the iscsi_transport structure. When an iSCSI transport is registered with the iSCSI subsystem, the transport's handle is available to unprivileged users via the sysfs file system...
CVE-2021-26294
PUBLISHED: 2021-03-07
An issue was discovered in AfterLogic Aurora through 7.7.9 and WebMail Pro through 7.7.9. They allow directory traversal to read files (such as a data/settings/settings.xml file containing admin panel credentials), as demonstrated by dav/server.php/files/personal/%2e%2e when using the caldav_public_...