Summary 

• The controller credential is an extension of the Kantara Initiative, ANCR Notice Record specification, and apart of the notice record and receipt information structure used in the 0PN- AuthC Protocol.
• to get acces to the current draft - please join a work group call and request it. 

"The missing link between Human Trust and Digital Trust" Implementing   (SSI)

Introduction

In privacy regulations globally transparency is a key requirement.   transparency is most often represented by the requirements for notice and specifying a legal justification and purpose for processing.

In this regard standards for the transparency and notice are required for transparency to scale. As a result there is a critical security issue in which people are not able to see who is in control of their personal data, what the legal justification and authority is used to processing personal - which makes it almost impossible to consent to transfer or exchange personal data across boarders.

This specification specifies the creation of a notice controller credential, which is used to generate micro-credential, signing a receipt to authorise  a specific purpose of use to implement international records of processing. 

Default - consent (representing shared understanding - as starting point)  - is provided in relationships record. 

• the default presented to the controller - using the controller credential 
• a notice request is the provided aka - a request to track - to  update the understanding 

Security , Transparency & Governance Gap

At this time people can't verify the services that  are processing their personal information, or control the source of information that is processed. 

There are 3 vectors of governance that this specification is designed to cater for which affect the privacy and security risks

Between, 

Transparency Governance Framework - For Transparency Trust 

3 Vectors of Governance 

1. Personal Data Control (Gov) - (lower risk) uses micro-credentials 
   1. the individual controls the source of data and verification 
   2. attribute by attribute control 
   3. Logging the access to the attribute for processing 
2. Co-Regulation : multi-party governed - 
   1. Data trusts, where the individual + regulator and service co-regulate
   2. Logging the access to the processing 
3. Data Protection : Self-Regulated -
   1. the service provider regulates the processing of personal data
   2. Signed, verified and open code, with shared logging

3 Tiers of  Controller Assurance

0 - Self Asserted Identifier 

1. Public verifiable 
2. Digitally verifiable & Legal (service delegation)
3. Operator Controller - Certified and legal 

Specification Overview 

This specification builds upon the Kantara ANCR Record specification (and Consent Reciept)(ref) to build a notice controller credential for recording the controller and contract information in a notice. 

The ANCR Record provides Consent Types to anchor the record trust record and an individual's understanding of the relationship.  Specifically, root of trust record for the individual, which the individual owns and controls In a personal data store and profile. 

Two types of Trust: OECD ref

type 1. 

The individual trusting the system 

type 2

the individual prooving who they are. digital (don't need to trust)  technology like zero knowledge, 

The Record and Receipt specification uses ISO/IEC 29100 Security and Privacy techniques ref (free ISO specification) terms and definitions to identify the legal stakeholders(ref) and their roles in the processing and control of personal information.    Using international standards for creation of  record and receipts publicly. 

ISO/IEC 29184 - Online Privacy Notice and Consent Controls  - 

The field data for the records and receipts are specified from numerous sources, in particular the W3C Data Privacy Vocabulary, for 

Fields Added to ANCR Record to Create Verifiable Credential

ANCR Record spec - is here (enter link)

This credential is for transparency and accountability for data (and identifier) governance,

The  eNotice (PII) Controller Cresdential, is used to generate eNotice record, for micro-credential PII Principal 

1. PII Controller Identifier [DiD] 
   1. Credential ID 
   1. Accountable Person 
   2. Accountable Person role
   1. Controller Notice Record Identifier 
   1. Controller Receipt Identifier 
   1. : DiD: Verified Credential  

1. Controller Type[Ctype]:  
2. Notice Controller,  
3. PII notice controller,  
4. PII controller,    
5. PII surveillance controller , (info not provided by PII Principle) 
6. [Ctype] controller operator, 
7. Accountable Person Type

Security

To address the security gap, the controller credential is presented in a privacy or security notice, prior to surveillance.

The individual can use this controller credential to provide consent for a specific purpose, as well as specifying the source of data, by providing a consent receipt, signed to be a micro-credential. 

There are a series of steps which need to take place to establish two types of trust 

Type 1: Transparency Trustframework - 

Human security, discovers or generates a controller credential to create human trust anchor record and credential (dial tone)independent of the Controller/Service provider. 

Type 2: Technical Trust 

This Controller Credential is 

Micro-Credential Use Cases

 Examples

1. Security, 
   1. evidence 
      1. fraud, traceabilty
      2. permission and access control transparency. 
   2. Security of Security 
      1. schema struture and use of object identifiers 
      2. NIST - Privacy and Security Control framework 
         1. NIST Language - 
2. Auditing a ToiP implementation

Glossary

Controller Credential 

Micro Credential

Privacy Stakeholders - ISO 29100

Annex: Privacy Stakeholder Mapping to Functional ToiP Roles

Continuing of the ANCR Record Assessment to identify the controller credential,

Map the ToiP functional role to the legal authority, justification and role of the stakeholder. 

Questions: 

Is the controller the holder, verifier, or issuer? 

Delegated Authority Examples :

References for Controller Credential, Infrastructure and Legal Framework

Reference: 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