Skip to main content
Category

Blog

Identiverse 2022: The Time for Decentralized Identity is NOW

By Blog

Two weeks ago was the first full-scale Identiverse since the pandemic began, and host Ping Identity pulled out all the stops. It started off with a wonderful video splash with spotlighted drummers banging away, setting the stage for three days of wonderful entertainment, great keynotes, engaging sessions, and nonstop networking.  

Ping CEO Andre Durand ‘s opening keynote set the tone by putting decentralized identity front and center. Stating that our current systems do not scale, Andre took us on a journey through the history of Identity solutions from passwords, to single sign-on, to OAuth, to centralized and federated identity. 

Projected slide showing a progression from centralized identity to decentralized identity

He then ended with what we all know at the Trust Over IP Foundation: that the future is decentralized identity. 

A projected slide, with the presenter shown to the right

It was not just a wonderful start to the conference, but a great summary of exactly why ToIP was founded: we are collaborating to develop the recommendations, standards, guides, and templates needed to connect the gap shown on Andre’s slide above.

If there was a real surprise at this year’s Identiverse, it was the evidence presented throughout the conference that decentralized identity isn’t just the future, it is the NOW. For example, only an hour after Andre’s keynote, Kristina Yasuda, Senior Identity Standards Architecture at Microsoft, gave an entire talk extolling the virtues of verifiable credentials (VCs) without even mentioning Microsoft’s own VC products. (She also didn’t mention that she is the new co-chair of the new W3C Verifiable Credentials 2.0 Working Group along with Brent Zundel of Avast).

Shortly after Kristina’s session, Brent and Drummond Reed gave a presentation on how the SSI model of digital wallets and VCs can and should be integrated with existing identity and access management (IAM) systems. Their goal was to dispel any notion that “rip and replace” was necessary to start using VCs and the ToIP stack.

But the most resounding endorsement of VCs came when Alex Simons, Microsoft’s Corporate Vice President of Identity and Network Access gave the opening keynote on the second day. He not only spent the entire first half of his talk explaining why VCs were the headline new feature of the Microsoft Entra product suite, but then invited Kristina to give a live demo of VC interop between Microsoft, Ping, Workday, IBM, and MATTR. For more on the specific interop profile they were using, see this blog post from Microsoft decentralized identity product manager Ankur Patel.

On Thursday, ToIP Steering Committee member Mike Vesey, CEO of IdRamp presented several use cases in his session “Establishing Trust with Decentralized Identity Networks, Verifiable Credentials, and Zero Trust”. Mike shared several decentralized identity solutions operating in production today, including:

  • “Zoom Bouncer”, a new meeting security application now available in the Zoom public app store that allow meeting hosts to use verifiable credentials and biometrics to protect virtual meetings from zoom bombing. 
  • The North Dakota Department of Education decentralized identity initiative shows how verifiable credentials are being used for decentralized verification of student learner records for graduating students. 

Mike also gave a demo of the IdRamp zero code orchestration platform that allows issuance of verifiable credentials from any traditional IAM system and verification with any traditional relying party service—an entire journey that can be implemented in just a few minutes without any code. “IdRamp has been providing decentralization for a few years now.” states Mike Vesey, “The IdRamp platform provides a seamless bridge from centralized identity systems into decentralized credential based authentication and access control. It was inspiring to hear that same vision being shared by the largest IAM organizations in the world. The future of identity is decentralized and ToIP is playing a major role in guiding organizations on their journey into decentralized zero trust protection.”

Judith Fleenor, Director of Strategic Engagement at the Trust Over IP Foundation, agrees: “It’s exciting to see live use cases of verifiable credentials across various sectors of government and industry. It is equally exciting to see organizations such as our Steering Committee members IdRamp and Monokee making integration with traditional IAM a breeze through their innovative system integration platforms and consulting services.”

Another key theme throughout the conference was FIDO2 passkeys. At least a half-dozen sessions were focused on this topic—not surprising given the announcements from Apple, Google, Mozilla, and the FIDO Alliance earlier this spring—and that Identiverse focuses on an enterprise IAM-centric audience where solutions to multi-factor and passwordless authentication have been sought after for two decades.

Overall, the attendees from ToIP agreed that this Identiverse took a strong step in the direction of ToIP—and it made it even more important that we push forward with our work of completing the full definition of the ToIP stack.

If you’d like to participate in ToIP’s efforts to further define a complete governance and technical architecture for interoperable digital trust, join us by becoming a member.

Monokee Joins ToIP as a Steering Member

By Blog
Monokee

We are pleased to announce that Monokee s.r.l., a scaleup from north Italy, has joined the ToIP Foundation as a Steering Member. A company rising from the centralized and federated IAM world to embrace the SSI paradigm, Monokee intends to be an active contributor to the community’s efforts in defining the interoperability standards that will lead to Web 3.0.

Launched in 2018, Monokee leverages the 20 years of experience of its two founders in IAM/IGA consulting. The company’s flagship product is an easy-to-integrate, point-and-click visual identity orchestration tool used by security architects from SMEs to larger enterprises.

Representing Monokee on the Steering Committee will be Ing. Roberto Griggio, Monokee’s CEO. Roberto graduated in Computer Science from the University of Venice, Italy and sports more than 20 years in identity and access management and related fields. On the technical working groups and task forces, Monokee will be represented by Dr. Mattia Zago, Monokee’s SSI Solutions Architect. Mattia holds a Ph.D. from the University of Murcia, Spain, specifically dedicated to cybersecurity and artificial intelligence subjects. 

