This specification for a controller credential is required to operationalize the electronic notice and eConsent framework.   This specification distinguishes between what is referred to as consent by services online, with eConsent, which is a digital version of consent for use by digital identity systems to enable self-sovereign identity governance to scale from the physical world to the digital world. 

Today what is called consent online is a capture of a consent preference as permission with the use of a contract or licensee agreement (terms of use).  And is regulated with a privacy policy for this contract. 

In this electronic architecture data governance policy is implemented with privacy law and then made scalable with contracts and terms and conditions.  This is made possible by updating standardizing the required privacy controller information and its presentation, to include the accountable person and how the credential is linked, presented, recorded, shared, logged and stored.  

Mission: " a public utility register for human centric transparency, identifier control and trust" 

The controller credential is for implementing decentralized identity control transparency.  Public utility for  data governance used for automating personal data control transparency. 

Implementing true SSI with electronic notice and consent - using international governance frameworks for hyperlocal transparency and data control

Introduction

In privacy regulations transparency is a key requirement.   transparency is most often represented by the requirements for notice and specifying a legal justification and purpose for processing. These represent the analogue legal requirements. Modern privacy law has additional requirements in which transparency over rights and identity based controls should be proportionate to the technology and risk.   Current digital identity notice and consent mechanisms are governed by terms, conditions and contracts and are most often defined by system permissions rather than the purpose of use.  As a result analogue / human consent and control does not scale online to govern and control digital identifiers. 

This is a significant security challenge for decentralized identity as lack of transparency over who controls and benefits from the digital identifier is a) not standardized and b) not provided until after digital identifiers are created and used to permission access and controls to an eco-system. 

To scale transparency and data controls online, digital data controller information (and identitifiers) are required to automate rights based controls are to autonomously provide a  stateful privacy signal.  Required so that people can understand, access and effectively operationalize privacy for interoperability.   Without standardized digital transparency and privacy controls,  decentralized identifier control is not possible.   

This additional controller 'digital trust' information is used to generate an electronic two factor notice (2FN) for eConsent.  

Governance & Risk

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 

International standards are used to address limitation  to internet scale data governance in national standards frameworks. 

This controller credential utilizes a reference architecture that began with 1980 OECD Guidelines, and has been worked on for international /internet scalable data governance.  This work has driven regulatory reform and convergence internationally. GDPR refer framework for digital. 

This controller credential specification extends this international governance standard to the Trust over IP Governance Framework and is used to generate purpose specific micro-credentials for the governance of digital information with SSI's.   This enables the use of this reference architecture to scale analogue notice and consent to electronic eNotice and eConsent for digital exchanges and interoperability.  

• ISO/IEC 29100
  • ISO/IEC 29100:2011 provides a privacy framework which. specifies a common privacy terminology; defines the actors and their roles in processing personally identifiable information (PII); describes privacy safeguarding considerations; and. provides references to known privacy principles for information technology.
  • ISO/IEC 29184 Online Privacy Notice & Consent 
  • ISO/IEC 29184 WD 5 Consent record information structure 
• ISO 27002 Series : WG 5 SC27
  • ISO 27001 sets forth the compliance requirements needed to become certified. In contrast, ISO 27002 is a set of guidelines that are designed to help you introduce and implement ISMS best practices.
• CoE 108+
  • International GDPR - 
    • data governance framework which provides the international enforcement policy baseline suitable for internet scale data control, identity transparency governance and consent
• W3C Data Privacy Vocabulary 
  • V.5
• Kantara
  • ANCR WG: eNotice and eConsent identity governance information structure  
  • ANCR Notice Record

Addressing The Challenge: Security Risk, Vulnerability  and Governance  Transparency Gap for SSI, as decentralized identifiers need a framework for transparency and control that can demonstrate international legal adequacy.  

The controller credential can be generated by any stakeholder, and is use to generate eNotice and eConsent records and receipts, that are defined here as micro-credentials.

Terms & Definitions

The terms and definitions presented and defined here are in addition to the references, this cover the field names specified for the controller. 

• specific to this spec, (in the annex - mapping semantics between frameworks )
•   

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. 

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. As a DiD: Verified Credential  

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

Security Considerations

how to specify the 

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 

Mitigation Risk

Using standard framework for transparency of control with data control defaults 

Micro-Credential 

defined as a credential specified to a specific purpose. 

Use Case

Assessment of transparency and performance of a micro-credential to mitigate risks with SSI

 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