Token Vault
Docs
TerminologyHow It Works
Token Vault
Engineering

Terminology

A comprehensive guide to the technical terminology used by Token Vault.

Core Concepts

TermDescription
VaultThe core encryption service that handles secret encryption, decryption, and key management
SecretEncrypted data payload stored in the vault, accessible only through proper authentication
ProjectA logical container for secrets with isolated encryption keys and access controls
OrganizationA tenant boundary that contains multiple projects and manages user access
Project IdentifierUnique identifier used for key isolation and secret lookup

Encryption & Key Management

TermDescription
Root Key (KEK)Master encryption key loaded from environment variables, used to encrypt all DEKs
DEKData Encryption Key - project-specific 256-bit key used to encrypt secret payloads
AES-256-GCMAuthenticated encryption algorithm used for all encryption operations
AADAdditional Authenticated Data - context metadata ensuring encryption integrity
Nonce96-bit random value used once per encryption operation for security
KeyringService managing DEK lifecycle including creation, storage, and retrieval

API & Authentication

TermDescription
API KeyAuthentication token scoped to specific projects for programmatic access
Proxy APIEndpoint that forwards requests to target APIs while injecting secrets
Secret ReferenceUnique identifier used to reference encrypted secrets in requests
Project IdentifierProject-specific identifier used for key lookup and secret isolation

Request Processing

TermDescription
Secret InjectionProcess of decrypting secrets and inserting them into proxied requests
Header InjectionMethod of injecting secrets into HTTP request headers
Query InjectionMethod of injecting secrets into URL query parameters
Body InjectionMethod of injecting secrets into request body using JSON path notation
Request LoggingAudit trail recording all proxy requests and secret usage

Security & Isolation

TermDescription
Project IsolationCryptographic boundary ensuring secrets are inaccessible across projects
Organization BoundaryAccess control boundary preventing cross-organization data access
Forward SecrecyCryptographic property ensuring compromised keys don't affect historical data
Authenticated EncryptionEncryption method that provides both confidentiality and integrity

Storage & Infrastructure

TermDescription
S3 StorageObject storage service used for encrypted DEK and secret data persistence
PostgreSQLRelational database storing metadata, audit logs, and system state
TransactionAtomic database operation ensuring consistency during project creation
Audit LogImmutable record of all system operations with user and IP context

Technical Implementation

TermDescription
VaultServiceCore encryption service class handling encrypt/decrypt operations
KeyringService managing DEK lifecycle and S3 storage operations
dot-propLibrary used for JSON path-based secret injection into request bodies
CUID2Collision-resistant unique identifier generator for system entities

Proxy a request to a url POST

Previous Page

How It Works

Technical architecture and implementation details of Token Vault's encryption and proxy system.

On this page

Core ConceptsEncryption & Key ManagementAPI & AuthenticationRequest ProcessingSecurity & IsolationStorage & InfrastructureTechnical Implementation