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.

Comments
Checkers Breach Underscores Continued POS Dangers
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
6/3/2019 | 2:05:03 PM
Re: Protection Profiles for PoS
Less technical notes - many POS devices years ago had an XP version called 'Embedded" - never had a chance to work on one of these different systems but I wonder who was in control - who supported them?  I presume the retail store itself or parent firm has a support conract and how often, and this is frightening, do their staff visit a retail store for upgrades and review.  Never knew.  Kroger has POS stations of course and about 2 yeas ago they were upgraded from (god forbid) Windows NT ----- true, I recongized the OS screen easy ---- to Windows 7 and that was a nightmare for 2 weeks.  Again - WHO supports these devices.  And Every Kroger has four of them.  I have seen in Atlanta internet attached parking meters!!!   True - debit card, swipe and there you go.  
RetiredUser
100%
0%
RetiredUser,
User Rank: Ninja
6/1/2019 | 3:07:35 PM
Protection Profiles for PoS
In a 2014 paper on PoS protection profiles [1] the authors point to the failure of PoS companies in general to comply to any given standard (including, I assume, the EMV) or, despite trying to comply, still end up getting hacked.  There is no guarantee of security when an organization uses a standard such as EMV; failure points exist across the PoS ecosystem, not just at a single point.  The paper focuses instead on a protection profile for PoS based on Common Criteria (CC) with the goal of developing security functional requirements for PoS systems that are more robust, more likely to produce a secure PoS system and are not limited to a specific country's standard for security, but drawn from an international standard (ISO/IEC 15408).  While many standards from each country who have written them for PoS security reference or draw from CC, the importance of having mandatory security functional requirements based on the CC (ISO/IEC 15408) that are NOT rooted in any one country's interpretation or implementation is critical to higher levels of PoS security globally.  As the paper concludes, this aids in making the most objective evaluation of the security of a PoS system possible.   

[1] Lee HJ., Lee Y., Won D. (2014) Protection Profile for PoS (Point of Sale) System. In: Park J., Adeli H., Park N., Woungang I. (eds) Mobile, Ubiquitous, and Intelligent Computing. Lecture Notes in Electrical Engineering, vol 274. Springer, Berlin, Heidelberg


DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3349
PUBLISHED: 2019-11-19
lightdm before 0.9.6 writes in .dmrc and Xauthority files using root permissions while the files are in user controlled folders. A local user can overwrite root-owned files via a symlink, which can allow possible privilege escalation.
CVE-2019-10080
PUBLISHED: 2019-11-19
The XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI ...
CVE-2019-10083
PUBLISHED: 2019-11-19
When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.
CVE-2019-12421
PUBLISHED: 2019-11-19
When using an authentication mechanism other than PKI, when the user clicks Log Out in NiFi versions 1.0.0 to 1.9.2, NiFi invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to m...
CVE-2019-19126
PUBLISHED: 2019-11-19
On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR ...