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.

Endpoint

1/6/2014
10:55 AM
Doug Landoll
Doug Landoll
Commentary
50%
50%

3 Themes For Implementing PCI DSS 3.0 For SMBs

How the new PCI DSS v3.0 requirements affect the scope of cardholder data systems

2013 was not only a year of multiple major breaches exposing cardholder data (CHD) but also a year in which the Payment Card Industry Security Standards Council (PCI SSC) released the next major revision to the Payment Card Industry Data Security Standard: Version 3.0. PCI DSS v3.0 changes are largely aimed at misinterpretations and misapplications of requirements meant to reduce the risk of such attacks.

There are some "evolving requirements" (read: new requirements) in this new version, but mostly version 3.0 addresses a general lack of awareness and appropriate implementation of existing requirements. Small and medium businesses implementing PCI DSS typically do not require a Qualified Security Assessor (QSA) and either implement these requirements of their own or with the help of a security consultant. This series of blogs is aimed at those planning their 2014 PCI DSS strategy with 3 distinct and important themes found in PCI DSS 3.0.

PCI DSS 3.0 for SMBs Theme 1: Scope

The cardholder data environment (CDE) comprises all system components that a) store, process, or transmit CHD, b) any component that is directly attached to those systems, or c) any component that supports those systems. Element "a)" of the above definition has been well understood but proper segmentation of connected systems is often overlooked (element "b)") and supporting systems such as update servers and authentication support have been erroneously left out of the PCI DSS scope in many SMB PCI DSS scoping diagrams.

The result of an inaccurate PCI DSS scope is the misapplication of requirements, a non-compliant business, and a more susceptible environment. Understanding such misapplication of requirements is widespread; the PCI SSC specifically strengthened the guidance and requirements to address this. The following revisions to PCI DSS address the CHD scope issue:

Current Network Diagram – Really! [Requirement 1.1.2 – Clarification; Requirement 1.1.3 - New]

The Council went out of its way to explain that not only do you need a current network diagram with all connections to CHD but also one that identifies all connections between the cardholder data environment (CDE) and all other networks. This is an important exercise in determining the scope of your CDE and the applicability of PCI DSS requirements to your network components.

Inventory of System Components [Requirement 2.4 – New; Requirement 11.1.1 – New]

There is a new requirement to maintain a formal inventory of the system components within the CDE. The reason for this requirement is to ensure that configuration standards are applied to all CDE components. In many SMBs the inventory process can be worked in with the network diagram development, in more complex systems automated inventory process would be advisable. Another new requirement states that organizations must maintain an inventory of authorized wireless access points (including the business justification).

Penetration Testing – Verify Proper Segmentation [Requirement 11.3 – New; Requirement 11.3.4 - New]

There is a new requirement for a penetration testing methodology that (among other things) includes the testing of the segmentation and scope-reduction controls. Furthermore, a specific new requirement was created for annual penetration testing to verify that segmentation methods are operational and effective in isolating CDE system components from those components deemed out-of-scope.

Determine and Reduce your Scope Now.

The PCI DSS v3.0 standards are now in effect and organizations have until the end of the year to become compliant. Organizations have adequate time to address these new requirements but determining the proper scope of the CDE (and taking steps to reduce it) is the first step.

Doug Landoll CEO of Lantego Security, a firm specializing in assisting organizations with information security compliance (HIPAA, PCI, FISMA) and can be reached at [email protected] Doug Landoll is an expert in information security for the SMB market with over 20 years experience securing businesses and government agencies. He has written several information security books and dozens of articles for national publications. He has founded and ran four ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
FluBot Malware's Rapid Spread May Soon Hit US Phones
Kelly Sheridan, Staff Editor, Dark Reading,  4/28/2021
Slideshows
7 Modern-Day Cybersecurity Realities
Steve Zurier, Contributing Writer,  4/30/2021
Commentary
How to Secure Employees' Home Wi-Fi Networks
Bert Kashyap, CEO and Co-Founder at SecureW2,  4/28/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31793
PUBLISHED: 2021-05-06
An issue exists on NightOwl WDB-20-V2 WDB-20-V2_20190314 devices that allows an unauthenticated user to gain access to snapshots and video streams from the doorbell. The binary app offers a web server on port 80 that allows an unauthenticated user to take a snapshot from the doorbell camera via the ...
CVE-2021-31916
PUBLISHED: 2021-05-06
An out-of-bounds (OOB) memory write flaw was found in list_devices in drivers/md/dm-ioctl.c in the Multi-device driver module in the Linux kernel before 5.12. A bound check failure allows an attacker with special user (CAP_SYS_ADMIN) privilege to gain access to out-of-bounds memory leading to a syst...
CVE-2021-31918
PUBLISHED: 2021-05-06
A flaw was found in tripleo-ansible version as shipped in Red Hat Openstack 16.1. The Ansible log file is readable to all users during stack update and creation. The highest threat from this vulnerability is to data confidentiality.
CVE-2019-25043
PUBLISHED: 2021-05-06
ModSecurity 3.x before 3.0.4 mishandles key-value pair parsing, as demonstrated by a "string index out of range" error and worker-process crash for a "Cookie: =abc" header.
CVE-2020-18889
PUBLISHED: 2021-05-06
Cross Site Request Forgery (CSRF) vulnerability in puppyCMS v5.1 that can change the admin's password via /admin/settings.php.