“Joining the ToIP Steering Committee represents a significant milestone for me as a researcher and us as an identity company,” said Dr. Zago. “Seeing that the community is aligned with our view of a hybrid integration between federated enterprises’ services and decentralized identities further increases our motivation to pursue it. Indeed, we will keep pushing forward our identity orchestrator to provide seamless (and codeless) integration experiences for security engineers.” 

Monokee believes a formal definition for the authentication and authorization processes is critical for integrating IAM/IGA solutions. Despite the importance of this aspect, most contemporary solutions require a non-negligible amount of engineering effort to connect identities, attributes, applications, flows, protocols, and many other elements.

Monokee simplifies this process with its Visual Identity Orchestrator (VIO), a drag-and-drop interface to build your authentication processes from scratch, starting from predefined blocks and connecting them in a flow-chart fashion as illustrated below.

Screenshot of Monokee's Visual Identity Orchestrator (VIO)

Each block and connector in the resulting map represent parts of the process in a virtually codeless environment: Monokee’s visual builder turns that map into computer-generated code, with no room for human errors. The VIO is also a major improvement for process management. For example, adding an authentication factor in an existing process is just a matter of dragging a new block into the chart and inserting it into the flow.

The abstraction provided by Monokee’s VIO aligns perfectly with the vision of the ToIP foundation of an interoperable web of trust. Specifically, Monokee aims to bridge the gap that exists at layers 3 and 4 of the ToIP stack between classic centralized and federated ecosystems and new decentralized services and resources. While this obviously involves technical challenges, the real interoperability questions reside in the governance framework that coordinates the topmost ecosystem layer: how to embrace the new trust paradigm without tossing away the achievements of the last decade?

Monokee envisions a hybrid world capable of taking advantage of the structured, well-tested, and effective IAM solutions while incorporating decentralized and distributed elements to improve end-user privacy and usability. Monokee plans to provide resources and workforce to help ToIP working groups achieve their 2022 objectives, starting with the ToIP Technology Architecture Specification, anticipated for release in September 2022.

Key ToIP Takeaways from the European Identity Conference

By Blog
EIC logo and dates

EIC 2022, held May 10-13 at the the Berlin Conference Center, had a strong ToIP presence, including Director of Strategic Engagements Judith Fleenor and Steering Committee members André Kudra (esatus), Bryn Robinson-Morgan (Mastercard), Christine Leong (Accenture), Drummond Reed (Avast), Mike Vesey (IDRamp), and Scott Perry (Schellman). Other ToIP members in attendance included Trinsic, IDunion, and Sezoo.

Our first collective takeaway was that identity conferences are back! This was the first full-scale EIC since 2019, and although still in hybrid form, in-person attendance was very strong. Vendor booths and conference sessions were quite busy, and there were four full tracks on content from midday Tuesday through Friday. “EIC was a wonderful opportunity to connect with colleagues old and new, with a shared mission to advance digital trust.” remarked Bryn “I was impressed by the interest in the ToIP stack and the recognition that to achieve interoperability on a global scale we must address both technology and governance issues.”

Our second major takeaway was that decentralized identity is a very hot topic. One of the four conference session tracks was devoted entirely to this new branch of the industry, and references to SSI and verifiable credentials were sprinkled throughout the keynotes. André noted: “Federated identity solutions are broadly used globally today and it’s great that there’s now such huge interest to infuse SSI to it. To ultimately arrive at a truly decentralized online identity world, embracing what’s already out there is inevitable.”

On that note, Judith spotted numerous examples of SSI terminology being “co-opted” to describe products and services that did not in fact follow SSI and ToIP design principles. This is both a good thing (because the speakers wanted to be associated with SSI) and a bad thing (because they are mis-using the terms).

A third major takeaway was that the world of federation wants to join the world of decentralization. One of the major announcements from the conference was the OpenID Foundation white paper entitled OpenID for Verifiable Credentials. To quote from the OpenID website:

The goal of this whitepaper is to inform and educate the readers about the work on the OpenID for Verifiable Credentials (OpenID4VC) specifications family. It addresses use-cases referred to as Self-Sovereign Identity, Decentralized Identity, or User-Centric Identity.

This theme was further reinforced by a series of sessions on GAIN, the Global Assured Identity Network, whose original white paper described it as an OpenID “federation of federations” that aims to bring “roaming” to existing bank ID networks around the world. At EIC, GAIN was working hard to “broaden the tent”, inviting Judith to join their final panel with 11 different speakers talking about the GAIN vision of a globally interoperable network for high-value digital identity credentials. 

Judith did a wonderful job speaking to how that vision aligns with ToIP’s mission while advocating that, while federation technologies like OpenID are fine for enterprise usage, true global interoperability can best be achieved with a network of networks based on the ToIP protocol stack. She summarized the benefits of using standardized protocols rather than technical API specifications as: “OIDC for the enterprise, ToIP for the Internet”.From a ToIP perspective, the highlight was our 40-minute panel called “The Stack, the Stack, the Stack: How ToIP is Enabling Internet-Scale Digital Trust”. Judith moderated the panel consisting of André, Bryn, Christine, and Drummond sitting in front of a full-screen image of the ToIP stack.

People watching a presentation that has the ToIP stack as the current slide

The session drew a packed audience, and this panel format proved to be a very effective way to share the ToIP vision. At the close of the panel, we were swamped with many more questions than we had time for. We spent the next 45 minutes outside the room talking with attendees about the ToIP stack, the ToIP Foundation, and how our solution to interoperability can be applied to the European Digital Identity Wallets initiative.

