Skip to main content

Understanding General Data Protection Regulation (GDPR) and the business impact

Do you know how your personal data is used and exchanged within Facebook or Google? How do you feel if you see your personal information is exposed to a digital marketer and he keeps bombarding you with promotional offers which you are not interested in? Whether you like it or not, this is how it works today. Your personal information is there to be used by anyone who can pay a small amount of money or capable of doing some kind of hacking. Do you ever think about why someone wants your full detail when registering into some kind of service?

Within first 6 months of 2017, there has been more than 6 Billion personal records were exposed through data breaches. They cost millions of dollars to the organizations today and in the future. Trust and confidence are the most important factors in today's business. 70% of customers reports that they would be less inclined to work with a business that suffered a public disclosure of a data breach.

From the above facts, it is self evident that data protection is not only important to the customers but also to the businesses. Even though business leaders understands the value of the data, that understanding has not translated into careful data stewardship. But with the impact they have seen with these data breaches on other businesses, everyone is now keen on having a better protection to their data.

Source: https://marketoonist.com/2017/10/gdpr.html

General Data Protection Regulation or GDPR provides the much needed kick in the ass to many businesses that have become complacent about the data security. All the businesses dealing with data about EU citizens (in and out of EU) needs to comply with this regulation by 2018 May. It is the successor to the previous regulation data protection directive which was introduced in 1995.

Even though this is a regulation, it has many useful things which any business can use for their benefit.

Forcing awareness about entire data web

  • Business leaders are forced to understand their data landscape no matter if your company is a small company or a large multi national company with subsidiaries and 100s of partners. All the incoming and outgoing data must be well understood. 
  • If the business has subsidiaries and partners, the entire data web needs to be well understood. 

Demanding knowledge of data sources and origin countries

  • Every data source (Partners, Customers, Subsidiaries) feeding data into the organization must be vetted and documented.
  • GDPR is the first global data protection law
  • Applies to any business which process data about EU citizens

Advising data minimization

  • Companies must state a planned use for all the personal data they obtain. Recommend to use data which is absolutely necessary. No additional data to be used for future.
  • Not holding data for any longer than absolutely necessary
  • Not changing the original purpose of the data capture
  • Deleting any data at the request of the data subject (customer)

Spotlighting data sharing

  • Data in transit needs to be properly secured.
  • Businesses must be able to document appropriate security measures for every step in data's life cycle

Acquiring consent

  • Requires clear, affirmative consent of use for personal information of EU citizens. 
  • Lack of response is not considered automatic consent

Breach monitoring and response

  • Breach notifications needs to sent within 72 hours of breach detection
  • Breach policies needs to be carefully setup with partners and well documented
Even though this looks like something annoying for a business, it really has some good things which can be gained for every company. This regulation provides the careful design of your business data and avoid keeping unnecessary data within your organization and hence reducing the operational expenditure.

In addition to the above mentioned points, following link provides a list of major changes which are coming with the GDPR.

https://www.eugdpr.org/key-changes.html


Comments

  1. nice post you have shared thanks for sharing. Here i have found a origination where you can consults about GDPR and Web Services and they will clear you all dout about GDPR.

    ReplyDelete
  2. Thanks for sharing this information with us we are GDPR Consultant in India where we are single focused towards our clients and there business strategic objectives and we can provide regular and independent audit services regarding GDPR compliance.For more details call us:- +91 9968416366

    ReplyDelete

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...

WSO2 ESB usage of get-property function

What are Properties? WSO2 has a huge set of mediators but property mediator is mostly used mediator for writing any proxy service or API. Property mediator is used to store any value or xml fragment temporarily during life cycle of a thread for any service or API. We can compare “Property” mediator with “Variable” in any other traditional programming languages (Like: C, C++, Java, .Net etc). There are few properties those are used/maintained by ESB itself and on the other hand few properties can be defined by users (programmers). In other words, we can say that properties can be define in below 2 categories: ESB Defined Properties User Defined Properties. These properties can be stored/defined in different scopes, like: Transport Synapse or Default Axis2 Registry System Operation Generally, these properties are read by get-properties() function. This function can be invoked with below 2 variations. get-property(String propertyName) get-property(String scop...