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.

Vulnerabilities / Threats

7/14/2016
02:30 PM
Sean Martin
Sean Martin
Slideshows
Connect Directly
LinkedIn
RSS
E-Mail
50%
50%

What SMBs Need To Know About Security But Are Afraid To Ask

A comprehensive set of new payment protection resources from the PCI Security Standards Council aims to help small- and medium-sized businesses make security a priority.
Previous
1 of 9
Next

Image Source: imsmartin/PCI Council

Image Source: imsmartin/PCI Council

After more than 10 years making a name for itself as delivering a globally recognized industry standard, the PCI Security Standards Council (PCI SSC) recently launched a new set of payment protection resources for small businesses which has been appropriately called PCI Payment Protection Resources for Small Merchants. This is a timely launch, for sure, given the increased awareness and focus on third party vendor risk and the realities behind small- to mid-sized business security postures.

Furthering this point, the PCI SSC noted in a recent press release that small businesses around the world are increasingly at risk for payment data theft — and nearly half of cyberattacks worldwide in 2015 were against small businesses with fewer than 250 workers.

In response to this trend, and as a means to help small- to mid-sized business merchants protect their own data – as well as their customers’ data – the PCI SSC Small Merchant Taskforce developed the new set of payment protection resources.

Troy Leach, Chief Technology Officer for the PCI SSC, captures the essence of this delivery quite well by saying: “Small merchants often rely on their banks and their technology vendors for information on what’s needed to take card payments. For security to become a priority, it has to be part of that dialogue.”

 

Sean Martin is an information security veteran of nearly 25 years and a four-term CISSP with articles published globally covering security management, cloud computing, enterprise mobility, governance, risk, and compliance—with a focus on specialized industries such as ... View Full Bio

Previous
1 of 9
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
3Dmerchant
50%
50%
3Dmerchant,
User Rank: Guru
7/17/2016 | 10:41:14 AM
Good resource, but falls a little short
Note: Documents target SMALL merchants only, and includes some great resources. If looking for guidance, should comparative risk identify non-PCI compliant practices on nearly every slide? A chief complaint is risk profiles including "hard copy data, for example on paper receipts..." and "pin entry devices that are not PCI Compliant". To include that, maybe the report should be include color coding for non-PCI compliant elements (credit card numbers on receipts, pin entry devices),

Shortcomings:
  • What's not illustrated? What a P2PE solution looks like.
  • Type 14 Virtual Terminal Protections, for example, should add: Install browser, software, firewall patches; Use an encrypted Keypad.
  • Terminology: "Semi-integrated" is commonly being used by companies selling POS solutions. It's not in the Glossary, nor readily identifiable in the Payment system types at a glance. Too keep it simple for small businesses, it needs to be easier to figure out what they're comparing in real world.
Windows 10 Migration: Getting It Right
Kevin Alexandra, Principal Solutions Engineer at BeyondTrust,  5/15/2019
Artist Uses Malware in Installation
Dark Reading Staff 5/17/2019
Baltimore Ransomware Attack Takes Strange Twist
Kelly Jackson Higgins, Executive Editor at Dark Reading,  5/14/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12198
PUBLISHED: 2019-05-20
In GoHttp through 2017-07-25, there is a stack-based buffer over-read via a long User-Agent header.
CVE-2019-12185
PUBLISHED: 2019-05-20
eLabFTW 1.8.5 is vulnerable to arbitrary file uploads via the /app/controllers/EntityController.php component. This may result in remote command execution. An attacker can use a user account to fully compromise the system using a POST request. This will allow for PHP files to be written to the web r...
CVE-2019-12184
PUBLISHED: 2019-05-19
There is XSS in browser/components/MarkdownPreview.js in BoostIO Boostnote 0.11.15 via a label named flowchart, sequence, gallery, or chart, as demonstrated by a crafted SRC attribute of an IFRAME element, a different vulnerability than CVE-2019-12136.
CVE-2019-12173
PUBLISHED: 2019-05-18
MacDown 0.7.1 (870) allows remote code execution via a file:\\\ URI, with a .app pathname, in the HREF attribute of an A element. This is different from CVE-2019-12138.
CVE-2019-12172
PUBLISHED: 2019-05-17
Typora 0.9.9.21.1 (1913) allows arbitrary code execution via a modified file: URL syntax in the HREF attribute of an AREA element, as demonstrated by file:\\\ on macOS or Linux, or file://C| on Windows. This is different from CVE-2019-12137.