This strong interest in ToIP reflects our final major takeaway from the conference: the European Digital Identity Wallets initiative is generating intense interest in interoperability. Many EIC sessions touched on different facets of the interoperability questions facing the “toolbox teams” from each of the 27 EU member states working to develop their own digital wallets. Furthermore, these questions are not limited to technical interoperability—governance is also a major concern.

“The privacy-preserving and citizen-empowering advantages of decentralized identity and verifiable credentials are clearly what is driving the EU initiative,” said Governance Stack Working Group co-chair Scott Perry. “However much of their thinking on governance is still rooted in federation technologies, so this is an area where ToIP’s work on governance frameworks can really help.”

As a final highlight, Italian digital identity company Monokee, whose Solutions Architect Dr. Mattia Zago presented on “Hybrid Central/Decentralized Identity: Deployment strategies for SSI”, was impressed enough by the ToIP presence at EIC that by the end of the conference Monokee had joined as our newest Steering Committee member. 

“Joining the ToIP SC represents a significant milestone for me as a researcher and us as an identity company,” said Dr. Zago. “Seeing that the community is aligned with our view of a hybrid integration between federated enterprises’ services and decentralized identities further increases our motivation to pursue it. Indeed, we will keep pushing forward our identity orchestrator to provide seamless (and codeless) integration experiences for security engineers.” 

Welcome Monokee!

Decentralized Identity: Keys to mainstream adoption

By Blog

by Mike Vesey, CEO, IdRamp, and Karl Kneis, COO, IdRamp

idRamp logo

A cityscape at night, with a globe above it of interconnected lines

Understanding the decentralized identity (DCI) market can be challenging. Inspiring C-level decision makers and IT executives to adopt decentralized identity technology is even more difficult. Current research publications provide limited insight with inconsistent ideas and terminology. Anyone interested in DCI adoption can quickly get lost in an ocean of information that raises more questions than answers. What is the solution? Decentralized ID, Self-sovereign ID, Blockchain ID, Web 3.0 ID, Personal ID, Verifiable Credentials, DID or are they all the same thing? Is the technology production-ready or a next-generation innovation to be considered in the future? 

After spending a great deal of time working with enterprise C-level teams on complex digital identity problems, one thing seems clear. When it comes to decentralized identity solutions, many business sponsors do not yet understand how DCI can provide practical answers to immediate frontline business problems. This climate creates the impression that decentralized identity is interesting but not ready for prime time adoption.

Business leaders want to know

Business leaders want to know: 

  • How can I use decentralization to make identity management easy to deploy and operate? 
  • Is it possible to add new features and business requirements without investing in long, expensive projects? 
  • How do I adapt this new technology without re-platforming every few years? 
  • Is it possible to enable decentralized identity with the systems I have to grow it at a speed and cost I can afford?

Prominent decentralized identity initiatives are often presented as pilots or innovation projects. Popular decentralized identity community discussions prioritize solving large social problems over business solutions that drive mass adoption. Understandable for a new bleeding edge technology, but the good news is DCI technology is ready for mainstream adoption now. With careful listening, collaboration and education, we can dispel misunderstanding and help business sponsors understand that decentralized identity is the best possible solution for problems they have today. 

Most C-level executives do not understand the complexities of SAML or OIDC, but they do understand that solutions using these protocols help solve their business problems. We need decentralized identity to reach that same level of understanding in terms of reliability, comfort, and adoption. 

Decentralized Identity needs to become ID

Shifting the conversation to the perspective of people who actually buy technology is an effective way to speed up adoption. Business leaders need proof of value, battle testing, and technical maturity. Decentralization will prevail based on measurable business results. DCI is not in battle with centralized systems; it is simply a better business solution for modern problems.

Focusing on familiar business performance indicators goes a long way in moving DCI out of the innovation lab and into mainstream adoption. Does decentralized identity help me save or make money? Is it more expensive than what I have today? When a business spends millions per year on centralized SSO and learns how decentralized identity based authentication can solve the same problem with stronger protection at less cost. That business will find value and interest in DCI adoption.

Ultimately, decentralized identity needs to become digital ID in the minds of business leaders. Trust architecture needs to be easy to understand and use. Businesses do not have time to navigate the ideology and technical complexities. They need education that speaks directly to their business problems today. Trust Over IP (TOIP) models, guides,and specifications are powerful business tools to help drive learning, transformation and adoption. You can use the growing list of free information published on the TOIP Deliverables page to help educate and transform your organization through DCI.

Perception is reality

A few common misunderstandings that come up in our business adoption conversations include:

  • Decentralized identity is not just a solution for social issues, it is pain relief for front line business problems. Decentralized identity will provide superior results if you need Zero Trust, Password elimination or fraud prevention.
  • Decentralized identity does not equal loss of control. It is a more effective way to manage and protect digital business.
  • Decentralized identity adoption does not require re-platforming and heavy investment in line with past ID platforms. We can quickly deploy it with incremental adoption and easily combine it with all other ID services.
  • Decentralized identity governance complements existing IT operation models and standards. It does not require a total change to current procedures.
  • Decentralized identity service management does not require significant HR changes, custom development skills, or advanced technology resources. Existing IT teams can easily deploy and operate DCI systems with the people they have today.

That all sounds simple enough to explain, but how do you make it happen? Business sponsors need evidence to justify the investment. They need to see it in action. Our next post will focus on how we help overcome decentralized identity adoption through decentralized orchestration. This simple but powerful strategy provides an easy path for adoption and innovation.

Stay tuned.

