{"id":13389,"date":"2019-11-27T15:16:14","date_gmt":"2019-11-27T14:16:14","guid":{"rendered":"https:\/\/www.rosello-mallol.com\/incidencies-de-seguretat-que-fer\/"},"modified":"2023-03-30T09:49:01","modified_gmt":"2023-03-30T08:49:01","slug":"security-incidents-what-to-do","status":"publish","type":"post","link":"https:\/\/www.rosello-mallol.com\/en\/security-incidents-what-to-do\/","title":{"rendered":"Security incidents: what to do?"},"content":{"rendered":"\n

Any business that, to a greater or lesser extent, has started or has thought about starting its digitisation process may become a victim of a cyber-attack.<\/strong> What to do in case of security incidents?<\/p>\n\n\n\n

Websites, apps, or e-commerce managed by businesses are almost always on third-party servers and, therefore, however small your business, if the target of the attack are the servers of major companies hosting the contents of their clients, then nobody is free from being a victim of an attack. <\/p>\n\n\n\n

These major companies often have measures to minimise the risks, but they are never 100% safeguarded. What happens, however, if the personal data of your clients, employees or the recipients of your newsletter is put at risk during the attack?<\/p>\n\n\n\n

What does the data protection regulation have to say about security incidents? <\/strong><\/h2>\n\n\n\n

Until the GDPR came into force (May 2018), there was an obligation for the internal control and registering of any incident that might affect the security of personal data. The incident had to be identified, and steps taken to minimise or eliminate it before it could be formally closed. Since 2018, this formal obligation has included another two steps:<\/p>\n\n\n\n