http://learninternetgovernance.blogspot.com/p/new-to-internet-governance.html
Showing posts with label GDPR. Show all posts
Showing posts with label GDPR. Show all posts

Saturday, March 3, 2018

General Data Protection Regulation (GDPR)

Learn Internet Governance

The General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679) is a regulation by which the European Parliament, the Council of the European Union and the European Commission intend to strengthen and unify data protection for all individuals within the European Union (EU).

The GDPR covers the companies that collect data on citizens in EU countries will need to comply with strict new rules around protecting customer data by May 25. GDPR is expected to set a new standard for consumer rights regarding their data, but companies will be challenged as they put systems and processes in place to comply.

Compliance will cause some concerns and new expectations of security teams. For example, the GDPR takes a wide view of what constitutes personal identification information. Companies will need the same level of protection for things like an individual’s IP address or cookie data as they do for name, address and Social Security number.

In short the GDPR is a regulation that requires businesses to protect the personal data and privacy of EU citizens for transactions that occur within EU member states. And non-compliance could cost companies dearly. Here’s what every company that does business in Europe needs to know about GDPR.

History
The European Parliament adopted the GDPR in April 2016, replacing an outdated data protection directive from 1995. It carries provisions that require businesses to protect the personal data and privacy of EU citizens for transactions that occur within EU member states. The GDPR also regulates the exportation of personal data outside the EU.

The provisions are consistent across all 28 EU member states, which means that companies have just one standard to meet within the EU. However, that standard is quite high and will require most companies to make a large investment to meet and to administer.

Privacy data Protected by  GDPR :

  • Basic identity information such as name, address and ID numbers
  • Web data such as location, IP address, cookie data and RFID tags
  • Health and genetic data
  • Biometric data
  • Racial or ethnic data
  • Political opinions
  • Sexual orientation

Inside GDPR 

Part I  Deals with the history and of data privacy law in the European Union.
Part II Highlights and discusses how the GDPR can lead to the adoption of data privacy practices in countries without comprehensive data privacy laws through the private sector.
Part III Focuses on challenges for developing economies to adopt a comprehensive regime like the GDPR, and proposes co-regulatory approach for data privacy.


GDPR Reach and Limitation :


GDPR must be comply by any company that stores or processes personal information about EU citizens within EU, even if they do not have a business presence within the EU. Specific criteria for companies required to comply are:
  • A presence in an EU country.
  • No presence in the EU, but it processes personal data of European residents.
  • More than 250 employees.
  • Fewer than 250 employees but its data-processing impacts the rights and freedoms of data subjects, is not occasional, or includes certain types of sensitive personal data. That effectively means almost all companies.

GDPR and  third-party contracts :

The GDPR places equal liability on data controllers (the organization that owns the data) and data processors (outside organizations that help manage that data). A third-party processor not in compliance means your organization is not in compliance. The new regulation also has strict rules for reporting breaches that everyone in the chain must be able to comply with. Organizations must also inform customers of their rights under GDPR.

What this means is that all existing contracts with processors (e.g., cloud providers, SaaS vendors, or payroll service providers) and customers need to spell out responsibilities. The revised contracts also need to define consistent processes for how data is managed and protected, and how breaches are reported.