"The missing link between Human Trust and Digital Trust Assurance"
Digital trustworthiness - is the missing link for people. To achieve human trust, the control of privacy needs to be human/individual centric, not business, legal and technical centric. It is for this reason that the global point of interoperability for privacy and human data control is on the requirement for a privacy, surveillance, safety, and security notice.
In all of the jurisdictions, in all the laws, providing a notice to people is required, as this is how people gain contextual knowledge and can participate in consensus. Every privacy law requires that the identity of the privacy controller and the contact point for rights administration be provided.
A privacy controller credential is
- the combination of the legal entity +
- the accountable / contact person into a verifiable credential
- so that it can be used to provide privacy assurances (access to privacy rights information and to be heard)
Legally, this information is required to be as open as possible and is codified in law in many different ways. Standardizing the credential using ISO 29100( open and free ) so that privacy controller credential can be used by people internationally to assert privacy controls and negotiate individual digital rights with service providers and communities.
This specification focuses on a best practice schema for identifying the privacy controller.
What is this
Decentralized Governance and Data Control - through the use of the credential, which can be asserted.
Process in progress:
Notice & Consent for people relies on clear communication.
Decentralized identity relies on contextual legal semantics and notices in order to be compliant with sovereign data rights or operational in context.
Specification proposal: to extend Decentralized Semantic Governance for a dynamic data control ( DDC) architecture for transparency and controls that are human centric.
Privacy Controller Credential For Decentralized Data Governance with Notice and Consent
This specifies the controller record used to verify, validate and notarize rights claims for online environments/services by individual to increase human awareness, control, and trust. Utilizing semantically standardized notice records and consent receipts, (also known as a Consent Notice Receipt)(ref ISO 29184), in addition to, Data Privacy Vocabulary specified for generating notice and notifications that are both human and machine readable.
This credential is comprised of the legal entity name and the accountable person as defined by their role in the data organization and documented in the ISO/IEC 29100 standard. This record is further specified and extended in this specification for 3 levels of transparency assurance and controls when processing personal data in a digital service supply chain,
Challenges focused on with this specification:
- The accountable person may or may not be an employee of the organization.
- Different jurisdictions name/define and reference this role differently
- Some jurisdictions, like the UK have a data controller registry (DCR), where this binding is public and legally required (benefit in this case, challenge where absent)and the name of the accountable person is publicly available in ICO DCR. (using blinding identity taxonomy)
- Some jurisdictions, like the EU require an accountable data controller representative in the jurisdiction where a service is operating, in order to address legal data privacy and security issues that may arise.
- 2 or more Controllers might be accountable for processing of personal data.
- Identify in context of service for any user the controller and accountable person.
- The privacy law in some jurisdictions, can itself break privacy law in other jurisdictions by requiring the accountable person information to be published publicly,
- Specifies how to by a VC (in this case the Privacy Controller Credential) for trust assurance for privacy assurance
- International Notice & Control protocol for Unified Data Control & Portable semantics for governance interoperability between domain and jurisdictions.
- Develop an extensible controller credential format
- specifying 3 nested layers of controller identifier claims, to correspond with tiers of Privacy Risk Assurance.
- A set of rules for the use: verification, validation and notarization of the controller credential.
The specification shall provid:
- 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.
- control providence begins with the person making the assertion to the accountable role using laws and standards to bind privacy rights request to a legal entity
Why Privacy Controller and why ToiP?
Supporting Decentralized Data Controls with Identity Governance for Data subject’s (data) rights. This task force mission is to enhance identity and data governance interoperability with standardized notice of Control and accountability for processing personal data (with the ToiP layered governance model.)
The key challenge this initial specification is aimed to address is systemic (and broadcasted) transparency over the controller of personal information, so that data controls can be used automatically to enable dynamic data control.
Unlike in physical world, the processors of your personal data are invisible. This is why the identity of the data controller is required in all legal privacy frameworks and is the most common and similar legal component for processing personal data. This makes the notice of control an ideal focus for ToiP governance interoperability.
Online, there can be many processors, personal identifiers can be shared and aggregated without any transparency, personal data may continuously be processed and people are completely unaware and at risk of this surveillance. This is why the promise of SSI is so attractive and why profiling and aggregation using identifiers is specifically called out in privacy legislation as high risk to privacy in which processing is required to be more (proportionally transparent). What's more, even the Controller, might contain multiple legal entities. This challenges identity management technologies for privacy compliance and human trust.
To address a key part of this challenge a specification for listing the Identity Control Provenance, focusing on the legal entities and accountable people in control of processing personal data as the first spec to providing the needed transparency (or Notice) for the control of processing, required for trustworthy processing.
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 people to control personal data directly to provide Privacy assurance.
Background of this Semantic Standards Stack
- A key challenge to interoperability is addressed with the International ISO/IEC standards framework 29100 and 29184. This provides a semantic control framework to address the lack of semantic harmonization for personal data control which provides security for the portability and control of private information and is a required for people to be able to independently consent and control personal information. This challenge first presented the W3C DoNotTrack Conference in Berkeley California. 'Opening Up the Online Infrastructure' .
- This turned into a Kantara Specification effort in 2014 and now, last year, ISO voted to fast track this to a standard 27560, to be used with ISO 29184 to address what was know by the phrased of the Biggest Lie on the Internet, was a focus of a movie Terms and Condition's May Apply. With an international governance rule set, people can use independently of Terms and Conditions.
- Now this work is being updated to the ANCR WG Notice Records for Receipts version,.
Decentralized Data Governance
The Identity and Data Governance semantic based line is the international ISO/IEC 29100 security and privacy techniques framework, this is mapped to Legal jurisdiction notice schema and the differnces and risks (in terms of rights and the performance of data controls) is provided as a component of the notice of control.
The risks are used to provided a progressive framework for people to self-mitigate the risks and themselves drive the development of dynamic digital identity governance interoperability. Translating a local governance schema to the internationalized schema base for governance controls and privacy rights comparison. Then, to overlay the next schema for localized identity and data governance controls, which utilized the same surveillance and privacy semantic governance framework in order to indicate the level of data governance interoperability.
In this process the OCA utilizes this stack of standards and specifications to syncratically harmonize data portability and control with purpose driven interoperability for data and identity governance.
This is accomplished with the standard for specifying a purpose for notice and consent.
The Trustworthy Transparency Specification Stack
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 .
Data Governance Interoperability: semantic standards stack:
- For privacy and security notifications of decentralized identifiers, VC's and the ISO 27710 series,Security Techniques - Information Security Management Systems - in particular,
- ISO/ IEC 29100 Security Techniques - Privacy Framework (for identifier governance)
- ISO/IEC 29184 Online Privacy Notice & Consent
- ISO/IEC 27560 Consent Record Structure
- Kantara Advanced Notice & Consent Receipt specifications for
- Decentralized Proof of Notice for orgs
- Decentralized Proof of Processing (aka consent) for people
- W3C Data Control Vocabulary ( maps legal semantics to ontology) to harmonize decentralized legal semantics with machine readable semantics for linking identifiers and personal data.
- OCA Specification for Operational Semantic Notice
- conformity assessment vectors for OCA schema's
- legal schema overlay from localized privacy law schema
- legal schema conformity assessment to ISO baseline
- legal schema overlay conformity assessment to a privacy law schema
- conformity assessment report o n legal adequacy for privacy rights and associated information controls
- conformity assessment vectors for OCA schema's
- Friction Reduction - simplifying compliance for digital ecosystems
- simple services that are purpose driven will have a better user experience
References for use for creating a Unified (generic) Data Control Vocabulary for OCA
Information technology — Security techniques — Privacy framework
ISO/IEC 29100:2011 provides a privacy framework which
|Status - Is publicly available - https://www.freestandardsdownload.com/iso-iec-29100-2011.html|
|ISO/IEC 29184:2020||Online privacy notice and consent||(just published - not available to public - we are working on publishing a report/appendix for use with this group )|
|W3C DPV 0.01||Data Privacy Vocabulary|
Reference: OPN-Notice Schema
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]
OPN Privacy Profile URI
Link to the controller's profile in the OPN registry.
Type of Notice Receipt
Label Notice Receipt
A unique number for each Notice Receipt. SHOULD use UUID-4 [RFC 4122].
Date and time of when the notice was generated and provided. The JSON value MUST be expressed as the number of seconds since 1970-01-01 00:00:00 GMT (Unix epoch).
The Controller’s profile public key. Used to sign notice icons, receipts and policies for higher assurance.
Language in which the consent was obtained. MUST use ISO 639-1:2002 [ISO 639] if this field is used. Default is 'EN'.
The identity (legal name) of the controller.
The jurisdiction(s) applicable to this notice
Contact name of the Controller. Contact could be a telephone number or an email address or a twitter handle.
Link to Notice
Link to the notice the receipt is for
Link to Policy
Method of notice presentation, sign, website pop-up etc
|Receipt Type||The human understandable label for a record or receipt for data processing. This is used to extend the schema with profile for the type of legal processing - and is Used to identify data privacy rights and controls|
OCA schema specification: https://docs.google.com/spreadsheets/d/1KOdq8Yy3OXmuELyh7tpHMlhyMZPSZ3Ib/edit#gid=68769926