GDPR Compliance Requirements and Implications for US Companies

    Sep 12, 2018 7:35:31 AM by John Pocknell

    Written by John Pocknell and Colin Truran.

    As a DBA, I’m sure you are probably aware by now there’s been a lot of recent coverage around data breaches and access to personal data. You may also have heard about the new GDPR (General Data Protection Regulation (GDPR) legislation that went into effect on May 25th this year.

    The maximum penalty for non-compliance is 4% of annual revenue or €20 million, whichever is higher. Lower fines of up to 2% are possible for administrative breaches, such as not carrying out impact assessments or notifying the authorities or individuals in the event of a data breach. This puts data protection penalties into same category as anti-corruption or competition compliance.

    You might be asking yourself, so what do I need to know and how do ensure our business is protected?

    The first thing you need to consider is one aspect of GDPR called “Privacy by Design”. This requires a fresh look at how you should design your systems with data privacy as a priority. This starts with data discovery. How do I know what data in my databases is “Personally Identifiable Information” or PII.

    Our own (UK based) Principal Technology Strategist and GDPR expert, Colin Truran, sets out some of the background to GDPR and what it should mean to US companies.

    In future blogs, we’ll get into some of the detail of what this means for DBAs and what they should start doing now to ensure the protection of their company’s data.

    Over to you Colin….

    GDPR

    I thought I would dedicate this blog to one topic that keeps coming up: “As a US business or government organisation, does GDPR affect me?”  However, even if you are not based in the United States, I encourage you to continue reading, as the same challenges, restrictions, enforcements and opportunities still apply around the world.

    What people are really asking is whether the EU’s new teeth can be brought to bear outside of the EU, and in particular, what influence could it possibly have against an economical giant such as the US.  Why should organisations listen, take notice or even be slightly worried?  The answer for many small organisations that only trade within the US and have no interest in employing or dealing with any EU citizens data is going to be pretty simple.  However, unless you can be absolutely sure that you will not hold, receive or pass through data by any means regarding an EU citizen, no matter where they actually live, then you may need to be a little more attentive.

    So let’s try to answer the first question, can the European Union impose a fine or penalty on a US or otherwise external organisation?   The simple answer is yes, although the extent of the penalty and how it is enforced will be dependent on many factors, such as:

    • local due process
    • current unilateral trade agreements
    • whether you are exclusively based in the US or have an EU presence
    • or whether you have a presence in a country outside of the EU, but which has strong ties to the EU through trade agreements

    But yes, the simplest way for the EU to impose a fine or penalty on a non EU-based company is to use local data protection regulations. Increasingly, GDPR is being seen as the standard model for other countries, so you may find yourself subject to local rules based on GDPR compliance principals that impose even greater restrictions and penalties.  In other countries, the primary route for ensuring compliance and enforcement will come from the Data Protection Authority.  However, a DPA does not exist in the US. The closest equivalent that has jurisdiction over most commercial organisations is the Federal Trade Commission (FTC), as well as a state attorney’s office, which have similar authority over other areas.

    The real question is how far does the US Department of Commerce want to go to avoid trade embargos and impediments?  We have already seen that the US-EU Safe Harbour self-certification program “PrivacyTrust”, formally “eTrust”, fell short of required European Commission requirements and has been replaced by Privacy Shield.  In the meantime, this forced cloud providers to establish data centres and data policies that favour the EU territories.  There is also an underlying desire by governments to protect its citizens and organisations wanting to be taking a moral stand on how personal information is handled and used.  On many occasions, we have heard that the European Commissions’ data protection and data privacy policies are leading the way for the rest of the world.  We also need to note that many countries have stronger regulations within their own boarders that need to be adhered to.  So the practical upshot is that US companies will be under pressure to adhere to GDPR requirements if they wish to trade with or pass data through the EU, and this will be backed up by a desire to make sure any failures will be enforced by the US government in a desire to prove itself as a desirable platform for ecommerce.

    To summarise;

    • A large number, but not all US-based organisations, will have the requirement to demonstrate compliance with GDPR. This especially applies to those with a physical presence in any EU country or territory that trades within the EU, such as the UK after its exit, as these countries will be implementing GDPR as their own local laws. 
    • The US authorities and federal government will have a desire to ensure organisations adhere to these regulations in an effort to protect its own ability to trade. Infringements will be supported by the best appropriate method at the request of the European Commission.  
    • It won’t just be the EU that is trying to enforce such high standards in data protection, as many other countries around the world adopt the same or similar stringent policies in order to both remain an effective trading partner as well as its moral obligation to individuals’ rights.
    • Local laws will still be in effect in conjunction with GDPR and affect not just where the data resides, but come into play based on where it is used and transferred through.  Don’t forget that you will need to consider the local data regulations for every country that your data passes through.
    • Data protection is not just about fining organisations. There are a great number of criminal actions that will be taken against individuals responsible within a business.
    • A data processor is any organisation that takes part in the data lifecycle.  So even if you only store the data for a company or simply collect and instantly pass on to the owner, you are classified as a processor and therefore impact the assessed risk to that data. This means that your customers be it an individual or multiple organisations will be deciding to do business based on the level of risk you pose as a data processor. 

     It is important to remember that you will be competing both as a country and as a business against those that handle personal data to the high standards laid out by GDPR.   Companies that have a strong moral compass and verifiable good data practices will do well as we move into this new era of ethical e-commerce where individuals have the ability to choose to be adequately protected.

    For more information and resources on GDPR, please click this link.

    Tags: Administration GDPR

    John Pocknell

    Written by John Pocknell

    John Pocknell is a senior product marketing manager at Quest Software. Based at the European headquarters in the U.K., John is responsible for the go-to-market strategy for the Toad portfolio of products worldwide. He has been with Quest Software since 2000, working in the database design, development and deployment product areas. John has spent over 17 years (including 12 years in Product Management) successfully evangelising Toad to customers at various conferences and user groups around the world and he writes blogs and produced many videos on the Toad user community, Toad World as well as technical papers about Toad on the Quest Software website.

    John has worked in IT for more than 30 years, most of that time in Oracle application design and development. He is a qualified aeronautical engineer with more than 10 years of experience in provisioning IT consultancy services and implementing quality assurance systems to ISO 9001.