Showing posts with label Data Breach. Show all posts
Showing posts with label Data Breach. Show all posts

Thursday, May 22, 2014

Bad Customer Service vs. Data Breaches: Competing for "Best Way to Lose Customers" Award

So which is worse: bad customer service or a data breach? Well, when it comes to brand reputation and customer loss rate, they may be equivalent.

identity theft, ID protection, data breach, information securityCustomer service has always been a sticking point for brands. After all, a bad in-store or phone experience with a company can send customers heading for the door, never to be heard from again. Environmental disasters also still rank high on the list of reasons customers may consider discontinuing their loyalty to a brand or company (think Exxon Mobile or BP). Yet, according to a recent study by the Ponemon Institute, customers now rate data breaches right along with customer service and environmental disasters as a major reason to ditch a company and run into the loving arms of its competitors.

It was really bound to happen, if you think about it. With the increase of very highly publicized data breaches in recent years (think Target a few months ago and eBay getting headlines today), customers are beginning to sit up and take notice. After all, the threat of identity theft promises much worse consequences than a bad experience with a rude customer service rep, and it hits much closer to home than an oil spill hundreds of miles away.

The average American consumer understands the long-lasting and potentially devastating effects of a breach of their personal information. According to the study, “prior to having their personal information lost or stolen, 24 percent of respondents (customers) said they were extremely or very concerned about becoming a victim of identity theft. Following the data breach, this concern increased to 45 percent, Ponemon says. Almost half of respondents feel their identity is at risk for years or forever.”

Wednesday, May 7, 2014

Data Breach Costs Rise 9% in 2013


data breach, data security, corporate security
So just how much money did companies lose last year to data breaches? Which industries are most at risk? Let’s break down the facts for 2013:
  • Average cost of a data breach to US companies: $5.4 million
  • Average cost per lost record: $201
  • Industries with highest breach costs (in this order):
    • Healthcare
    • Transportation
    • Energy 
    • Financial services 
    • Communications 
    • Pharmaceuticals
    • Manufacturing

While 2013 did not reach 2011’s high ($214 per lost record), this information still represents a 9% rise in data breach costs from last year’s $188 loss per lost record—and they think this may be due to loss of customers. A 15% “churn rate” (or tendency for customers to abandon a company) based on a data breach represented a steep increase from prior years. Folks are getting wise to companies that don't make securing their sensitive information a priority.

Will this rising cost trend cause companies to sharpen their security behaviors and stay on top of the dangers? We hope so. After all, security is our business. 

Maybe your company in that high-rilibrary of security courses, security awareness campaigns, or even social engineering consulting and penetration testing. These first steps can go a long way towards ratcheting those costs down and keeping customers feeling safe and satisfied. 
sk list. Maybe you are a small company with limited resources that still feels the pressure of social engineering and identity theft. Or maybe you just need more ideas about how to secure your own company’s assets. Consider Sight Training’s

Thursday, March 20, 2014

Are Deceptive Pen Testing Methods Always the Wrong Way to Go?

phishing, pen testing, data securityIt’s been interesting to watch all the articles and stories fly about the Army phishing attack carried out by an internal commander, and which was finally shut down last week.

Words like “panic,” disaster,” and “terrible’ and “irresponsible” are being thrown around like confetti.

Do I agree with the commanding officer’s decision to take matters into his own hands? No. He was one man acting on his own intuition, rather than one part of a concerted effort with proper executive notification. In an organization as large as the US military, no test should be completed without a lot of feedback and forethought.

It was also unfair to include the Thrift Savings Plan in an attack they knew nothing about—and then leave them to clean up the messy backlash.

But let’s get to the brass tacks here: we can’t necessarily call the commander’s actions “irresponsible” just because some folks got panicked or felt like guinea pigs.

Thursday, December 19, 2013

Wasted Energy: How Info Purges and a Third-Party Test Could Have Helped the DOE

cost, cleanup, data breach, security breachThere’s been a lot of online chatter this week about last summer’s Department of Energy breach—and rightly so. 150,000 affected employees is nothing to sneeze at. The worst part? All the affected employees may not even know yet.

