Payload Encryption & SSR Security

Native, zero-dependency AES-256-GCM in-flight payload encryption and decryption for zero-trust data storage, client-side protection, and SSR memory guards.

๐Ÿ”’ CWebCryptoEncryptionProvider ยท ๐Ÿ›๏ธ AEncryptionProvider ยท ๐Ÿ“‹ IProviderEncryptionOptions ยท ๐Ÿ”Œ IEncryptionProvider

End-to-End Encryption Architecture

The Katlux encryption pipeline uses the built-in CWebCryptoEncryptionProvider (which extends AEncryptionProvider and implements IEncryptionProvider) using the standard Web Crypto API (crypto.subtle) to encrypt sensitive payloads on the client before sending them across the network and decrypt incoming ciphertext on the fly.

SSR Security Guard (decryptOnSSR: false): When disabled during Server-Side Rendering, raw ciphertext is preserved in server memory, logs, and serialized SSR payloads (__NUXT_DATA__). Decryption is automatically deferred until client-side hydration in the browser.

E2EE Threat Model & Multi-User SaaS Scope: Designed to eliminate risk from catastrophic server-side or database leaks. All GDPR data is stored as ciphertext in the database. Shared access across users in the same tenant is governed by database roles holding encrypted/wrapped keys. Local device protection against trojans/malware is out of scope and remains the endpoint device owner's responsibility.

Configured via IProviderEncryptionOptions on data providers (such as ADataProvider implementations) or directly on RequestProvider and IRequestOptions.

Live Cryptographic Sandbox

โš ๏ธ Production Security Notice: Never hardcode master secrets or passphrases in production frontend source code. In production applications, obtain keys dynamically from an authenticated session or secure key agreement.