Security Whitepaper

Executive Summary

ZeroCopy Systems provides hardware-isolated signing infrastructure built on AWS Nitro Enclaves. Our architecture eliminates the need for trust in operators, administrators, or cloud providers by enforcing cryptographic isolation at the hardware level.

Core Security Properties

• Hardware Isolation: Private keys exist only in encrypted enclave memory. No root access, no SSH, no debugging interfaces.
• Cryptographic Attestation: Every request includes a PCR0 measurement proving the exact enclave code running.
• Zero-Knowledge Architecture: ZeroCopy employees cannot access keys, even under subpoena.
• Reproducible Builds: Enclave images are designed for independent verification of source code. Build reproducibility tooling is under development.

Threat Model

Architecture Overview

The system consists of three layers:

1. Client Layer: User-controlled application (trading bot, wallet, AI agent)
2. Sidecar Layer: Vsock proxy running on parent EC2 instance
3. Enclave Layer: Nitro Enclave with signing logic and policy engine (6 rule types: notional limits, rate limiting, contract whitelist/blacklist, chain restrictions, time windows, AI risk scoring)

Compliance

Our architecture is designed to meet the following regulatory requirements:

• SEC 17a-4: Immutable audit logs with hash chaining
• MiCA (EU): Operational resilience and key custody controls
• EU AI Act Article 14: Hardware-enforced human oversight via kill switch and policy engine
• SOC 2: Type I planned (via Vanta/Drata). Type II to follow after 6-month observation period.

Independent Verification

All claims in this whitepaper can be independently verified:

Contact

For security inquiries or to report vulnerabilities, contact: [email protected]