> For the complete documentation index, see [llms.txt](https://bdi.gitbook.io/bdi-public-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bdi.gitbook.io/bdi-public-documentation/readme/trust-kit.md).

# Trust KIT

## 1. Introduction

The Trust KIT serves as the foundational pillar of the Basic Data Infrastructure (BDI), ensuring secure and reliable data exchange within a BDI Association. As the core KIT, it integrates critical capabilities that empower organizations to establish and operate a BDI Association while leveraging the BDI Identity, Authentication, and Authorization (IAA) solution. The Trust KIT is essential for authorizing and delegating data access through established APIs, offering a robust framework for managing trust relationships and data governance.

{% hint style="info" %}
Trust is the measure to which one believes that another entity (being a person, an organization or a support system) is willing and able to fulfill an agreement. Measures can be in place to increase trust. For instance, encryption, signing certificates and the Public Key Infrastructure (PKI) are in place to increase trust in a message exchange over the internet.
{% endhint %}

### 1.1 Trust in the BDI

The BDI is mainly concerned with trust at the business level, i.e. trust between parties in a business transaction. However, as data exchange over a network is crucial for the BDI, we make extensive use of tools and techniques to increase trust at a technical level.

### 1.2 The Trust KIT

The Trust KIT is inspired by the iSHARE Trust Framework, and uses some of the concepts and components from iSHARE. However, the BDI is not identical to iSHARE.

At its core, the Trust KIT encompasses vital building blocks, including IAA functions that provide the necessary identity and access management capabilities. The Association Register and Authorization Registers enable the secure recording of membership and authorization rights. Discovery and Onboarding processes ensure that members can be seamlessly integrated into the BDI, guided by clearly defined Terms & Conditions and structured process flows. Furthermore, Policy Agreements and Edge Agreements provide the necessary governance framework to ensure that all data interactions comply with agreed-upon standards and regulations.

## 2. Building blocks

The Trust KIT comprises the following building blocks:

<a href="/pages/PzHHCnAho0g45UwG6l7z" class="button secondary">Association Register</a> <a href="/pages/MPLEjPt5kabk8CZYvGea" class="button secondary">Onboarding terms and conditions</a> <a href="/pages/ocDuAH4FVgsfATml7kiy" class="button secondary">Digital identity</a>

<a href="/pages/khlL3SkrlRt47EjJHagB" class="button secondary">Authentication</a> <a href="https://github.com/Basic-Data-Infrastructure/BDI-Reference-Architecture/blob/main/readme/trust-kit/authorisation-oauth-2.0-ar-dm-+-xacml-policies" class="button secondary">Authorization</a> <a href="/pages/QoRjWMRXGekMFBBkQ8yF" class="button secondary">Discovery</a> <a href="/pages/ZEAxgui2EiTYQwj4n2Sp" class="button secondary">Policy Agreements</a>

<a href="/pages/evJF88VmTCLo696Ht6Qd" class="button secondary">Edge Agreements</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bdi.gitbook.io/bdi-public-documentation/readme/trust-kit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
