Home   › What should you do if you discover a personal data breach?

What should you do if you discover a personal data breach?

May 27, 2019

Sharing is caring!

In case you discover a personal data breach, it is very important to conduct an investigation for identifying the nature, origin, or extent of the attack, inquire about the type of private data which was involved and what all individuals were affected in the breach. There is a possibility that, the organization itself is very likely to be involved in this breach in order to submit the personal data of users, to any third party. What better example than Facebook!

Always remember to document each and every action that is to be undertaken. This is necessary under the regulations of GDPR that will help in demonstrating the suitable measures taken accordingly for mitigating all the risks.

A more notable provision of the updated GDPR is the Article 33 or to say, the mandatory 72-hour data breach reporting requirement. The Article 33 orders in case of any personal data breach, the data controllers need to notify the apt supervisory authority, without any undue delay and, wherever, feasible, and it should not be later than 72 hours after becoming aware about  it.

With summarizing the different requirements or response mechanisms regarding the rule, you can be easily aware of the to-do steps, in case you witness a personal data breach.

Under the GDPR requirements, any organization have only 72 hours to collect all the breach related information while reporting the data breaches to the respective law regulator. This significant undertaking for an organization involves development and provision of a wide-ranging containment plan.

Well, the steps are pretty simple: Carry out the investigation, after which inform the regulators and the respective individuals of the data breach. Just be specific in respect to the data that is being impacted and how this issue can be addressed to move forward… keep in mind all this to be done within 72 hours. It is worth noting that if — for any reason — the notification is not made within 72-hour, the GDPR demands the controller to provide a justifiable reasonable for this delay; along with potentially adding some disruption of the regular business operations to exasperate the administrative hassle.
The GDPR Article 33 specifies the type of information every notification need to include.

Obviously, the information expectations are quite high, as the timeline is short- and thereby pose a significant challenge to the organization as it scrambles to meet the requirements while trying to simultaneous address that the issue is associated with the data breach, maintaining an ongoing operation.

for Further security teams, to be particular, this challenge of data breach identification tends to become even more demanding, given the data breaches doesn’t get discovered for weeks, months or even years.

But if the data breach gets discovered, with understanding its impact, report it in accordance with the Article 33 parameters.

Take an immediate action in order to mitigate the data breach (or rather switch to a platform, much more secure and encrypted, like Signal. This is help you to restore the access authorization in case of any security failure, while safeguarding your private communications.

Set up your Signal account to enjoy, hassle-free, secure communications. This includes end-to-end encryption and the company not storing any user’s data on its servers.

Signal-private messenger holds responsible for a complete security of its users from different breaches.

After identifying the root cause and extent of the data breach, it is crucially important to get a proper solution of the problem, by switching to a much more secure and private platform like Signal.


Leave a Reply

Your email address will not be published. Required fields are marked *