Ovierview  

Data Governance: Data subject’s (data) rights

1. A key challenge is found in the lack of semantic harmonization for personal data control  which provides security for the portability of private information is required as a precondition to data control and portability. 
   1. to address this issue a unified notice control language which can be used to address harmonisation of  the notice to indicate which Data Subjects rights apply to which context, and which  data controls are authorized to be  used by the Data Subject. 
   2. whats involved
      1. use/finish the latest Operational Notice & Consent Receipt Specification -Kantara V1.2  that combines the ISO 29100 & 29184 and 27560 -standards comprised of the International privacy security framework (for Soverign data transfer) 
      2. start a generic - unified data control notice schema - mapped to the ISO 29100 framework - 
      3. map/generate a single international baseline overlay - ANCR WG-  ISO 27560 - Notice & Consent Receipt - Record Structure.
         

2. Key Points to consider:

   1.  sovereign identity, a data processing activity is based on a data subject’s explicit  or otherwise (human) consent (not internet service /cookie consent),

   2. an individual’s privacy rights need to be extended to proportional digital privacy rights, so an overlay extends the analogue privacy law with a standard digital control semantics with a unified notice control as the language for people to see, understand and control personal data

   3. Digital Rights usage Challenge

      1. different legal justifications have different rights associated with them.  This makes it very difficult for people and orgs to know what rights apply in any given data control context  - a problem that the can be solved with the use of these standards - 

      2.  e.g. a notice for explicit consent - or legitimate interest?  when does a Data subjects have the right to data portability (Article 20) when is processing is based on consent. When not used on consent- people have  the right to object (Article 21)

      3. the right to withdraw consent may provide a different outcomes - - 

      4. Articles 16 to 20 of the GDPR indicate that (when data processing is based on consent), data subjects have the right to erasure when consent has been withdrawn and the rights to restriction, rectification and access.

3. Gaps to cover 
   1. core schema base
   2. what missing in this base? 
      1. Verified Privacy Controller Credential 
4. Use Cases 
   1. Digital Immunisation Passport
      1. Holder, Verifier & Issuer

Unified Notice Control Language for Semantic Harmonization 

For UNCL - the  aim is to start a specification with the key roles specified for data control, transparency and accountability as the starting point.  And to start with the Privacy Controller, the key authorizing stakeholder for data processing, and to represent this in the.  standards and references for legal governance, and to currate a list of proposed (new terms/elements to explore) 

Requirements Privacy Controller Credential Specification

Providence  chain starts with the person who is accountable bound to a legal entity. 

Legal Entity Accountability Levels according to Tiers of Privacy Risk

Tier 0 - is self asserted controller (not a verified privacy controller) even in the ICO Controller Registry 

Tier 1 -  Privacy Controller - with low risk services - (employee privacy ) 

Tier 2 - High Risk Privacy - identity management, any specifically category of data - 

Tier 3 - Very High Risk - Beneficial owners - 

Objective - is to have a single identifier for a Privacy Controller, which includes all LEI's for beneficial ownership. 

• Privacy - Transparency over legal entities, accountable people and beneficial - 
• Legal Entity Identifier 
  • to identify the legal entity of the privacy controller 
  • beneficial owner of the legal entity 

• Accuntable Person
  • to identify the accountable person / role that is bound to the legal entity identifier (aka) organization. 
    • could be an employee
    • owner / director / officer 
    • data proaction officer 
    • 3rd. Party Company Representative 
      • accountable role - (for another 3rd Party) acting representative 
• Privacy Controller 
  • under what authority 
  • under what legal justification 

ISO 29100 Actors

(Note: In progress - consulting with Steven on auto filling) 

• looking to make a process for what Legal Privacy Stakeholder has the Credential Role
  • Steps to assign Stakeholder Roles
    • Test for checking if its a processors or a 3rd party? 

Delegated Role :

References for use for creating a Unified (generic) Data Control Vocabulary for OCA

Topic List

References

Reference Implementations

OPN: Open Notice  (+ Consent) Receipt Schema: Starters Guide to Unified Data Control Schema

Lizar, M. & Pandit, H.J., OPN: Open Notice Receipt Schema, 14th International Conference on Semantic Systems (SEMANTiCS 2019), Karlsruhe, Germany, 2019 [Published http://www.tara.tcd.ie/handle/2262/91576 [accessed July 1, 2020]

OCA schema specification: https://docs.google.com/spreadsheets/d/1KOdq8Yy3OXmuELyh7tpHMlhyMZPSZ3Ib/edit#gid=68769926