STE WILLIAMS

Tech Insight: Defending Point-of-Sale Systems

Jan
25

Major hacks at retailers that include Target and Neiman Marcus have put a new spotlight on the security of point of sale (POS) systems. What may come as a surprise to some is that the memory-scraping malware attacks were nothing new. Last year, Visa published two “Visa Data Security Alerts” warning merchants of an increase in attacks targeting credit card data with specific references to memory-scraping malware.

The alerts were published in April and August. The first stated that Visa has seen an increase in network intrusions involving grocery merchants since January 2013. August’s update used nearly the same verbiage but mentioned retail instead of grocery. The part that’s of particular interest is how the attackers were carrying out the attacks.

“Once inside the merchant’s network, the hacker will install memory parser malware on the Windows based cash register system in each lane or on Back-of-the-House (BOH) servers to extract full magnetic stripe data in random access memory (RAM).”

With two notices earlier in the year, retailers breached in the 4th quarter had early notification that attacks specifically targeting POS systems had been seen increasing. The alerts from Visa even included details on how to protect POS and related PCI systems from the types of attacks being carried out. So how is it that companies who were considered PCI compliant had their POS devices and PCI environment compromised?

From a penetration tester’s perspective, it is all too common to find merchants considered compliant as not necessarily secure. As an industry, we’ve been saying for years that compliance does not equal security and these big data breaches are classic examples. It is easy to fill out a form that certain controls are in place, but the harsh reality is that rarely are those controls actually tested thoroughly to ensure their effectiveness at protecting cardholder data.

US CERT, part of the Department of Homeland Security, issued Alert TA14-002A on January 2, 2014 titled “Malware Targeting Point of Sale Systems.” The document discusses hardware and software attacks against POS systems and includes specific recommendations on protecting them. Unlike the Visa Alerts, US CERT has put together guidance that focuses specifically on security best practices without mentioning specialized hardware and software (i.e. EMV-enabled PIN-entry, SRED-enabled devices, PA-DSS compliant payment applications).

Alert TA14-002A targets 6 areas that POS administrators should follow:

Use Strong Passwords: During the installation of POS systems, installers often use the default passwords for simplicity on initial setup. Unfortunately, the default passwords can be easily obtained online by cybercriminals. It is highly recommended that business owners change passwords to their POS systems on a regular basis, using unique account names and complex passwords.

Default passwords are the low-hanging fruit that penetration testers tend to go for first. It’s amazing how often network devices and application servers are set up on a network with default passwords in place. Whether it’s an administration interface for Apache Tomcat or something like HSRP for Cisco routers, it’s difficult to find a network that doesn’t have at least one system with a default password. A vulnerability scanner like Nessus or NeXpose can help with finding these default passwords, but manual verification should be done also, as vulnerability scanners don’t have the default passwords for every device.

Update POS Software Applications:Ensure that POS software applications are using the latest updated software applications and software application patches. POS systems, in the same way as computers, are vulnerable to malware attacks when required updates are not downloaded and installed on a timely basis.

Keeping POS applications updated should be part of the patch management strategy for every merchant. The common hurdle is that new versions generally cost money, which causes companies to avoid upgrades until technical problems arise. While the risks to POS software can sometimes be mitigated through other security controls like host intrusion prevention software (HIPS) and firewalls, it’s important that merchants remember that new versions also bring security and bug fixes that can help keep cardholder data safe — they’ll need to bite the bullet eventually and upgrade.

Install a Firewall: Firewalls should be utilized to protect POS systems from outside attacks. A firewall can prevent unauthorized access to, or from, a private network by screening out traffic from hackers, viruses, worms, or other types of malware specifically designed to compromise a POS system.

A key tenet of the PCI DSS is network segmentation and firewalls are essential. Host- and network-based firewalls should be utilized as part of a layered security approach. Traffic should only be allowed to and from the POS to systems that are similarly hardened against attack. Where possible, the traffic should also be monitored by an intrusion detection/prevention system to detect and/or prevent attacks.

Use Antivirus: Antivirus programs work to recognize software that fits its current definition of being malicious and attempts to restrict that malware’s access to the systems. It is important to continually update the antivirus programs for them to be effective on a POS network.

US-CERT is on target with its advice to use updated antivirus, but anti-malware protections should not stop there. Merchants should consider implementing a full endpoint protection suite that includes antivirus, HIPS, firewall, traffic inspection, and application whitelisting. While these solutions are not foolproof, they raise the bar for exploitation considerably.

Restrict Access to Internet: Restrict access to POS system computers or terminals to prevent users from accidentally exposing the POS system to security threats existing on the Internet. POS systems should only be utilized online to conduct POS-related activities and not for general Internet use.

Unless the POS application specifically needs Internet access, then it should be completely firewalled off from the Internet. In the situation that the POS software does need to communicate with systems on the Internet, firewalls should be used to strictly block all traffic except that to authorized systems. Application proxies should be used to proxy and inspect traffic to and from the Internet.

Disallow Remote Access: Remote access allows a user to log into a system as an authorized user without being physically present. Cybercriminals can exploit remote access configurations on POS systems to gain access to these networks. To prevent unauthorized access, it is important to disallow remote access to the POS network at all times.

This is the only area of advice from US-CERT that might be considered overkill, as it’s going to make authorized remote management impossible. With proper firewall configurations restricting access only to authorized management workstations and multi-factor authentication, remote access is perfectly acceptable. Of course, this is where companies get in trouble as they aren’t always diligent in ensuring firewalls configurations are correct and the machines accessing them are secured.

POS systems are not difficult to secure if merchants would simply follow the advice that has been put out by Visa and the US-CERT. Most of the advice is based on security best practices that have been around for years. Unfortunately, it often takes a data breach for companies to have their eyes opened to the impact their negligence can have on their customers and their brand. Will Target, Neiman Marcus, and other retailers’ recent troubles be the impetus companies need to secure their systems or will they have to experience it firsthand?

Have a comment on this story? Please click “Add Your Comment” below. If you’d like to contact Dark Reading’s editors directly, send us a message.

Article source: http://www.darkreading.com/attacks-breaches/tech-insight-defending-point-of-sale-sys/240165629

Comments

Comments are closed.