State of (in)security - Week 43
Take action: Track Repeat Incidents to establish trends of wrong behavior. One-off incidents can occur to anyone, but multiple similar incidents indicate deeper systemic issues. Monitoring the frequency and nature of incidents is crucial - especially for third-party providers. Don't be afraid to change a provider if they are not behaving properly. It costs much less than being impacted by their incidents.
There were a total of 2,920,344 impacted individuals across 10 incidents, with the largest breach being the Redcliffe Labs apparently impacted by data leak, exposing 12 million records incident exposing 2,500,000 individuals. Since not all incidents report a number of impacted individuals, the real number is definitely higher than that.
|Cause||Number of incidents|
|third party breach||4|
|database configuration error, exposed w/o password online||2|
|protocol design issue||1|
|DB config error, exposed w/o password||1|
|email account breach||1|
|Industry||Number of incidents|