September 8, 2016 By Larry Loeb 2 min read

Point-of-sale (POS) malware used to be limited to Verifone-style data terminals that were hardwired to a register at a retail establishment. That aspect of a point-of-sale data breach has changed drastically of late, with POS software moving to the cloud.

Point-of-Sale Data Breach Targets Mobile Database

Lightspeed, a POS provider that serves over 38,000 business clients, announced last Thursday that it had suffered a breach, CSO Online reported.

The breach affected a system that allows clients to connect via mobile devices. In a statement, the company said the attack targeted a database that stored specific client information regarding products, sales and encrypted passwords that can be used to access the system.

No Evidence of Stolen Data

In a worrisome development, the company said attackers also accessed electronic signatures that had gone through the POS software. However, the statement claimed there was no evidence that the data was stolen or otherwise used for criminal purposes.

“It’s worth noting that Lightspeed does not store credit card information, and therefore no cardholder data was compromised in this incident,” a company spokesman told CSO Online in an email.

If the customer data is safe, it may have been due to the company’s practice of encrypting its passwords at rest. In its statement, Lightspeed said it was using an “advanced encryption technology” that had been upgraded in January 2015.

Remediation Steps

The provider is taking remediation steps right now. It is limiting personal access to the company’s production infrastructure as well as its sensitive data. It’s always a good idea to keep as many hands off the production machines as possible.

In addition, the company is upgrading its security to detect more advanced attacks. It did not disclose which advanced attacks it thought were worth detecting.

Security frontiers and perimeters have changed over time. Even though user and customer data were protected to some degree, a breach was still possible. Perhaps Lightspeed’s threat model was incomplete or deficient in some area. The company obviously took steps toward hardening its system, since it encoded the credentials at rest.

Still, given the accessibility of customers’ e-signatures, there was obviously a vulnerability that was not detected. The whole affair illustrates the importance of re-evaluating the threat model continually, even when it seems a decent solution is already in place.

More from

Passwords, passkeys and familiarity bias

5 min read - As passkey (passwordless authentication) adoption proceeds, misconceptions abound. There appears to be a widespread impression that passkeys may be more convenient and less secure than passwords. The reality is that they are both more secure and more convenient — possibly a first in cybersecurity.Most of us could be forgiven for not realizing passwordless authentication is more secure than passwords. Thinking back to the first couple of use cases I was exposed to — a phone operating system (OS) and a…

DOD establishes Office of the Assistant Secretary of Defense for Cyber Policy

2 min read - The federal government recently took a new step toward prioritizing cybersecurity and demonstrating its commitment to reducing risk. On March 20, 2024, the Pentagon formally established the new Office of the Assistant Secretary of Defense for Cyber Policy to supervise cyber policy for the Department of Defense. The next day, President Joe Biden announced Michael Sulmeyer as his nominee for the role.“In standing up this office, the Department is giving cyber the focus and attention that Congress intended,” said Acting…

Unpacking the NIST cybersecurity framework 2.0

4 min read - The NIST cybersecurity framework (CSF) helps organizations improve risk management using common language that focuses on business drivers to enhance cybersecurity.NIST CSF 1.0 was released in February 2014, and version 1.1 in April 2018. In February 2024, NIST released its newest CSF iteration: 2.0. The journey to CSF 2.0 began with a request for information (RFI) in February 2022. Over the next two years, NIST engaged the cybersecurity community through analysis, workshops, comments and draft revision to refine existing standards…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today