The Trust Over IP Foundation Publishes New Introduction and Design Principles

By Blog

When it was launched in May 2020, the ToIP Foundation summarized its mission in a single 20-page white paper called “Introduction to Trust Over IP”. This paper was based on an article called The Trust Over IP Stack published in the December 2019 special issue of IEEE Communications Standards Magazine called The Dawn of the Internet Identity Layer and the Role of Decentralized Identity.

Two years later, with ten times more members and double the original number of working groups, the Foundation is a much more mature organization. Despite this growth, we are very pleased that the original vision of the ToIP stack has stood the test of time.

In summer of 2021, we put out a call to all ToIP members to participate in a series of “community writing workshops” to collaboratively produce two new Foundation-wide deliverables:

  1. Introduction to ToIP V2.0 (PDF)
    This is the second-generation version of our original introductory white paper that would go more deeply into the origin and purpose of the ToIP stack and how it addresses the key challenges of decentralized digital trust infrastructure.
  2. Design Principles for the ToIP Stack V1.0 (PDF)
    This is an articulation of the key design principles we must follow in the design and development of all aspects of the ToIP stack.

We were thrilled that over two dozen members took us up on this challenge to participate over four months to produce these two documents, both of which have just been approved by the ToIP Steering Committee.

Introduction to ToIP V2.0

Our primary goal with this second-generation white paper was to make the vision and mission of ToIP accessible to a general audience—literally anyone who cares about the future of the Internet and how we can deal with the myriad security, privacy, data protection, and data sovereignty issues that have emerged as “the world’s greatest information utility” passes its first half-century of growth.

Our second goal was a “plain English” explanation of the overall structure of the four-layer, two-half sided ToIP stack using new graphics based on the wonderful interactive version developed by Peter Stoyko of Elanica. Here is the new static version of the diagram:

Diagram of the four-layer Trust Over IP Stack.

Our third goal was to provide a more complete introduction to the ToIP Foundation as a collaborative organization devoted to the design, development, adoption, and promotion of the ToIP stack—a guide to helping prospective members understand how and why to engage.

The resulting document is divided into the following sections:

  • ToIP in a Nutshell
  • Why Has Digital Trust Become Such a Major Problem?
  • The ToIP Model for Digital Trust
  • Applying This Model to the Digital World
  • The ToIP Stack
  • The ToIP Foundation
  • How to Engage with the ToIP Foundation
  • The Road Ahead

It is available as a PDF document here and on the homepage of the ToIP Foundation website

Design Principles for the ToIP Stack V1.0

To establish a truly interoperable decentralized digital trust layer for the Internet as a whole, meticulous attention must be paid to the design of the ToIP stack. Given the tremendous growth of the ToIP Foundation—from 27 original founding member organizations to over ten times as many today—it was critical to form a strong consensus among the new members about the principles governing this design.

Another key reason to establish design principles for the development of a system is summarized in this quote from the start of the document:

The goal of any design principle is to provide guidance to the designers of a product, service, or system so they can take advantage of lessons learned from the success or failure of previous designs. Design principles represent accumulated wisdom that falls in between the generality of scientific laws and the specialization of best practices.

When it comes to a layered architecture for both technology and governance of decentralized digital trust infrastructure, the “lessons learned from the success or failure of previous designs” is prodigious. Thus the writing workshops for this document continued for four months in order to bring all the relevant design principles together.

To organize the final set of 17 principles into a logical progression, we followed a rubric suggested by co-editor Victor Syntez based on a 2006 blog post by cryptography pioneer Nick Szabo. Szabo distinguished between two types of “code”:

  1. Code written in a computer language expected to be executed by a machine (“dry code”), and
  2. Code written in a human language, i.e., laws, regulations, rules, policies and other forms of governance expected to be followed by humans (“wet code”).

Accordingly, we divided the principles into three categories:

  1. Principles of computer network architecture—these “dry code” principles represent fundamental lessons learned about the design of large-scale computer networked systems, especially the Internet:

#1: The End-to-End Principle

#2: Connectivity Is Its Own Reward

#3: The Hourglass Model

#4: Decentralization by Design and Default

#5: Cryptographic Verifiability

#6: Confidentiality by Design and Default

#7: Keys at the Edge

  1. Principles of human network architecture—these “wet code” principles represent fundamental truths about how trust relationships operate between humans—either individually or in groups:

#8: Trust is Human

#9: Trust is Relational

#10: Trust is Directional

#11: Trust is Contextual

#12: Trust has Limits

#13: Trust can be Transitive

#14: Trust and Technology have a Reciprocal Relationship

  1. Overall design principles—these three remaining principles apply to the overall design of the ToIP stack, “wet or dry”:

#15: Design for Ethical Values

#16: Design for Simplicity

#17: Design for Constant Change

Care was taken to not only explain each principle in plain English, but to analyze how it applies to the design of the ToIP stack at each layer. We summarized those recommendations using this table format:

LayerRelevanceExplanation
Layer 4 The ecosystem symbol represents the purpose of Layer 4 to support the applications needed to develop and sustain entire digital trust ecosystems.
Layer 3 The triangle symbol represents the Layer 3 verifiable credential “trust triangle” of issuer, holder, and verifier that enables parties using the ToIP stack to establish transitive trust.
Layer 2 The symbol of two connected mobile phones represents the purpose of Layer 2 as a universal peer-to-peer secure privacy-routing DID-to-DID communications protocol.
Layer 1 The anchor symbol represents the purpose of Layer 1 public key utilities to provide strong anchors for Decentralized Identifiers (DIDs) and their associated public keys.

