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.

5 Ways To Think Outside The PCI Checkbox
Newest First  |  Oldest First  |  Threaded View
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
9/23/2014 | 10:13:32 AM
Re: Checkbox mentality > Roadmap v Best Practices
Thanks for the example, @gabehernandez9. I'd love to hear more from the Dark Reading community about their advice and tactics for navigating DSS.
User Rank: Apprentice
9/23/2014 | 9:19:34 AM
Re: Checkbox mentality > Roadmap v Best Practices
A roadmap need not be overly detailed with specific turn-by-turn steps.  It could be a composed of a series of sucessive milestones to help you on your way.  For example, a key tenant of PCI environments is the concept of "isolation".  Why not have a tactical and practical guide to explain typical steps to achive isolation at the network layer...something like this.

1. Create an inventory of all IP-enable devices that are part of a PCI environment

2. Create a separate environment (ideally physical with separate routers, switches, firewals etc, but must be logically separate) to host and enable the functionality of those PCI assets isolated from the coporate LAN

3. Apply the following hardening and access restrictions to the edge of the new PCI network in accordance with DSS section blahblahblah

4. Migrate the previously defined PCI assets to the new network.

4. Train network personnel how to access and support the new envionment with strong emphasis in maintainng isolation from coporate LAN systems and services.


And so on....


This is admittedly a very simplistic example but not far from what I've had to do multiple times with assorted teams to help them navigate the DSS.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
9/22/2014 | 12:17:21 PM
Re: Checkbox mentality > Roadmap v Best Practices
Are we splitting hairs about the difference between a road map and a best practices? Yes, best practices may be overly generic to be particularly useful. But on the other hand, a roadmap view with turn by turn directions might be too specific to be of value to various industry segments, or companies of different sizes. 
User Rank: Moderator
9/22/2014 | 11:03:12 AM
Re: Checkbox mentality
I agree, in some ways, perhaps having a recommendations guide where organizations can benchmark against what other industry folks are doing would help.  In many cases, PCI seems overly daunting, especially for small and mid sized organizations, so having better guidance on "here's some examples of what companies are doing to check off those boxes" would help, or at least help prioritize the technologies/policies that would help reduce the overall threat gap and give folks a better idea where to start.
User Rank: Apprentice
9/22/2014 | 9:09:09 AM
Re: Checkbox mentality
Education is always valuable, but for my money the Council would increase it's value by providing a roadmap to help companies achieve compliance when starting from square one.  I've encountered a lot of frustration with the DSS, not because it sets some aggressive security standards, but because those standards don't provide enough guidance on getting there.  Admittedly, Standards are meant to only stipulate the "What" as far as Security controls objectives to meet, but we could all use a lot more help with the "How" of getting there.  Not necessarily with a list of products or tools, but a cohesive tactical roadmap template that any businees can use and modify (within reason) to get to the compliance finish line.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
9/22/2014 | 8:16:09 AM
Checkbox mentality
It's hard to argue with any effort that will up the card industry's game when it comes to data security. But I don't think education alone will turn the tables. The problems run deeper than an attitude shift and a new set of of best practices. Thoughts anyone?


I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
The 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.