> For the complete documentation index, see [llms.txt](https://docs.hardpoint.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hardpoint.dev/security.md).

# Security

## Security

Hardpoint is infrastructure that sits in the connection path between your application and your data. We take that position seriously.

This page describes our security posture for developers and operators evaluating Hardpoint. Security engineers and compliance reviewers should refer to the [Threat Model](https://docs.hardpoint.dev/threat-model.md).

***

## Zero Trust, Zero Passwords

Application code connecting through Hardpoint never handles passwords, connection strings, or static secrets. Every connection is authenticated using short-lived cryptographic credentials tied to a verified identity. There is no privileged bypass path — including for schema migrations and administrative operations.

At the infrastructure layer, data store credentials are managed exclusively by Hardpoint's control plane, rotated continuously, and never accessible to human operators after initial provisioning.

***

## Encryption

All traffic between the Hardpoint SDK and destination agents is encrypted end-to-end using TLS 1.3 with an additional ML-KEM (post-quantum key encapsulation) layer. Session keys are ephemeral and unique per request. The relay infrastructure that forwards your traffic cannot decrypt it.

Data at rest is encrypted with AES-256 using per-tenant keys managed via HSM-backed key management. Tenant key material is isolated — a compromise of one tenant's keys has no effect on others. Customer-managed keys (BYOK) are supported; where used, Hardpoint cannot access your data at rest under any circumstance.

Quantum resistance is a baseline requirement for all cryptography in Hardpoint, not an optional feature. We do not adopt mechanisms that do not meet this bar.

***

## The Relay Is Not Trusted

Hardpoint's relay mesh is operated by us but is explicitly untrusted by design. Relays forward traffic blindly — they cannot inspect content, cannot forge authorisation decisions, and cannot impersonate the control plane. This is enforced cryptographically, not by policy.

Your data is not readable by Hardpoint's own relay infrastructure.

***

## Audit Logging

Every query routed through Hardpoint is logged at the agent layer before the underlying data store processes it. Log records include the tenant identity, originating service, verified actor identity, and request trace — not just the query itself. Logs are shipped to an append-only sink before execution, making them tamper-resistant by construction.

They can be optionally anchored to an independent [RFC 3161](https://en.wikipedia.org/wiki/Time_stamp_protocol) Time Stamping Authority for third party verification.

***

## Traffic Separation

Relay infrastructure is provisioned per customer. For private cloud deployments, relays operate entirely within your VPC and never traverse the public internet. For internet-facing deployments, traffic is protected at the Cloudflare edge.

In both cases, the cryptographic tunnel between SDK and agent means separation is enforced at the content layer, not just the network layer.

***

## What We Deliberately Don't Cover

Hardpoint does not attempt to protect against cloud provider-level attacks, compromise of your configured identity providers, or client-side compromise of processes holding valid credentials.&#x20;

These are documented explicitly in the [Threat Model](https://docs.hardpoint.dev/threat-model.md) alongside the reasoning.

***

## Responsible Disclosure

If you've found a security issue, please contact us at <security@hardpoint.dev>.

You may use our [Security](https://docs.hardpoint.dev/security.md#pgp-public-key) to encrypt any sensitive messages.

We aim to acknowledge reports within 24 hours.

***

## PGP Public Key

Hardpoint Labs' PGP key can be found on most popular public PGP key servers. The fingerprint of the latest valid key is `A001 1B53 6778 11D4 5B58 46F1 876B 5ECC E613 72AE`.