For each principle, in the “Relevance” column we assigned star ratings for each layer as follows:

★★★★★Highly relevant to the design of this layer
★★★★Very relevant to the design of this layer
★★★Moderately relevant to the design of this layer
★★Somewhat relevant to the design of this layer
Only slightly relevant to the design of this layer

Once all 17 principles had been compiled into a document with this format, the contributors felt that we had identified the “center of gravity” of the design of the ToIP stack that could now guide our work in completing it.

We strongly recommend this document for anyone who wants to deeply understand the rationale for our work at the ToIP Foundation. It is available as a PDF document here and on the homepage of the ToIP Foundation website

Acknowledgments

Our thanks to Victor Syntez and Drummond Reed for serving as co-editors for these two documents and to the following ToIP members who contributed their time and expertise:

Introduction to ToIP V2.0Design Principles for the ToIP Stack 1.0
Carly Huitema
Daniel Bachenheimer — Accenture
Darrell O’Donnell — Continuum Loop
Jacques Bikoundou
Judith Fleenor — Trust Over IP Foundation
Kaliya Young — COVID-19 Credential Initiative
Karen Hand — Precision Strategic Solutions
Karl Kneis — IdRamp
John Jordan — Province of British Columbia
Lynn Bendixsen — Indicio
P. A. Subrahmanyam — CyberKnowledge
Sankarshan Mukhopadhyay — Dhiway Networks
Scott Perry — Scott S. Perry CPA, PLLC
Vikas Malhotra — WOPLLI Technologies
Wenjing Chu — Futurewei
Antti Kettunen
Daniel Bachenheimer — Accenture
Daniel Hardman — SICPA
Darrell O’Donnell — Continuum Loop
Jacques Bikoundou
Jo Spencer — 460degrees
John Jordan — Province of British Columbia
Jonathan Rayback — Evernym
Judith Fleenor — Trust Over IP Foundation
Lynn Bendixsen — Indicio
Mary Lacity — University of Arkansas
Michel PlanteNeil Thomson — QueryVision
P. A. Subrahmanyam — CyberKnowledge
Rieks Joosten — TNO
Sankarshan Mukhopadhyay — Dhiway Networks
Scott Perry — Scott S. Perry CPA, PLLC
Steven McCown — Anonyome Labs
Thomas Cox
Vikas Malhotra — WOPLLI Technologies
Vinod Panicker — Wipro Ltd
Wenjing Chu — Futurewei

Data Governance Act meets ToIP framework

By Blog

by Jan Lindquist, Neil Thomson, Burak Serdar, Paul Knowles, Christoph Fabianek, Phil Wolff

Introduction

Europe’s Data Governance Act (DGA) reached a milestone. The European Parliament announced it “…reached a provisional agreement on a new law to promote the availability of data and build a trustworthy environment to facilitate its use for research and the creation of innovative new services and products.”

What does the Data Governance Act mean to the ToIP framework and the SSI community?

Background

The DGA defines an “intermediary” that facilitates processing and sharing of data for individuals and organizations to “…increase trust in data intermediation services and foster data altruism across the EU”. In the MyData framework for user-controlled data sharing, intermediaries are called MyData Operators and there is a certification program in place. (See references at the end of this blog post.)

The DGA intermediary has a trusting relationship with the individual. There cannot be any conflict of interest in sharing the data from the individual. In the eyes of the Act, the sharing of the data shall foster “data altruism” across the EU.

To achieve this goal, DGA provisions a certification program and rules for some public-sector data.

SSI Data Sharing Models

The Data Governance Act introduces new roles into data sharing and will set up the necessary governance for a more transparent and accountable data economy. Two main actors are introduced called Data Sharing Service or Intermediaries [refer to chapter III, Requirements Applicable to Data Sharing Service in Data Governance Act] and Data Altruistic Organizations [refer to chapter IV, Data Altruistic in same reference].

Neither of these actors shall have a financial incentive that conflicts with representing a Data Subject when personal data is made available to Third-parties or Data Using Service. The following diagram has three SSI data sharing models.

A business or organization collects personal data and shares it with a third-party often in proprietary and closed interfaces. A non-proprietary health care data exchange interface is FHIR from HL7 which created an open interoperable standard.

A cooperative or intermediary represents the individual when sharing personal data. The sharing shall be standardized and interoperable between different suppliers.

A non-profit organization, acting altruistically, facilitates sharing of data that are in the public institution’s domain. The public institutions may, for example, be health care systems.

Data Governance Act Architecture Overview
Figure 1: Data Governance Act Architecture Overview

Some similarities can be drawn with the Verifiable Credential model where the Data Subject is a Holder, an organization is the Issuer and a third-party is a Verifier.

The DGA adds intermediaries to the ToIP framework

The key difference is addition of the Intermediary. The Intermediary represents an agent for the Holder (Data Subject) which has direct control of processing of personal data through a policy engine. Figure 1 shows the ToIP framework with the actors introduced in the Data Governance Act.

ToIP control and data planes overview
Figure 2: ToIP control and data planes overview

Two layers or paths when performing data exchange are described in the diagram.

  • A data path (yellow arrows) composed of Verified Credentials (VCs) and interfaces to a data repository.
  • A control path (green arrows) that sets the conditions for personal data usage, given through a data subject consenting to collecting, processing or sharing of personal data.