The Real Cost of Data Breach Cleanup

In our experience, there is not a deep enough respect in the market for how difficult and expensive the notification requirements for data breaches can be. Not only can this cause public embarrassment, but it can also put the organization at serious legal and financial risk. Many organizations are mostly worried mostly about the intrinsic dangers of losing the actual data but do not demonstrate fear or motivation to invest in preventing the process of notification and remediation.

Thursday, November 14, 2013

Oh, the Humanity! Train Employees to Say "No" to Social Engineers

Let’s set the scene for the third social engineering tale in our story series “Oh, the Humanity.” A Fortune 100 company asked us to test their defenses against pretext calling, email phishing, and physical security. The best part? They pretty much just gave us carte blanche and asked us to figure out how a social engineer would develop an attack.

After making a few phone calls and obtaining a few seemingly innocuous pieces of information (we call them “building blocks”), we decided to make an attempt to obtain VPN access to their network. Through their audit, we had already obtained the Cisco VPN client and had numerous usernames and passwords. All we needed was a host name.


Thursday, October 31, 2013

Frontline Employees: Stop Being Polite and Start Getting Suspicious

Back in the late 90’s, I began a career path in college administration. I started slow, worked my way around a few schools, and tried out lots of positions: lowly student intern, undergrad admissions officer, International student admissions coordinator, marketing and creative officer. At one school, I even took over admissions for a while.

And I loved it, most of the time. There is something exciting about growing a department from the inside; creating policies and procedures that improve life for everyone, helping young people realize their dreams. I worked at some outstanding institutions.

But every institution I attended, visited, or worked for struggled with a common issue: low-level security awareness among frontline employees.

Tuesday, October 15, 2013

Information Security in 2013: Are Passwords Really Dead?

email password, phishing, security awareness, information securityAccording to Heather Adkins, Google’s information security manager, “the game is over” if your company is still relying on passwords as a primary form of information security protection.

Adkins laid it all out when speaking at a recent tech panel. Apparently, Google’s done with passwords and we should be too. She went on to describe a new means of authentication that could require physical tokens embedded in clothing. And who’s behind this world changing, space-age technology? You guessed it—Google.

Wednesday, September 11, 2013

IRS Exposes Social Security Numbers

Well, this one’s a real comedy of errors. An audit on July 1 by independent transparency and public-domain group Public.Resource.org indicates that the IRS may have accidentally exposed some social security numbers.

Actually, it might have been as many as 2319 Social Security numbers...attached to highly sensitive non-profit political groups…which sat exposed on the Internet for 24 hours.

Here’s just one more example of how easy it is to let really sensitive information slip through the cracks. The IRS are professionals at keeping people’s most private financial information under wraps, and breaches even happen to them.


California Releases First Data Breach Report

The State of California just released its first data-breach report for 2012 last week. Some of the report’s key findings include:
  • Reports of 131 data breaches affecting more than 500 Californians.
  • The breaches exposed 2.5 million Californians’ personal data.
  • More than half of the breaches (56 percent) involved Social Security numbers.
  • The use of encryption could have protected 1.4 million Californians’ data.
Yet, one of the most striking quotes was that “more than half of the breaches (55 percent) were the result of intentional intrusions by outsiders or by unauthorized insiders. The other 45 percent were largely the result of failures to adopt or carry out appropriate security measures.”

That says to me that breaches are all about people—whether they are social engineers or hackers intent on fraud, or regular hard-working employees who aren’t adequately protecting the information they access.

In either case, it’s obvious that California can’t really blame the computers. These breaches are a people problem, and can also be solved with people—people who are adequately trained to ward off hackers and social engineers and take steps to safeguard data or devices that contain sensitive information.

California Attorney General Kamala D. Harris opened the report by reminding readers of California’s strong consumer privacy laws and required data breach notification. If our “strongest” state still has data leaks to plug, then I wonder how the other 49 are faring.

http://oag.ca.gov/sites/all/files/agweb/pdfs/privacy/2012data_breach_rpt.pdf