> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/architecture-and-security/cryptographic-architecture.md).

# Cryptographic architecture

Cifer uses hybrid encryption so that post-quantum key establishment protects efficient symmetric payload encryption.

## Encryption

1. Resolve the secret's ML-KEM-768 public key.
2. Encapsulate to derive a shared secret.
3. Derive or use the shared material for AES-256-GCM.
4. Return the Cifer envelope and encrypted payload.

## Decryption

1. Authenticate the owner, delegate, permit, or active Web2 session.
2. Validate request freshness and authorization.
3. Reconstruct the required protected operation across the enclave cluster.
4. Decapsulate the Cifer material.
5. Authenticate and decrypt the AES-GCM ciphertext.

## Key placement

| Material                     | Location                                                               |
| ---------------------------- | ---------------------------------------------------------------------- |
| Public key                   | Addressed through its IPFS CID                                         |
| Private-key material         | Split as threshold shards across the enclave cluster                   |
| Ownership and delegate state | SecretsController                                                      |
| Application ciphertext       | Chosen by the integrating application                                  |
| File job output              | Blackbox workflow until downloaded/expired according to service policy |

Cifer's design reduces dependence on a single conventional key store. Security still depends on correct SDK use, enclave and cluster operation, authorization policy, and integrator key handling.


---

# 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://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/architecture-and-security/cryptographic-architecture.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.