Each actor in the diagram has three different role types: a data role, a Distributed Ledger Technology (DLT) role, and a privacy role.

  • The data role represents Data Subject who the collected data relates to, the Data Source that collects the data, the Data Sharing Service that processes the data prior to sharing the data, and Data Using Service which provides services based on the shared data.
  • In addition to the standard DLT roles an additional role called Intermediary is introduced. As described before, the Intermediary facilitates the processing of data on behalf of the Data Subject prior to sharing with a third party.
  • The privacy roles are the standard Data Controller/Processor, Data Subject, and Third-party. To better understand the Data Subject, it is split into two, a client and an agent. The Data Subject has direct control via the Client. The Agent allows the Data Subject to delegate control to the Agent (as a proxy).

The final aspect to understand are the key functions to enable the Intermediary to act on behalf of the Data Subject. The Intermediary requires a privacy function that applies the transformation and the privacy control selected by the Data Subject. For example the Data Subject may give consent to processing anonymized personal data that would be controlled by the privacy engine. The storage function may be in a wallet or a pseudonymized database with restricted access.

Summary

While it may look like most of the work in ToIP relate to VC’s, there is also the work from Inputs and Semantics work group that look at standardizing the storage, portability of the personal data, and creating a layered schema that helps with setting the policy engine when preparing and sharing of the data.

The Data Governance Act can be supported based on the technology being promoted in ToIP Working Groups. The work underway in ToIP Working Groups are aligned with the specific requirements of the Data Governance Act. Both ToIP and the DGA are avoiding a pervasive data ecosystem that promotes the surveillance economy. We both put a data exchange with humans at the center of any data transfer.

A future blog post will look at the Digital Markets Act in relation to ToIP. When an organization exceeds a threshold of users and net income, they are required to adhere to the rules of a Gateway stipulated by the Digital Markets Act. More in the next post.

References

A DIF & ToIP joint Statement of Support for the Decentralized Identifiers (DIDs) v1.0 specification becoming a W3C Standard

By Blog

This statement was co-written by DIF and ToIP.

On 3rd August 2021, the World Wide Web Consortium proposed advancing the Decentralized Identifiers (DIDs) v1.0 specification to their W3C Recommendation stage, the ultimate level of the W3C standards process, which indicates that the specification as currently defined is technically sound, mature and ready for adoption. This includes the expectation that this will allow for widespread implementation, as well as further development and ongoing evaluation, paving the way for future versions.

Collectively, the memberships of the Decentralized Identity Foundation (DIF) and the Trust Over IP (ToIP) Foundation represent over 350 companies globally who are committed to the development and implementation of decentralized identity and trust infrastructure. Many of these organizations have contributed directly or indirectly to the W3C DID 1.0 specification for one simple reason: the DID layer of cryptographically verifiable identifiers is foundational to the common infrastructure we are building together and on top of; therefore, this spec is an integral part of DIF’s and ToIP’s shared vision for an empowered, secure and interoperable future, and in line with W3C TAG Ethical Web Principles.

As such, DIF and ToIP support the Decentralized Identifiers (DIDs) 1.0 specification becoming an official W3C Recommendation. DID 1.0 represents the efforts of over thirty active W3C Working Group contributors over the past two years— on top of contributions from dozens of others in the W3C Credentials Community Group and its predecessors for several years before that. This is a significant milestone in the digital identity sector. Having common ground for development, particularly in terms of interoperability, allows work to continue with renewed energy and focus. It also mitigates the risk of shifting goalposts, which seriously hinders long-term development, investment, and widespread adoption. 

DIDs are a critical part of a technical foundation for the products and activities of many of our members. Many of the implementations in the DID Working Group’s implementation report were developed by engineers and companies who collaborate openly at DIF on points of technical interoperability, and at ToIP on points of policy and governance. DIF also hosts the Universal Resolver, a community project which puts practical intra-DID method interoperability into practice by co-developing a “translation engine” for diverse DIDs with contributions from DIF members and non-members alike. Similarly, other DIF efforts like the DID Communications protocol and the Presentation Exchange protocol and ToIP efforts like the ToIP Trust Registry Protocol serve to align a broad range of implementations and ecosystems already building on these standards, laying the groundwork for robust interoperability across ecosystems and diverse families of technologies.

This specification is the result of half a decade of sustained, broad-based, dedicated work on the part of W3C, DIF, and ToIP members. We acknowledge also the work done by numerous, forward-thinking organizations who have already built working implementations using the provisional specification, thereby laying the foundations of new infrastructures for “identity data”. We believe DIDs will change the course of digital identity by building in better user controls, portability and interoperability at the lowest possible level, while also offering increased security and simplicity for implementers and service providers. This advancement unlocks new opportunities for our digital lives, and we look forward to leveraging DIDs and other technologies developed in the community to champion a new class of user-first, self-owned digital identity systems.

Signed,

DIF & ToIP 

October, 2021

Engaging with the Ontario Digital Identity Program

By Blog

We recently had the honor to host a presentation from our Canadian counterparts in Ontario about their technology roadmap for their Digital Identity (ID) program.

The aim of their program is to “make accessing online and in-person services simpler, safer and more secure”, and they’re aiming to introduce Digital ID later this year.

They’ve been busy since their announcement in October 2020, hosting roundtable discussions with large market participants, surveying and consulting with the public and small-to-medium businesses, developing a tech roadmap to get questions and input from private-sector partners, and publishing the technical tools they’re going to leverage.

A four-step process with accompanying images: Download, Sign up, Add your ID card, and Use your digital ID.
Ontario’s simplified version of how Digital ID will work. Read more on their website.

The recent presentation to the ToIP Foundation was to further their goal of aligning and interoperating with the broader market for digital identity. They recognize the importance of market engagement, technology standards, and of partnering with the private sector in building a digital identity ecosystem. Ultimately, all this will help drive end user adoption and the delivery of value.

