> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/security-and-support/security/post-quantum-cryptography.md).

# Post-Quantum Cryptography

## Summary

Datalink follows ASD and AWS best practice in terms of adopting its encryption to post-quantum computing standard.

Crisisworks protects data in transit with TLS 1.2 and 1.3 and protects stored data with AES-256 encryption, using algorithms approved in the Australian Signals Directorate's Information Security Manual (ISM). The user-facing application and GraphQL endpoints already support **hybrid post-quantum key exchange (X25519MLKEM768)** for clients that offer it.  Digital signatures, such as certificates and authentication tokens, use classical RSA algorithms because post-quantum signatures aren't yet supported by browsers or public certificate authorities.

## Cryptographic inventory

<table data-header-hidden="false" data-header-sticky data-search="false"><thead><tr><th width="189.97265625">Area</th><th width="484.7265625">Mechanism</th><th>PQ Ready</th></tr></thead><tbody><tr><td><strong>Application and GraphQL endpoints</strong> (web app, real-time data)</td><td>TLS 1.2 and 1.3. TLS 1.3 clients that support post-quantum key exchange negotiate hybrid X25519MLKEM768. Other clients use classical ECDHE.</td><td>Yes</td></tr><tr><td><strong>API endpoints</strong></td><td>TLS 1.2 and 1.3. TLS 1.3 clients that support post-quantum key exchange negotiate hybrid X25519MLKEM768. Other clients use classical ECDHE.</td><td>Yes</td></tr><tr><td><strong>Symmetric encryption in transit</strong></td><td>AES-GCM (128-bit or 256-bit, negotiated by TLS).</td><td>Yes</td></tr><tr><td><strong>Server certificates</strong></td><td>RSA-2048, issued by AWS Certificate Manager.</td><td>No <sup>[1]</sup></td></tr><tr><td><strong>Encryption at rest: database</strong></td><td>Amazon Aurora storage encrypted with AES-256 using a customer-managed AWS KMS key.</td><td>Yes</td></tr><tr><td><strong>Encryption at rest: files</strong></td><td>Customer file storage and the file-sharing service use AES-256 with customer-managed AWS KMS keys. The shared file system is also encrypted.</td><td>Yes</td></tr><tr><td><strong>Encryption at rest: backups</strong></td><td>Encrypted with a customer-managed AWS KMS key.</td><td>Yes</td></tr><tr><td><strong>Key management</strong></td><td>AWS Key Management Service (KMS), using Datalink-managed (customer-managed) keys for the database, file storage and backups.</td><td>Yes</td></tr><tr><td><strong>Authentication</strong></td><td>OAuth 2.0 and OpenID Connect through Amazon Cognito, with SAML and OIDC federation to customer identity providers. Multi-factor authentication is available. Authentication tokens are signed JWTs (RS256, RSA-2048).</td><td>No <sup>[2]</sup></td></tr><tr><td><strong>Password storage</strong></td><td>Salted one-way hashes. Passwords are never stored reversibly.</td><td>Yes</td></tr><tr><td><strong>Digital signatures</strong></td><td>RSA-2048 (certificates, tokens).</td><td>No <sup>[3]</sup></td></tr><tr><td><strong>Certificate-based authentication</strong></td><td>Not used for end users.</td><td>N/A</td></tr><tr><td><strong>PKI</strong></td><td>AWS-managed certificate authorities. Datalink does not operate its own PKI.</td><td>No <sup>[4]</sup></td></tr><tr><td>Fileshare Utility</td><td>TLS 1.2 and 1.3 with classical key exchange (ECDHE)</td><td>No <sup>[5]</sup></td></tr></tbody></table>

Footnotes:

<table><thead><tr><th width="83.28515625">#</th><th>Why it’s “No”</th></tr></thead><tbody><tr><td><strong>#1, #3</strong></td><td>Browsers and public certificate authorities don’t yet accept post-quantum certificates</td></tr><tr><td><strong>#2, #3</strong></td><td>SAML and OIDC federation depend on each customer’s identity provider and on how the standards define PQ signatures. PQ algorithm support for JWT/JOSE is still in draft, and the standards bodies have not adopted PQ yet.</td></tr><tr><td><strong>#4</strong></td><td>Datalink uses AWS Certificate Manager’s for PKI, which issues only classical certificates. The public web trust system hasn’t adopted PQ yet.</td></tr><tr><td>#5</td><td>PQ pending AWS support for HTTP APIs</td></tr></tbody></table>

## Post-quantum position

Datalink continually assesses the technical environment to ensure it adapts post-quantum standards as they become available.

### **What is protected today**

Quantum computers threaten key exchange and digital signatures, not AES-256 data at rest.&#x20;

AES-256 remains strong against known quantum attacks, so stored data is protected. For data in transit, the application and GraphQL endpoints negotiate a hybrid of classical X25519 and the NIST-standardised ML-KEM-768 algorithm.&#x20;

This protects recorded traffic from being decrypted later ("harvest now, decrypt later") when the client supports it.

### **Where we are still classical**

* **Clients.** Post-quantum key exchange requires TLS 1.3 and a client that offers it. Older browsers, older devices and networks with TLS-intercepting proxies use classical key exchange.
* **Digital signatures.** Certificates and authentication tokens use RSA-2048. Post-quantum signature algorithms (such as ML-DSA) are not yet accepted by browsers or public certificate authorities, so Datalink will move to them as they become supported by the platforms we run on.

### **Roadmap**

Datalink's Cryptography and Encryption Policy requires algorithms and protocols from ASD's approved lists. Datalink tracks ASD's post-quantum transition guidance and the post-quantum capabilities of Amazon Web Services and adopts them as they become available.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cw.crisisworks.com/security-and-support/security/post-quantum-cryptography.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
