Share on LinkedInShare on LinkedIn

ARTICLE · 05 MAY 2016

Deeper Dive: Regulatory Investigations Following A Reported Breach

BakerHostetler
BakerHostetler
Contributor
BakerHostetler

BakerHostetler

Recognized as an innovator and one of the top firms for client service, BakerHostetler helps...

View firm profile
Explore more from BakerHostetler

We recently released our 2016 Data Security Incident Response Report, which provides lessons learned and metrics related to over 300 data security incidents handled by our team.

United StatesPrivacy

We recently released our 2016 Data Security Incident Response Report ("Report"), which provides lessons learned and metrics related to over 300 data security incidents handled by our team. As noted in the report, once an incident is made public the potential ramifications include a wide-ranging investigation by a regulatory agency, such as state attorneys general. However, we found that regulatory investigations were slightly lower for incidents we managed in 2015 – 24% – down from 31% the year before.

While these statistics show that an investigation is not necessarily inevitable following every reported data incident, the frequency is such that the response to any data incident should be handled with an eye towards a potential investigation by a government agency. This means thinking long-term, instead of just getting through the immediate incident response.

We operate a free-to-view policy, asking only that you register in order to read all of our content. Please login or register to view the rest of this article.

See more popular content from