The presentation covered:

  • A summary of findings from government-led public consultations on digital identity
  • An overview of Ontario’s Digital ID technology roadmap, and discussions about the technology stacks and infrastructure
  • Ontario’s proposed conceptual model for digital identity, and the principles that inform it

The presentation emphasized how the Government of Ontario’s digital identity strategy and roadmap is building upon the ToIP dual-stack model. It was exciting and gratifying to see a major public sector organization contributing to a digital identity ecosystem based on the interoperable open standards that are the heart of our efforts here at the ToIP Foundation. Equally, we hope that Ontario will benefit through exposure of their efforts to our worldwide presence—and further inspire others to adopt decentralized digital trust infrastructure.

If you are not yet a member of the Trust Over IP Foundation and wish to participate in future state-of-the-art member briefings such as this one, we encourage you to read more about membership.

A Year in Review: New Beginnings and Successes

By Blog

The Internet is one of the most extraordinary developments in human history. It is connecting the world farther, faster, and deeper than any previous communications network. It is steadily digitizing every company, industry, and economy it touches. And it is establishing new pathways for information of all types to flow.

Unfortunately, all of this has come with a growing downside. The Internet wasn’t designed with an integrated layer for digital identity, security, and privacy. As a result, we are now suffering from cybersecurity and cyberprivacy problems so severe that they have at times brought entire companies and industries to their knees.

The Trust Over IP (ToIP) Foundation was launched in May 2020 to tackle this problem at its very core: to define a complete architecture for Internet-scale digital trust. It combines cryptographic assurance at the machine layers and human accountability at the business, legal, and social layers. While ambitious, this mission is so urgent and essential that the Foundation has grown from its initial 27 founding member organizations to over ten times that number in just one year.

As part of the Foundation’s launch, working groups were established from the dedicated efforts of our founding members and volunteers. What those groups have accomplished in their first year has been phenomenal. Specifications, recommendations, guides, white papers, and glossaries have all been delivered. Through the groups’ efforts the Foundation has supported Digital Trust advances in many organizations and operations, especially important as the world grapples with the pandemic and the voluminous increase in everyday online activity.

A curved line showing various ToIP deliverables and new working groups over 2020 and 2021.

Here’s a small taste of what our working groups have been up to since their inception last year.

Technology Stack Working Group (TSWG)

The TSWG provides guidance and specifications that support the ToIP 4-layer model from a technical standpoint.

The TSWG has, amongst many accomplishments:

  • Created and pushed a Task Force recommendation that constructs a mapping of Kim Cameron’s “Laws of Identity”
  • Created a task force in late 2020 to create early specifications for Authentic Chained Data Containers. This task force is focused on the semantics of source provenance, authorization provenance, and delegation.
  • Focused the Interoperability Task Force on the creation of interoperability test suites that leverage and extend the Hyperledger Aries test suites. Multiple underlying Layer-1 technologies are being examined as well. 
  • Focused the Technical Architecture Task Force on building the TSS (ToIP Standard Specification) that defines the overall technical requirements for the four layers of the ToIP Stack
  • Created a Trust Registry Task Force to handle creation of the specifications and API (OpenAPI 3.0 compatible) for trust registries. This work was spawned from the urgent need identified by the Good Health Pass Interoperability Working Group.

Governance Stack Working Group (GSWG)

The GSWG specifies tools, templates, and other resources for developing governance frameworks (collections of rules and policies). These, in turn, support the integration of the legal, business, and social components of Digital Trust.

The GSWG has, amongst many accomplishments:

  • Made steady progress with the ToIP Governance Architecture TSS
  • Advanced the ToIP Governance Metamodel to the point where the GSWB now plans to issue it as a separate specification (apart from the ToIP Governance Architecture TSS), along with an associated Companion Guide
  • Contributed heavily to the governance framework recommendations in the Good Health Pass Interoperability Blueprint
  • Advised the authors of several ToIP-based governance framework projects in the market
  • Initiated a Trust Assurance Task Force focusing on governance risk assessment and accountability
  • Drafted a Risk Assessment Worksheet Template and associated Companion Guide 

Ecosystem Foundry Working Group (EFWG)

The EFWG facilitates a community of practice among governance authorities, implementers, operators, and service providers of Trust over IP Layer-4 ecosystems. 

The EFWG has, amongst many accomplishments:

  • Formed the Internet of Research Ecosystem Task Force to pioneer implementation of academic resource identifiers ecosystems for the research community
  • Created the COVID-19 Credentials Governance Framework Task Force to develop reference materials, best practices, and templates that enable diverse organizations to respond with technology
  • Formed the YOMA Ecosystem Task Force to create a ToIP-based Governance Framework to positively impact youth and local communities around the world
  • Formed the Human Trafficking Safety Response Task Force to research the use of ToIP models to effect the transformation of global human trafficking response
  • Drafted the initial Ecosystem Foundry Concepts and Workflow Model to aid ecosystem development and operation

Utility Foundry Working Group (UFWG) 

As with the EFWG, the UFWG also facilitates a community of practice among governance authorities, implementers, operators, and service providers, but instead for Trust over IP Layer-1 utilities.

The UFWG has, amongst many accomplishments:

  • Worked alongside utility conveners to document their utility into story formats
  • Committed best practice documents to the WG GitHub Repository, such as Decentralized Network Best Practices and Decentralized Network Design Principles
  • Worked to publish a public UFWG paper with which will incorporate many of our outputs as well as case studies from utility projects we’ve interfaced with
  • Committed to expanding the coverage of the UFWG to non-Indy-based ledgers.

