Enterprising Developments

The Cost of a Data Breach Versus the Cost of More Security

Joe McKendrick
Insurance Experts' Forum, July 2, 2013

The cost of a data breach keeps creeping upward. A new study from Ponemon Institute and Symantec calculates that the average cost is $136 per affected record — up from $130 in last year's survey. However, this is the international average — the cost is $188 within the United States.

The number of breached records per incident this year ranged from 2,300 records to more than 99,000 records, Ponemon states. This year, the average per incident settled somewhere around 23,647. Therefore, it can be surmised that the average cost of a security incident for a U.S. company was more than $4.4 million. Compare this with the cost of investing in security software and training.

Ponemon bases its estimates on a range of factors, including direct, indirect and opportunity costs stemming from activities required to detect a breach, activities necessary to report the breach of protected information to appropriate personnel within a specified time period, and activities that enable the company to notify data subjects with a letter, outbound telephone call, e-mail or general notice that personal information was lost or stolen.

The report also takes note that “lost business costs were stable (such costs include customer churn, customer acquisition activities, and brand reputation loss). In many organizations — especially in heavily regulated industries such as healthcare and financial services — lost business costs represented the largest financial consequence of a data breach.”

A total of 277 organizations were studied for the report.

The Ponemon-Symantec report makes the following recommendations for getting a better grip on potential security costs:

• Educate employees and train them on how to handle confidential information.

• Use data loss prevention technology to find sensitive data and protect it from leaving your organization.

• Deploy encryption and strong authentication solutions.

• Prepare an incident response plan including proper steps for customer notification.

Joe McKendrick is an author, consultant, blogger and frequent INN contributor specializing in information technology.

Readers are encouraged to respond to Joe using the “Add Your Comments” box below. He can also be reached at joe@mckendrickresearch.com.

This blog was exclusively written for Insurance Networking News. It may not be reposted or reused without permission from Insurance Networking News.

The opinions of bloggers on www.insurancenetworking.com do not necessarily reflect those of Insurance Networking News.

Comments (0)

Be the first to comment on this post using the section below.

Add Your Comments...

Already Registered?

If you have already registered to Insurance Networking News, please use the form below to login. When completed you will immeditely be directed to post a comment.

Forgot your password?

Not Registered?

You must be registered to post a comment. Click here to register.

Blog Archive

CIOs: “We Don't Have Enough People to Run Our Mainframes”

Insurers will be competing with other industries for both legacy and “new IT" talent.

4 Ways to Keep Insurance Data Quality Healthy

Continually building trust and credibility in the data is the key to a successful data warehouse.

Customer Experience Trend Watch

Three recent HR moves demonstrate that large life insurers recognize customer experience as a strategic differentiator.

Insurers Have a Lot of Data, But Too Many Silos

Insurers actually have more data analytics resources than other industries.

Are Data Centers Shrinking or Expanding?

Today's data centers are doing far more with much smaller footprints.

Too Much Manual Effort is a Show Stopper

Examining the administrative burden of doing business in the E&S market.

Advertisement

Advertisement