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

11/10/2017
01:00 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

Customers Punish Breached Companies

Equifax's 25% reduction in share value and other industry-wide stats show that consumers aren't so apathetic about cybersecurity after all.

Many executives don't take secondary breach costs very seriously: the numbers have long been tricky to pin down and many within the C-suite believe that consumer breach fatigue and apathy about cybersecurity buffer their brand in the wake of a breach.

But growing evidence is showing that customers really do care, and they'll put a wallop on the brand when the circumstances are egregious enough.

This is coming crisply into focus in the wake of the Equifax breach. Yesterday the firm released its third quarter earnings results, along with estimates of primary breach costs like forensic investigation, remediation, and consumer credit reporting. The contrast between the two sets of numbers should act as an example to CEOs and board directors as to the true risk that big breaches can pose to income and business health. 

According to Equifax, breach costs are currently measuring up to approximately $87.5 million. More troubling, though, is the precipitous drop in revenue Equifax experienced in the wake of the breach.

In 2017 the credit reporting agency was flying high with huge quarterly increases in net income. First quarter saw a 25% quarter-to-quarter gain and a whopping 50% gain in revenue compared to first quarter of 2016. Second quarter saw an 8% quarterly gain and a 26% rise in net income compared to second quarter of 2016, up to $165.4 million.

Then the breach made the engines fall off - after the early September announcement, revenue plummeted to $96.3. That is an incredible 42% quarterly drop in net revenue, and a 27% drop compared to the same time period last year. And that's just net revenue: Share value has been similarly ravaged. Since the September 7th breach announcement, the firm has lost just over a quarter of its stock valuation.

The circumstances with Equifax are different compared to mega breaches of the past, where company stock valuations have bounced back fairly quickly. The TJXs and Targets of the world primarily deal in goods and services, but Equifax's core business is in information. Protecting it should be a core competency and customers and shareholders are ticked.

Nevertheless, this event may be still be a global bellwether that shows that consumers and shareholders have had it with all breached companies. Their antennae are up with regard to how companies deal with their private data, and they'll change their behavior if they have evidence that companies aren't doing what they need to protect that data.

Just this week a Gallup poll showed that two-thirds of consumers today worry about hackers stealing their financial information - nearly double the amount of those worried about having their car broken into, being burglarized, or being the victim of terrorism.

Meantime, other market data has bubbled up this year that translates that concern into real brand value impacts for companies that aren't doing their security due diligence. A study in September by YouGov BrandIndex tracked brand scoring of a number of major brands following a mega breach in recent years. Equifax saw the most precipitous drop in brand scoring, but other companies like Anthem Blue Cross, Home Depot, and Ebay all saw attrition to their scores in the wake of a breach.

Meanwhile, earlier this year Ponemon Institute concluded that in a study of 113 companies they suffered an average 5% drop in stock value following the disclosure of their breach. The firm showed that nearly a third of consumers report terminating relationships with breached companies in the wake of the incident.

It's a worry that CMOs and marketing directors at least recognize. Within this audience almost three-quarters say that the biggest cost of a security incident is loss of reputation and brand value. That's way more than the fewer than half of IT leaders who would agree with that sentiment.

"Consumers and shareholders are tangibly holding companies responsible for consumer personally identifiable information (PII), and for data leaks and breaches," says Lisa Baergen, marketing director for NuData Security, a Mastercard company. "Companies need to break past outdated notions. While internal departments debate responsibility, consumers and shareholders are holding the brand responsible – making it everyone’s problem. The tangible economic impacts of breaches will only grow."

 

 

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda here.

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
vasukivasudav
50%
50%
vasukivasudav,
User Rank: Apprentice
11/13/2017 | 6:45:45 AM
Good
Nice post thanks for sharing
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
9 Tips to Prepare for the Future of Cloud & Network Security
Kelly Sheridan, Staff Editor, Dark Reading,  9/28/2020
Attacker Dwell Time: Ransomware's Most Important Metric
Ricardo Villadiego, Founder and CEO of Lumu,  9/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20902
PUBLISHED: 2020-10-01
Upgrading Crowd via XML Data Transfer can reactivate a disabled user from OpenLDAP. The affected versions are from before version 3.4.6 and from 3.5.0 before 3.5.1.
CVE-2019-20903
PUBLISHED: 2020-10-01
The hyperlinks functionality in atlaskit/editor-core in before version 113.1.5 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in link targets.
CVE-2020-25288
PUBLISHED: 2020-09-30
An issue was discovered in MantisBT before 2.24.3. When editing an Issue in a Project where a Custom Field with a crafted Regular Expression property is used, improper escaping of the corresponding form input's pattern attribute allows HTML injection and, if CSP settings permit, execution of arbitra...
CVE-2020-25781
PUBLISHED: 2020-09-30
An issue was discovered in file_download.php in MantisBT before 2.24.3. Users without access to view private issue notes are able to download the (supposedly private) attachments linked to these notes by accessing the corresponding file download URL directly.
CVE-2020-25830
PUBLISHED: 2020-09-30
An issue was discovered in MantisBT before 2.24.3. Improper escaping of a custom field's name allows an attacker to inject HTML and, if CSP settings permit, achieve execution of arbitrary JavaScript when attempting to update said custom field via bug_actiongroup_page.php.