Inputs and Semantics Working Group (ISWG) 

The ISWG provides an open forum for discussing the concepts and components that will ultimately shape a Dynamic Data Economy (DDE), a safe and secure decentralized data sharing economy. 

The ISWG has, amongst many accomplishments:

  • Delivered whitepapers such as Decentralized Resource Identifiers in the Research Landscape
  • Contributed to the Good Health Interoperability Blueprint (“GHP Blueprint”), such as for “Standard Data Models and Elements” and “Security, Privacy, and Data Protection”
  • Housed the Health Care Task Force (HCTF) that led to GHP Blueprint recommendations
  • Defined a privacy controller credential to ensure trustworthiness for the use of decentralized identifiers across ecosystems
  • Facilitated several presentations from external presenters of storage and portability solutions
  • Tackled important security concepts such as data correlation attacks, machine-readable data agreements, and data protection requirements

Concepts and Terminology Working Group (CTWG)

The CTWG analyzes and maintains terminology requirements of stakeholder groups within and outside the ToIP Foundation.

The CTWG has, amongst many accomplishments:

  • Maintained glossaries for the reuse of terms across groups, with mapping of terms and definitions across groups to encourage harmonization
  • Surveyed the available terminology development and maintenance tools on the market
  • Authored its own specification for a ToIP Term tool
  • Innovated with an approach called “terms wikis” to enable different stakeholder groups to develop and maintain glossaries in their own contexts.

Interoperability Working Group for Good Health Pass (IWG-GHP)

The IWG-GHP facilitated a community of practice among implementers, issuers, holders, verifiers, governance authorities, and other participants within the Good Health Pass digital trust ecosystem.

The IWG-GHP has, amongst many accomplishments:

  • Authored a blueprint based on an outline created by ID2020, going live in June 2021
  • Coordinated the meeting and responses of ten different drafting groups
  • Completed a 150-page report, the Good Health Pass Interoperability Blueprint, that makes key recommendations on how to reopen global travel with verifiable credentials for sharing COVID-19 health status (tests, vaccinations, and recovery).

There’s More To Do

Our work is just getting started! We encourage anyone interested in Digital Trust to join Trust Over IP and get involved in our working groups.

Read more about membership and find out the latest working group activity.

Here’s to our continued advancements and successes!

Trust over IP Foundation Issues Its First Tools for Managing Risk in Digital Trust Ecosystems

By Blog

The growing interest in verifiable digital credentials, such as mobile driver’s licenses or digital health passes, means companies and governments need new tools for managing risk in this decentralized infrastructure. “Risk management in financial services, such as banking and credit card networks, is a mature field,” said Scott Perry, co-chair of the ToIP Foundation Governance Stack Working Group. “But as we move into decentralized identity management, where individuals manage credentials in their own digital wallets, we need new risk management tools designed for this paradigm.”

To begin to fill this gap, today the Trust Over IP (ToIP) Foundation announced the release of the ToIP Risk Assessment Worksheet (Excel format) and Companion Guide (PDF). These new tools are intended to equip architects of digital governance frameworks — ”rulebooks” for establishing trust online—with the knowledge they need to perform a risk assessment grounded in generally accepted global standards and techniques, including:

  • Proper consideration and identification of potential risks,
  • Critical analysis of risks in terms of likelihood and severity,
  • Calculating a systematic risk impact score,
  • Triaging risks for further treatment,
  • Risk mitigation requirements and strategies,
  • Performance of an annual review to reassess existing risks and consider new ones.

The Risk Assessment Worksheet and Companion Guide provides a step-by-step method of performing a systematic risk assessment that conforms with industry-standard guidance such as ISO/IEC 27005 and NIST 800-30. This process identifies and categorizes risks by likelihood and severity in order to create a risk score that can be color-coded, and stack ranked to highlight the need for countermeasures as shown below. The Worksheet and Companion Guide include enough background and educational content that even risk assessment novices should be able to drive the risk assessment process. “A key missing piece of building open digital trust ecosystems has been a deep understanding of the various risks they introduce.

A table with Scale of Severity across the top, and Scale of Likelihood down the side

This can scare off key stakeholders“, said Darrell O’Donnell, CEO of Continuum Loop and Chair of the ToIP Governance Stack Working Group. “The Risk Assessment Worksheet is a powerful tool that helps create clarity about where the real risks are in an ecosystem and what to do about them.”

The Risk Assessment Worksheet and Companion Guide are the first deliverables from the ToIP Governance Stack Working Group (GSWG), whose mission is to produce a complete suite of tools, models, templates, and guides for digital governance frameworks. GSWG member Vikas Malhotra, CEO of WOPLLI Technologies, explained why risk assessment was at the top of the list: “Willingness to take risks is key to forming trust. A risk assessment process helps to qualify and quanfy the risk in a situation, so that the potential trustor can use the information to understand if they should take the risk or not.”

These new tools for risk assessment are already being put to use by digital trust ecosystems being incubated within the ToIP Ecosystem Foundry Working Group. An example is the YOMA governance framework for youth education and life skills credentials in Africa. “Designing a digital trust ecosystem without first assessing the specific risks it is intended to address is like laying underground pipes without testing them to determine the possibility of leakages” said Frednand Furia, who is leading the Yoma Trust Assurance Task Force. “The ToIP Risk Assessment Worksheet and Companion Guide have already proved to be very effective in architecting the YOMA Rules governance and trust framework.”