# Protocols

Ockam is composed of a collection of cryptographic and messaging protocols. These protocols make it possible to create **private** and **secure by design** applications that provide end-to-end application layer trust it data. The following pages explain, in detail, how each of the protocols work:

* [<mark style="color:blue;">Nodes and Workers</mark>](/documentation/protocols/nodes.md)
* [<mark style="color:blue;">Routing and Transports</mark>](/documentation/protocols/routing.md)
* [<mark style="color:blue;">Keys and Vaults</mark>](/documentation/protocols/keys.md)
* [<mark style="color:blue;">Identities and Credentials</mark>](/documentation/protocols/identities.md)
* [<mark style="color:blue;">Secure Channels</mark>](/documentation/protocols/secure-channels.md)
* [<mark style="color:blue;">Access Controls and Policies</mark>](/documentation/protocols/access-controls.md)

<figure><img src="/files/gHNxJLyqavHhcM8MgySn" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/hOWxqWX75ftbjcOi2tdp" alt=""><figcaption></figcaption></figure>

## Ockam has been audited and verified by experts

A team of security and cryptography experts, from Trail of Bits, conducted an extensive review of Ockam’s protocols. Trail of Bits is renowned for their comprehensive third-party audits of the security of many other critical projects, including Kubernetes and the Linux kernel.

The auditors from Trail of Bits conducted in-depth, manual analysis, and formal modeling of the security properties of Ockam’s protocols. After this review was complete, they highlighted:

> *Ockam’s protocols use robust cryptographic primitives according to industry best practices. None of the identified issues pose an immediate risk to the confidentiality and integrity of data handled by the system in the context of the two in-scope use cases. The majority of identified issues relate to information that should be added to the design documentation, such as threat model details and increased specification for certain aspects.*
>
> *— Trail of Bits*

### **Download the unabridged audit by Trail of Bits:**

{% file src="/files/7egsA2WpJ0uhGB20tdKb" %}


---

# Agent Instructions: 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:

```
GET https://docs.ockam.io/documentation/protocols.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.