Skip to content
FaradAiLab Docs
Enterprise Beta

KMS BYOK & Ephemeral Crypto-Shredding

In enterprise AI deployments, agent tool invocations, prompts, and tool outputs frequently contain sensitive information: customer Personally Identifiable Information (PII), proprietary algorithms, internal database records, and authentication tokens.

While storing audit logs is mandatory for security observability, data retention laws such as GDPR Article 17 (“Right to be Forgotten”), KVKK, and HIPAA require organizations to definitively delete customer data upon request across all backups, logs, and distributed storage systems.

Traditional file deletion across distributed SIEM pipelines, cold object storage, and immutable backups is notoriously complex, slow, and error-prone. FaradAiLab Enterprise Edition solves this fundamentally through KMS BYOK and Ephemeral Crypto-Shredding.

graph TD
    subgraph EnterpriseKMS ["Customer Cloud KMS (AWS / GCP / Vault)"]
        KEK["Customer Key Encryption Key (KEK)\n(Customer Solely Controls Key Lifecycle)"]
    end


    subgraph EncryptionPipeline ["Envelope Encryption Pipeline"]
        SessionStart["Agent Session Initiated"]
        DEKGen["Generate Ephemeral Data Encryption Key (DEK)\n(Per-Session / Per-Tenant AES-256-GCM)"]
        Wrap["Wrap DEK using KMS KEK"]
        EncPayload["Encrypt Telemetry & Prompts with DEK"]


        SessionStart --> DEKGen
        KEK -->|kms:Encrypt / Wrap| Wrap
        DEKGen --> EncPayload
        Wrap --> StoredLog["Audit Record: [Wrapped DEK] + [Ciphertext Payload]"]
        EncPayload --> StoredLog
    end


    subgraph StorageTargets ["Distributed Storage & SIEM"]
        StoredLog --> S3["Cold Object Storage (S3 / GCS)"]
        StoredLog --> SIEM["SIEM Stream (Splunk / Datadog)"]
        StoredLog --> DB["PostgreSQL Audit Database"]
    end


    subgraph CryptoShredding ["Crypto-Shredding Execution"]
        Revoke["Customer Revokes or Deletes KEK in AWS/GCP KMS"]
        Revoke -.->|"Key Revocation Event"| KEK
        Unreadable["All Historical Logs Across S3, SIEM, and DB\nINSTANTLY BECOME PERMANENT CIPHERTEXT NOISE"]
        KEK -.-> Unreadable
    end

The Envelope Encryption Hierarchy

FaradAiLab Enterprise Edition implements a two-tier envelope encryption architecture:

1. Key Encryption Key (KEK) — Customer Managed

  • Customer Sovereign Control: The KEK resides entirely within your cloud provider’s Key Management Service (AWS KMS, Google Cloud KMS, Azure Key Vault, or HashiCorp Vault).
  • Zero Key Export: The raw private key material never leaves your KMS hardware security module (HSM).
  • IAM Least Privilege: FaradAiLab Enterprise Edition requires only kms:GenerateDataKey and kms:Decrypt permissions scoped to your designated Key ARN.

2. Data Encryption Key (DEK) — Ephemeral

  • Granular Scope: A new cryptographic DEK is generated per developer agent session or per customer data subject.
  • AES-256-GCM: Payloads are encrypted locally at the edge using authenticated AES-256-GCM before transmission over the network.
  • Ephemeral Memory Only: The plaintext DEK exists only in volatile memory for the microsecond duration of payload encryption and is immediately scrubbed from RAM.

What is Crypto-Shredding?

Crypto-shredding (cryptographic erasure) is the practice of deliberately deleting, overwriting, or revoking the encryption keys used to encrypt data, rather than attempting to delete the data itself from every distributed replica.

Without the specific KEK:

  • The encrypted Data Encryption Key (DEK) cannot be unwrapped.
  • Without the plaintext DEK, the underlying ciphertext is mathematically impossible to decrypt.
  • The data is rendered permanently unrecoverable, satisfying statutory data deletion standards (including NIST SP 800-88 Rev. 1 Guidelines for Media Sanitization).
sequenceDiagram
    autonumber
    actor Compliance as Privacy Officer / CISO
    participant KMS as Customer AWS/GCP KMS
    participant DB as FaradAiLab Enterprise Edition DB
    participant ColdStorage as Long-Term SIEM / S3 Archives


    Note over Compliance,ColdStorage: Tenant Termination or GDPR Right-to-be-Forgotten Request
    Compliance->>KMS: Disable / Delete Workspace KMS Key (KEK)
    KMS-->>Compliance: Key Status: Disabled / Scheduled for Deletion
    Note over KMS: Immediate Hardware Revocation


    par Control Plane Query
        DB->>KMS: Attempt kms:Decrypt on Wrapped DEK
        KMS-->>DB: Error: KMS.DisabledException (Access Denied)
    and Cold Storage Audit
        ColdStorage->>KMS: Attempt Decrypt on Historical Archive
        KMS-->>ColdStorage: Error: KMS.NotFoundException
    end


    Note over DB,ColdStorage: All telemetry is mathematically irrecoverable noise

Supported KMS Providers & Configuration

Enterprise customers configure their KMS integration via the Control Plane dashboard or infrastructure-as-code:

AWS KMS Example

{
  "provider": "aws_kms",
  "region": "us-east-1",
  "key_arn": "arn:aws:kms:us-east-1:123456789012:key/b4291840-9a28-4f10-bc29-4821a8f90112",
  "encryption_algorithm": "SYMMETRIC_DEFAULT",
  "encryption_context": {
    "tenant_id": "tenant_corp_748291",
    "application": "faradaiwire-ee"
  }
}

Google Cloud KMS Example

{
  "provider": "gcp_kms",
  "key_resource_id": "projects/acme-corp-sec/locations/global/keyRings/ai-agent-ring/cryptoKeys/faradaiwire-key",
  "protection_level": "HSM"
}

HashiCorp Vault (Transit Secrets Engine)

{
  "provider": "hashicorp_vault",
  "address": "https://vault.internal.acme.corp:8200",
  "transit_mount": "transit",
  "key_name": "ai-proxy-telemetry-key",
  "auth_method": "approle"
}

Compliance Certifications & Audit Proof

Crypto-shredding operations generate a tamper-evident Certificate of Erasure signed by FaradAiLab Enterprise Edition, verifying:

  • The timestamp of key revocation.
  • The affected tenant and session identifiers.
  • Confirmation of failed decryption attempts against stored ciphertext samples.

This certificate serves as verifiable cryptographic proof for external SOC-2 Type II, ISO 27701, and KVKK regulatory auditors.

Next Steps