Experian Data Breach Resolution releases its Annual 2015-2016 Data Breach Response Guide
A Ponemon Institute study sponsored by Experian Data Breach Resolution found that a majority of businesses surveyed had a data breach response plan in place, but many were not confident in their response and did not practice their plan through discussions or drills. To help companies take their preparedness to the next level, Experian Data Breach Resolution enhanced its Annual 2015–2016 Data Breach Response Guide with new content that focuses on the gaps organizations still face with their incident response.
Companies today realize the need for a data breach response plan, but taking the next steps to respond successfully to a data breach seems to be the Achilles' heel in preparedness. Forty-one percent of Ponemon Institute survey respondents do not have a set time for reviewing or updating their plan, and 37 percent have not reviewed or updated their plan since it was put in place.
"A response plan in a binder does not really prepare a company for handling a breach," said Michael Bruemmer, vice president at Experian Data Breach Resolution. "Organizations need to develop what if' scenarios that require a plan 'B' and 'C'. This is important because a breach may be intended to damage a company's reputation, for extortion purposes or to compromise customers' reputations. How should unique circumstances be managed? It should all be part of the plan."
The complimentary Guide can be downloaded at https://bit.ly/1QUx19X.
Some of the Guide's new content includes more step-by-step instructions, checklists and a preparedness quiz. Organizations that have not developed a plan yet will find the guide also offers content addressing the notification process, how to select external vendors and the public relations component of a breach response.
For additional data breach resources, including Webinars, white papers and videos, visit https://www.experian.com/databreach. Read the Experian Data Breach Resolution blog athttps://www.experian.com/dbblog.