The GDPR’s “Right to be Forgotten,” also known as “The Right to Erasure,” has been hyped a great deal over the last couple of years. In fact, the Right to Erasure requires that personal information (PI) be securely deleted when requested by the individual - within 45 days - if no legal reasons require it to be kept, i.e. litigation or regulatory compliance. But what about PI collected or purchased that make up the massive marketing contact lists used for marketing campaigns etc.?
As more companies move their data to the cloud, the question of data sovereignty is becoming a hotter topic. Data sovereignty is the requirement that digital data is subject to the laws of the country in which it is collected or processed. Many countries have requirements that data collected domestically must stay in that country. They argue that it’s in the Government’s interest to protect their citizen's personal information against any misuse.
Subscribe to the blog and get instant access to the crucial steps to ensure your cloud-based Office 365 migration goes smoothly.
A great deal has been written about the GDPR and CCPA privacy laws, both of which includes a “right to be forgotten.” The right to be forgotten is an idea that was put into practice in the European Union (EU) in May 2018 with the General Data Privacy Regulation (GDPR).
Over the years I’ve written a lot about the benefits of enterprise file consolidation, i.e., storing and managing unstructured data in a common repository. In fact, most companies still have data spread around the enterprise in distinct stand-alone data silos (usually unmanaged at the file level) including custodian computers, removable media, personal cloud accounts, file systems, email systems, and SharePoint servers (to name just a few). Companies run the risk of experiencing eDiscovery and regulatory issues, the inability to run effective data analytics processes, and lower employee productivity.
The Journaling function in “on premise” Microsoft Exchange email systems was originally developed back in the late 1990s for financial services organizations to meet SEC requirements. The main requirement consisted of capturing broker/dealer communications (emails) immediately, ensuring those emails could not have been altered or deleted before they were stored on immutable storage (WORM) per SEC 17 a-3 and a- 4 requirements. The SEC wanted to ensure that broker/dealer communications were available to review in an unaltered state if complaints were later filed against the financial services organization or individual broker/dealers. In fact, other companies adopted journaling for various reasons, mostly when under litigation hold to ensure target custodian email was captured and held thereby avoiding spoliation charges. However, the financial services industry was the only industry to really require it via government regulation.
So, you’ve decided to move your on premise email system to Office 365/Exchange Online for cost savings, higher security, and scalability. However, before you begin the migration, a question you should ask is; does my organization journal email for compliance, legal, or business requirements? If your company does, then read on.
Customers tell us that their on premise storage systems are overflowing, causing them to continuously purchase additional, expensive enterprise storage, more floor-space, and hire additional personnel. The solution is straightforward, the cloud. So, it’s not a surprise that companies are discovering the benefits of the Azure Cloud along with the Archive2Azure intelligent data management solution to store, archive, and manage all types of structured, semi-structured, and unstructured data. Unlike third-party proprietary clouds, Azure plus Archive2Azure creates an intelligent cloud platform to store, secure, and manage all your data at the lowest price possible. And because your data is stored in your organization’s Azure tenancy, there is never a need to worry about cloud vendor lock-in or data ransoming when you want to move your data out – it's your data, stored in its native format, in your Azure account.