Crypto.com

The CDC Vault employs a two-tier security model:

The first layer incorporates a quorum-based approval workflow which allows customers to set up approval rules for transfers, such as requiring multiple sign-offs before a transfer happens. This prevents unauthorized transfers.

The second layer uses advanced cryptography known as Multiparty Computation (MPC) to secure the private keys needed to access funds. MPC allows multiple parties (devices) holding parts of a key generated locally to participate in a transaction signing in a distributed manner. In other words, keys are generated and stored on multiple separate machines in such a way that gaining access to only a single machine at a given time does not compromise the security of the original private key.

1. The first layer incorporates a quorum-based approval workflow which allows customers to set up approval rules for transfers, such as requiring multiple sign-offs before a transfer happens. This prevents unauthorized transfers.
2. The second layer uses advanced cryptography known as Multiparty Computation (MPC) to secure the private keys needed to access funds. MPC allows multiple parties (devices) holding parts of a key generated locally to participate in a transaction signing in a distributed manner. In other words, keys are generated and stored on multiple separate machines in such a way that gaining access to only a single machine at a given time does not compromise the security of the original private key.

Both tiers run within Trusted Execution Environments (TEE) implemented by Intel SGX which provides hardware-level security for storing private keys. TEE is a secure area of a computer’s hardware used to store and execute sensitive data and code, preventing them from being accessed by unauthorized parties or modified in any way.

The Crypto.com Vault provides multi-point failure resilience.

A quorum-based workflow with customer-defined rules prevents unauthorized transactions.

Distributing key generation and storage across multiple machines so compromising one does not compromise the key.

Private keys are never visible to humans or exposed in clear form. It is always secured in encrypted form in the hardware-level enclave.

Private key never exists in one place and hackers would need to compromise multiple devices simultaneously to get access.

All critical operations in the vault are cryptographically signed to guarantee integrity and tamper proof.

Random number generation using Intel RDRAND ensures strong entropy for cryptographic operations.

Keys are re-randomized periodically to thwart potential theft attempts.

Permissions are controlled to prevent misuse or unauthorized access. 

- A quorum-based workflow with customer-defined rules prevents unauthorized transactions.
- Distributing key generation and storage across multiple machines so compromising one does not compromise the key.
- Private keys are never visible to humans or exposed in clear form. It is always secured in encrypted form in the hardware-level enclave.
- Private key never exists in one place and hackers would need to compromise multiple devices simultaneously to get access.
- All critical operations in the vault are cryptographically signed to guarantee integrity and tamper proof.
- Random number generation using Intel RDRAND ensures strong entropy for cryptographic operations.
- Keys are re-randomized periodically to thwart potential theft attempts.
- Permissions are controlled to prevent misuse or unauthorized access.

Backups are encrypted and physically secured by senior management.

Private keys are stored in Intel SGX machine in Singapore and backup of the keys are located outside Singapore.

Crypto.com Vault (Singapore) handles storage, access, transfer, and security of customer’s assets.