The Basic Information Safety Regulation (GDPR) is a regulation in European regulation on knowledge safety and privateness within the European Union and the European Financial Space. It additionally addresses the switch of private knowledge exterior of those areas.
To fulfill Basic Information Safety Regulation (GDPR) necessities, Microsoft has applied technical (tooling) and organizational measures (processes) to make sure that knowledge processing is in accordance with GDPR privateness rules. The precise path will likely be completely different for each group, however basic assets can be found in a Service Belief Portal that Microsoft has created for patrons to get began.
1. Privacy principles
A compliant GDPR solution needs to address all privacy principles, which in turn will affect all business processes and workflows, IT systems, as well as all applications used and implemented by the organization. Addressing the security principle explained in section 4 of this document is particularly important and necessary, but not sufficient in terms of a GDPR-compliant solution. The key changes required to address GDPR are:
2. Security principle
The security principle relates to the collection of personal data: personal data must be processed in a manner that ensures appropriate security, including protection against unauthorized or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organizational measures to ensure integrity and confidentiality” of personal data.
3. GDPR Impact on SQL features
SQL-based applications must be reviewed and analyzed for their GDPR compliance. Here we will discuss the following features:
4. GDPR Data subject requests
Microsoft’s GDPR capabilities will enable enterprise customers to fulfill the GDPR requirement to give data subjects access to the data collected about them upon request. These requests are referred to as Data Subject Rights requests (DSRs). In the context of Azure, we distinguish between two categories of data:
