"The missing link between Human Trust and Digital Trust Assurance"

 digital trustworthiness - is about notice semantics that people can trust to see who (if not oneself) is in control and accountable for personal information.

 Privacy Controller Receipt Credential (Control Provenance Credential) 

This credential is essential for generating digital notice and consent, it contains the legal entity name, which is bound as a credential by the accountable person as defined by their role in the organization.

The challenges:

1. The accountable person may or may not be an employee of the organization 
2. different jurisdictions name/define and reference this role differently 
3. some jurisdictions, like the UK have a data controller registry, where this binding is public and legally required
4. some jurisdictions, like the EU require an accountable data controller representative in the jurisdiction they are operating in, to address data privacy and security issues that may arise. 
5. 2 or more Controllers might be accountable for processing of personal data
6. The privacy law in some jurisdictions, can itself break privacy law in other jurisdictions by requiring the accountable person information to be published publicly, 
7. extend a privacy assurance profile by binding a VC for trust assurance

The proposed solution: 

Develop this controller credential specification with a set of rules for the use, maintenance, and lifecycle of a privacy controller credential. 

To illustrate: 

A record format to capture the bound controller information, which can be used to present a notice of control according to context, and a notice of who the accountable person is according to purpose of credential use.

The specification should provide: 

• a record format that MUST blind the identity of the accountable person,
• be usable as a linked data in a notice of control receipt, which provides only the controller information required for the purpose of credential use. 
• record, so as to provide a profile of the bound controller credentials in a manner that can show the controlling person before, during and after the use of a decentralized digital identifier.

Details for Risk and Liability Management 

• Provenance  of control starts with the person who is accountable and bound to a legal entity (who is liable). 

Overview  

Supporting Decentralized Data Controls with Identity Governance for Data subject’s (data) rights. This task force mission is to enhance identity to enhance identity and data governance interoperability  with standardized notice of Control and accountability for processing personal data (with the  ToiP layered governance model.)

...

This specification will provide a nested schema to record a privacy controller credential for transparency over the control of processing.  This privacy controller credential is intended to use a stack of standards and specifications to provide a standard set of identity control semantics, that can then be used in notice and notification by and notification by people to control personal data directly to provide Privacy assurance. 

...

The use of an international standards framework for providing standarized notice semantics is critical to harmonize or highlight different security, privacy and identity management governance requirements.   Standardized semantics, usable for any data governance is also  critical for human interoperability/usability across domains which is the key driver of this work and effort at ToiP .  

Like consent.  

interoperable Interoperable semantic standards and specification stack:

1. For privacy and security notifications of  decentralized identifiers, VC's and the ISO 27710 series,Security Techniques - Information Security Management Systems - in particular,
   1. ISO/ IEC 29100 Security Techniques - Privacy Framework  (for identifier governance) 
   2. ISO/IEC 29184 Online Privacy Notice & Consent
   3. ISO/IEC 27560 Consent Record Structure
   4. Kantara Advanced  Notice & Consent Receipt specifications for 
      1. Decentralized Proof of Notice for orgs 
      2. Decentralized Proof of Processing (aka consent) for people
2. W3C  Data Control Vocabulary ( maps  legal semantics to ontology) to harmonize decentralized legal semantics with machine readable semantics for linking identifiers and personal data. 
3.  OCA Specification for Operational Semantic Notice 
   1. conformity assessment vectors for OCA schema's 
      1. legal schema overlay from localized privacy law schema 
      2. legal schema conformity assessment to ISO baseline 
      3. legal schema overlay conformity assessment to a privacy law schema 
      4. conformity assessment report on legal adequacy for privacy rigxzhts and associated infrormation controls

 Privacy Controller Receipt Credential (Control Provenance Credential) 

This credential is essential for generating digital notice and consent, it contains the legal entity name, which is bound as a credential by the accountable person as defined by their role in the organization.

The challenges:

1. The accountable person may or may not be an employee of the organization 
2. different jurisdictions name/define and reference this role differently 
3. some jurisdictions, like the UK have a data controller registry, where this binding is public and legally required
4. some jurisdictions, like the EU require an accountable data controller representative in the jurisdiction they are operating in, to address data privacy and security issues that may arise. 
5. 2 or more Controllers might be accountable for processing of personal data
6. The privacy law in some jurisdictions, can itself break privacy law in other jurisdictions by requiring the accountable person information to be published publicly, 

The proposed solution: 

Develop this controller credential specification with a set of rules for the use, maintenance, and lifecycle of a privacy controller credential. 

To illustrate: 

A record format to capture the bound controller information, which can be used to present a notice of control according to context, and a notice of who the accountable person is according to purpose of credential use.

The specification should provide: 

• a record format that MUST blind the identity of the accountable person,
• be usable as a linked data in a notice of control receipt, which provides only the controller information required for the purpose of credential use. 
• record, so as to provide a profile of the bound controller credentials in a manner that can show the controlling person before, during and after the use of a decentralized digital identifier.

Details for Risk and Liability Management 

...

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

...