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.

Attacks/Breaches

2/25/2009
04:31 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Heartland CEO Provides More Details On Big Data Breach

Heartland chairman and CEO Bob Carr talks about breach during quarterly earnings call

Heartland Payment Systems' top executives on Tuesday shed more light on the firm's massive data breach, and said that Heartland would fight ensuing lawsuits stemming from the incident.

In an earnings call, the transcript of which has been posted online as well as summarized in the firm's fourth quarter 2008 financial report, Heartland chairman and CEO Bob Carr said the malware that infected the firm's systems could read and collect unencrypted data in motion, and that the attackers may have been able to "trade" from its network some of the data that was accessed.

"Keep in mind that Heartland passed its PCI certification last April, and assessors are currently on-site for 2009 certification, which we are targeting to begin to complete by the end of April. In that regard, throughout the potential period of the breach, Heartland did have antivirus software installed on its payment processing network," Carr said.

Heartland, which processes 100 million payment card transactions per month for 175,000 merchants, announced on Jan. 20 that it had discovered malware on its processing system. Security experts say this may be the largest ever data breach. A second, as-yet undisclosed payment processor has also suffered a big breach, according to several credit union organizations.

Carr said Heartland thinks the malware was not always active on its servers. "And [it] was probably not gathering information from 100 percent of transactions flowing through the system even when active or exporting all of the captured information to the criminals," he said. "For this reason, it is simply not possible at this time to determine accurately the number of card accounts that had information placed at risk of compromise during the breach, or to what extent any such information placed at risk was, in fact, compromised."

Carr noted that while PCI provides some security, data in motion also must be encrypted. The company previously had announced its plans to spearhead an end-to-end encryption effort in the payment industry. "To this end we have formed an internal department dedicated exclusively to the development of end-to-end encryption, designed to protect merchant and consumer data use and financial transactions," Carr said.

Heartland considers end-to-end encryption to encompass "the point of card swipe or data entry by a hardware appliance with the encrypted data flowing through all the gateways and communication links to the front-end authorization in data capture switch," he said. Data also must be encrypted between the front-end and back-end processing systems, in transit as well as at rest, he said.

Robert Baldwin, president and CFO of Heartland, also said that the company was "the subject to several governmental investigations and inquiry, including an informal inquiry by the SEC and a related investigation by the Department of Justice, an inquiry by the OCC [Office of the Comptroller of the Currency], and an inquiry by the FTC."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Florida Town Pays $600K to Ransomware Operators
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/20/2019
Pledges to Not Pay Ransomware Hit Reality
Robert Lemos, Contributing Writer,  6/21/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12280
PUBLISHED: 2019-06-25
PC-Doctor Toolbox before 7.3 has an Uncontrolled Search Path Element.
CVE-2019-3961
PUBLISHED: 2019-06-25
Nessus versions 8.4.0 and earlier were found to contain a reflected XSS vulnerability due to improper validation of user-supplied input. An unauthenticated, remote attacker could potentially exploit this vulnerability via a specially crafted request to execute arbitrary script code in a users browse...
CVE-2019-9836
PUBLISHED: 2019-06-25
Secure Encrypted Virtualization (SEV) on Advanced Micro Devices (AMD) Platform Security Processor (PSP; aka AMD Secure Processor or AMD-SP) 0.17 build 11 and earlier has an insecure cryptographic implementation.
CVE-2019-6328
PUBLISHED: 2019-06-25
HP Support Assistant 8.7.50 and earlier allows a user to gain system privilege and allows unauthorized modification of directories or files. Note: A different vulnerability than CVE-2019-6329.
CVE-2019-6329
PUBLISHED: 2019-06-25
HP Support Assistant 8.7.50 and earlier allows a user to gain system privilege and allows unauthorized modification of directories or files. Note: A different vulnerability than CVE-2019-6328.