3.3.1: Implementation Considerations

Managing Technology Projects · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    3.3.1: Implementation Considerations

    Summary of the relevant GDPR requirements:

    • Consent (Article 6)
    • Data subject rights (GDPR Chapter 3, Articles 12-23)
    • Right to erasure/Right to be forgotten (Article 17)
    • Marketing opt-out (Article 21)
    • Data encryption (Article 32)
    • Pseudonymization (Article 25 and 32)
    • Handling data breach notifications. Prepare relevant processes. (Articles 33-34)
    • Hire DPO (Articles 37 and 38)
    • Certifications (Article 42)
    • Cross-border data transfers (Articles 44-49)

    Overarching Considerations

    Companies were aware of the regulation two years before it went into effect. Some worked to attain compliance by the date the GDPR went into effect, while others did not and have had issues. Achieving compliance requires investing resources to comply with the consent, data mapping, and cross-border data transfer requirements, among others.

    Organizations that want to attain GDPR compliance have a few options:

    • Change their existing business systems to handle the EU as a special case. The user's profile can be inspected to determine their address. The user's IP address can be used to ascertain location.
    • Change business systems to extend GDPR protections to all users globally.

    Taking stock

    Before launching into implementation, it would be wise to do a detailed assessment of the status quo, the current state of the organization's level of compliance with the GDPR articles. Organizations that had already implemented compliance with the predecessor Data Protection Directive (DPD) had a head start.

    This would involve assessing what user data is currently collected, what operations are performed on it, how and where is the data stored, and where is it transmitted. This assessment should include levels of pseudonymization and encryption. This assessment would include controllers and processors.

    An output of this assessment would be the identification existing gaps in GDPR compliance.

    Consent (Article 6)

    The data subject provides “informed consent” for each specific purpose that the data is going to be used for. The implementation cannot bundle multiple data processing types together when seeking consent. The data subject can revoke consent/permission any time.

    There is some good guidance provided by Recital 32.

    "Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject's agreement to the processing of personal data relating to him or her, such as by a written statement, including by electronic means, or an oral statement. This could include ticking a box when visiting an internet website, choosing technical settings for information society services or another statement or conduct which clearly indicates in this context the data subject's acceptance of the proposed processing of his or her personal data. Silence, pre-ticked boxes or inactivity should not therefore constitute consent. Consent should cover all processing activities carried out for the same purpose or purposes. When the processing has multiple purposes, consent should be given for all of them. If the data subject's consent is to be given following a request by electronic means, the request must be clear, concise and not unnecessarily disruptive to the use of the service for which it is provided."

    Note

    Note the specific reference to "pre-ticked boxes or inactivity."

    Note also that when the processing has multiple purposes, it is necessary to obtain consent of all of them (i.e., each of them).

    See also Marketing Opt-out (Article 21).

    Data Subject Rights (Articles 12-23)

    • Right to be informed about what is being collected, how is it used, how long is it retained.
    • Right to objection and “profiling”(e.g., for direct marketing): can request end to such use.
    • Right to request copy of data collected.
    • Right to have data erased.

    In all of these cases, a user interface needs to make this option available to interested data subjects and to obtain their input and take the actions required to fulfill the intent of the request. The user should be informed that the request has been accepted and to provide a timeframe within which the request likely will be completed and notify the user when the request has been completed.

    Right to erasure/Right to be forgotten (Article 17)

    This will require a user interface to make this option available to interested data subjects. Presumably the controller will gather this request from the data subject. The controller will also need to pass the request on to all relevant downstream processors.

    In addition to erasing all primary copies of the data of the data subject, all other copies of the data need to be erased.

    This raises an interesting question about how to handle data backups that include a broad range of data across multiple data subjects.

    Direct Marketing Opt-out (Article 21)

    GDPR Article 21 allows a data subject to object to using personal information for marketing, sales, or non-service related purposes (including “profiling”).

    Users “opting out” could impact a major source of advertising revenue for some companies. Companies that do most of their business on the internet can derive a significant amount of revenue from advertising. The ads might be targeted to certain users or user classes based on their data. If a company derives 95% of its revenues from direct marketing, asking a user if they want to opt out from having their data be used for direct marketing purposes to be in compliance with the GDPR would likely generate some interesting boardroom discussions.

    For example, in designing the user interface for this, one might consider the following possible wireframes to be presented to the user.

    Details in Accessibility Note.

    Figure \(\PageIndex{1}\): Wireframe for GDPR Starting Point. (Robert Slate, CIS 79 course materials)
    Accessibility Note

    Figure \(\PageIndex{1}\): Wireframe for GDPR Starting Point shows a mock-up creen stating "We will be asking you a series of short questions regarding your personal data used by our organization. We will save your responses in your profile so that you only need to answer each question once. You can update your profile preferences at any time." Next blue-colored arrow button.

    Details in Accessibility Note.

    Figure \(\PageIndex{2}\): Wireframe for GDPR Opt-Out. (Robert Slate, CIS 79 course materials)
    Accessibility Note

    Figure \(\PageIndex{2}\): Wireframe for GDPR Opt-Out shows a mock-up screen with text: "Please select whether you want to have your personal data used by our organization or by third party organizations for direct marketing purposes." With Opt-out and Opt-in options described in the text.

    Note that this screen specifically pre-selects the "Opt-out" option as the default option as required. The user would have to specifically select the "Opt-in" option to allow his or her data to be used for direct marketing purposes.

    Pseudonymisation/Pseudonymization

    • Article 25 requires that data protection mechanisms be designed into business systems.
    • With Pseudonymisation/Pseudonymization: data cannot be tied to a specific “data subject.” Note that data encryption can be employed as a data protection mechanism.

    Pseudonymization is a procedure by which the most identifying fields within a data record are replaced by one or more artificial identifiers, or pseudonyms. [Ref 1]

    Definition: Pseudonymisation/Pseudonymization

    ‘pseudonymisation’ means the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person.

    GDPR Article 4 (5)

    Example: John Smith maps to "Person 1", Sally Jones maps to "Person 2".

    Note

    However, 87% of the United States actually has a unique combination of birth date, gender, and zip code, so someone who has those 3 data items might be able to re-identify people. [Ref. 1]

    Full/complete anonymization could be employed as well.

    Default: highest privacy settings, data not publicly available.

    Relevant GDPR Recitals concerning Pseudonymisation/Pseudonymization

    GDPR Recitals 26, 28, and 29 provide additional context on Pseudonymisation/Pseudonymization.

    Recital 26

    The principles of data protection should apply to any information concerning an identified or identifiable natural person. Personal data which have undergone pseudonymisation, which could be attributed to a natural person by the use of additional information should be considered to be information on an identifiable natural person. To determine whether a natural person is identifiable, account should be taken of all the means reasonably likely to be used, such as singling out, either by the controller or by another person to identify the natural person directly or indirectly. To ascertain whether means are reasonably likely to be used to identify the natural person, account should be taken of all objective factors, such as the costs of and the amount of time required for identification, taking into consideration the available technology at the time of the processing and technological developments. The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable. This Regulation does not therefore concern the processing of such anonymous information, including for statistical or research purposes.

    Recital 28

    The application of pseudonymisation to personal data can reduce the risks to the data subjects concerned and help controllers and processors to meet their data-protection obligations. The explicit introduction of ‘pseudonymisation’ in this Regulation is not intended to preclude any other measures of data protection.

    Recital 29

    In order to create incentives to apply pseudonymisation when processing personal data, measures of pseudonymisation should, whilst allowing general analysis, be possible within the same controller when that controller has taken technical and organisational measures necessary to ensure, for the processing concerned, that this Regulation is implemented, and that additional information for attributing the personal data to a specific data subject is kept separately. The controller processing the personal data should indicate the authorised persons within the same controller.

    Hire DPO (Articles 37 and 38)

    The DPO can be either an internal employee or someone who works outside of the organization. Where the DPO reports into the organization is an important consideration in order to maintain the required independence and not have conflicts of interest. The hiring of the DPO may or may not be part of the compliance project as it could be handled as an executive staff action item.

    Certifications (Article 42)

    The company or organization can decide whether it wishes to pursue a formal certification per Article 42 to help mitigate risk and to inform its customers on its level of compliance. Remember, formal certification is voluntary, not mandatory.

    Implement new data protection and network protection procedures

    The data protection requirements have been previously discussed. Since data breaches need to be reported both to supervisory authorities as well as to affected data subjects, there likely would need to be an assessment of existing network security and closing identified gaps as required. It would be useful to document the relevant organizational processes and procedures.

    Handling data breach notifications (Articles 33-34)

    Implementing this item is more about preparing the relevant processes. Ideally the network and corporate data processing infrastructure should be proactively strengthened to minimize the potential for data breaches. However, in the event a data breach occurs occur, the processes need to be in place to allow for smooth execution to meet the GDPR requirements and notification timelines.

    This could be done in many ways. Conceptually, a list of tasks needs to be created along with a RACI matrix to show who is Responsible, Accountable, Consulted, and Informed.

    References

    1. Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation), 2016 O.J. (L 119) 1.
    2. Bowman, Gesher, Grant, and Slate, The Architecture of Privacy, 2015, page 166.

    3.3.1: Implementation Considerations is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.