@memberjunction/encryption

Server-side field-level encryption engine for MemberJunction with pluggable key sources. This package provides transparent encrypt-on-save and decrypt-on-load operations for entity fields, configurable entirely through database metadata. It supports AES-256-GCM authenticated encryption, multiple key source backends (environment variables, configuration files, AWS KMS, Azure Key Vault), and full key rotation with transactional safety.

Installation

npm install @memberjunction/encryption
Copy

For cloud key management, install the optional provider dependencies:

# AWS KMS support
npm install @aws-sdk/client-kms

# Azure Key Vault support
npm install @azure/keyvault-secrets @azure/identity
Copy

Overview

The encryption package sits between MemberJunction's entity system and the database, intercepting save and load operations on fields marked for encryption. When a field has Encrypt = true in its EntityField metadata, the engine automatically encrypts the value before writing to the database and decrypts it when reading, providing application-level transparency.

The system is designed around three database-driven configuration entities -- Encryption Keys, Encryption Algorithms, and Encryption Key Sources -- which together define what key material to use, which algorithm to apply, and where to retrieve the raw key bytes from. This metadata-driven approach means encryption can be enabled or disabled on individual fields without code changes.

flowchart TD
    subgraph App["Application Layer"]
        Entity["Entity Save/Load"]
    end

    subgraph Engine["EncryptionEngine"]
        Encrypt["Encrypt()"]
        Decrypt["Decrypt()"]
        Cache["Key Material Cache\n5-min TTL"]
    end

    subgraph Sources["Key Source Providers"]
        ENV["EnvVarKeySource"]
        CFG["ConfigFileKeySource"]
        AWS["AWSKMSKeySource"]
        AZR["AzureKeyVaultKeySource"]
        CUST["Custom Provider"]
    end

    subgraph DB["Database"]
        Meta["Encryption Metadata\nKeys / Algorithms / Sources"]
        Data["Encrypted Field Data\n$ENC$..."]
    end

    Entity --> Encrypt
    Entity --> Decrypt
    Encrypt --> Cache
    Decrypt --> Cache
    Cache --> ENV
    Cache --> CFG
    Cache --> AWS
    Cache --> AZR
    Cache --> CUST
    Encrypt --> Data
    Decrypt --> Data
    Engine --> Meta

    style App fill:#2d6a9f,stroke:#1a4971,color:#fff
    style Engine fill:#7c5295,stroke:#563a6b,color:#fff
    style Sources fill:#2d8659,stroke:#1a5c3a,color:#fff
    style DB fill:#b8762f,stroke:#8a5722,color:#fff
Copy

Key Features

• AES-256-GCM Encryption -- Industry-standard authenticated encryption (AEAD) that prevents both eavesdropping and tampering
• Pluggable Key Sources -- Environment variables, config files, AWS KMS, Azure Key Vault, or custom providers via the ClassFactory pattern
• Declarative Configuration -- Enable encryption on any entity field via database metadata without code changes
• Transparent Operation -- Automatic encryption on save and decryption on load
• Key Rotation Support -- Full re-encryption with transactional safety, batch processing, and progress tracking
• Secure Defaults -- API responses hide encrypted fields by default; plaintext must be explicitly opted into
• Self-Describing Format -- Encrypted values embed the key ID, algorithm, IV, ciphertext, and auth tag for algorithm-agnostic decryption
• Multi-Level Caching -- Key configurations and key material are cached with configurable TTL for performance

Quick Start

1. Set Up an Encryption Key

Generate a 256-bit (32-byte) encryption key:

openssl rand -base64 32
Copy

Store it in an environment variable:

export MJ_ENCRYPTION_KEY_PII=your-base64-key-here
Copy

2. Register the Key in the Database

After running the encryption migration, register your key:

INSERT INTO [${flyway:defaultSchema}].[EncryptionKey] (
    ID, Name, Description, EncryptionKeySourceID, EncryptionAlgorithmID,
    KeyLookupValue, KeyVersion, Marker, IsActive, Status, ActivatedAt
)
VALUES (
    NEWID(),
    'PII Master Key',
    'Encryption key for personally identifiable information',
    '38A961D2-022B-49C2-919F-1825A0E9C6F9',  -- EnvVarKeySource
    'B2E88E95-D09B-4DA6-B0AE-511B21B70952',  -- AES-256-GCM
    'MJ_ENCRYPTION_KEY_PII',
    '1',
    '$ENC$',
    1,
    'Active',
    SYSDATETIMEOFFSET()
);
Copy

3. Enable Encryption on Entity Fields

Update EntityField metadata to enable encryption:

UPDATE [${flyway:defaultSchema}].[EntityField]
SET Encrypt = 1,
    EncryptionKeyID = 'your-key-id-here',
    AllowDecryptInAPI = 0,  -- Secure default: don't send plaintext to clients
    SendEncryptedValue = 0  -- Secure default: send null instead of ciphertext
WHERE Entity = 'Contacts'
  AND Name IN ('SSN', 'TaxID', 'BankAccountNumber');
Copy

4. Encrypt Existing Data

After enabling encryption on a field, run the action to encrypt existing plaintext data:

import { EnableFieldEncryptionAction } from '@memberjunction/encryption';

const action = new EnableFieldEncryptionAction();
const result = await action.Run({
    Params: [
        { Name: 'EntityFieldID', Value: 'field-uuid-here' },
        { Name: 'BatchSize', Value: 100 }
    ],
    ContextUser: currentUser
});
Copy

Architecture

Class Hierarchy

classDiagram
    class BaseEngine {
        +Config()
        +Load()
        +Loaded: boolean
    }

    class EncryptionEngineBase {
        +EncryptionKeys: EncryptionKeyEntity[]
        +EncryptionAlgorithms: EncryptionAlgorithmEntity[]
        +EncryptionKeySources: EncryptionKeySourceEntity[]
        +GetKeyByID(keyId)
        +GetKeyConfiguration(keyId)
        +ValidateKey(keyId)
    }

    class EncryptionEngine {
        +Instance: EncryptionEngine
        +Encrypt(plaintext, keyId, user)
        +Decrypt(value, user)
        +IsEncrypted(value)
        +ParseEncryptedValue(value)
        +ValidateKeyMaterial(lookup, keyId, user)
        +EncryptWithLookup(plaintext, keyId, lookup, user)
        +ClearCaches()
    }

    class EncryptionKeySourceBase {
        +SourceName: string
        +ValidateConfiguration()
        +GetKey(lookupValue, version)
        +KeyExists(lookupValue)
        +Initialize()
        +Dispose()
    }

    class EnvVarKeySource
    class ConfigFileKeySource
    class AWSKMSKeySource
    class AzureKeyVaultKeySource

    BaseEngine <|-- EncryptionEngineBase
    EncryptionEngineBase <|-- EncryptionEngine
    EncryptionKeySourceBase <|-- EnvVarKeySource
    EncryptionKeySourceBase <|-- ConfigFileKeySource
    EncryptionKeySourceBase <|-- AWSKMSKeySource
    EncryptionKeySourceBase <|-- AzureKeyVaultKeySource

    EncryptionEngine --> EncryptionKeySourceBase : resolves via ClassFactory

    style EncryptionEngine fill:#7c5295,stroke:#563a6b,color:#fff
    style EncryptionEngineBase fill:#2d6a9f,stroke:#1a4971,color:#fff
    style EncryptionKeySourceBase fill:#2d8659,stroke:#1a5c3a,color:#fff
Copy

The EncryptionEngineBase (defined in @memberjunction/core-entities) provides metadata caching for encryption keys, algorithms, and key sources. It works in both client and server contexts. The EncryptionEngine in this package extends it with actual cryptographic operations using Node.js crypto, making it server-side only.

Encrypted Value Format

Encrypted values are stored as self-describing strings that embed everything needed for decryption:

$ENC$<keyId>$<algorithm>$<iv>$<ciphertext>$<authTag>
Copy

For example:

$ENC$550e8400-e29b-41d4-a716-446655440000$AES-256-GCM$Base64IV$Base64Ciphertext$Base64AuthTag
Copy

This format enables:

• Quick detection of encrypted values via the $ENC$ marker
• Identification of which key was used (for multi-key environments)
• Algorithm-agnostic decryption
• Key rotation without format changes

Encryption and Decryption Flow

sequenceDiagram
    participant App as Application
    participant EE as EncryptionEngine
    participant Cache as Key Cache
    participant KS as Key Source
    participant Crypto as Node.js crypto

    Note over App,Crypto: Encryption Flow
    App->>EE: Encrypt(plaintext, keyId, user)
    EE->>EE: buildKeyConfiguration(keyId)
    EE->>Cache: Check key material cache
    alt Cache miss
        Cache->>KS: GetKey(lookupValue, version)
        KS-->>Cache: Buffer (raw key bytes)
    end
    Cache-->>EE: Key material (Buffer)
    EE->>Crypto: createCipheriv(algo, key, randomIV)
    Crypto-->>EE: Ciphertext + Auth Tag
    EE-->>App: $ENC$keyId$algo$iv$ciphertext$authTag

    Note over App,Crypto: Decryption Flow
    App->>EE: Decrypt(encryptedValue, user)
    EE->>EE: ParseEncryptedValue(value)
    EE->>EE: buildKeyConfiguration(parsed.keyId)
    EE->>Cache: Check key material cache
    Cache-->>EE: Key material (Buffer)
    EE->>Crypto: createDecipheriv(algo, key, iv)
    Crypto-->>EE: Plaintext
    EE-->>App: Decrypted string
Copy

API Response Behavior

The encryption system provides secure-by-default API responses controlled by two EntityField flags:

Key Source Providers

Environment Variable (Default)

The simplest option -- store keys in environment variables. Best for development and containerized deployments with secret injection.

# Generate a 256-bit key
openssl rand -base64 32

# Set in environment
export MJ_ENCRYPTION_KEY_PII=your-base64-key-here
Copy

Database configuration:

• EncryptionKeySourceID: 38A961D2-022B-49C2-919F-1825A0E9C6F9
• KeyLookupValue: Environment variable name (e.g., MJ_ENCRYPTION_KEY_PII)

For versioned keys (during rotation), the provider appends _V{version} to the variable name (e.g., MJ_ENCRYPTION_KEY_PII_V2 for version 2).

Configuration File

Store keys in mj.config.cjs (not recommended for production):

module.exports = {
    encryptionKeys: {
        pii_master_key: 'base64-encoded-key-here'
    }
};
Copy

Database configuration:

• EncryptionKeySourceID: CBF9632D-EF05-42E2-82F6-5BAC79FAA565
• KeyLookupValue: Key name in config (e.g., pii_master_key)

Uses cosmiconfig to locate configuration files in standard locations (mj.config.cjs, mj.config.js, .mjrc.json, .mjrc.yaml).

AWS KMS

Uses AWS Key Management Service with envelope encryption. The raw key is encrypted by a KMS Customer Master Key (CMK) and decrypted at runtime.

Setup:

1. Create a symmetric CMK in AWS KMS
2. Generate a data key:

   aws kms generate-data-key \
     --key-id alias/your-cmk-alias \
     --key-spec AES_256 \
     --query 'CiphertextBlob' \
     --output text
   Copy

3. Store the output (base64 CiphertextBlob) as the KeyLookupValue

Authentication: Uses the standard AWS credential chain (environment variables, IAM role, shared credentials file).

Database configuration:

• EncryptionKeySourceID: D8E4F521-3A7B-4C9E-8F12-6B5A4C3D2E1F
• KeyLookupValue: Base64-encoded CiphertextBlob from GenerateDataKey

Azure Key Vault

Retrieves keys from Azure Key Vault secrets.

Setup:

1. Create an Azure Key Vault
2. Create a secret containing your base64-encoded key:

   KEY=$(openssl rand -base64 32)
   az keyvault secret set \
     --vault-name your-vault-name \
     --name mj-encryption-key \
     --value "$KEY"
   Copy

Authentication: Uses DefaultAzureCredential (Managed Identity, service principal, or Azure CLI).

Database configuration:

• EncryptionKeySourceID: A2B3C4D5-E6F7-8901-2345-6789ABCDEF01
• KeyLookupValue: Full secret URL or just the secret name (if AZURE_KEYVAULT_URL is set)

# With AZURE_KEYVAULT_URL set, use short names:
export AZURE_KEYVAULT_URL=https://your-vault.vault.azure.net
# Then KeyLookupValue can be: mj-encryption-key
Copy

Custom Provider

Extend EncryptionKeySourceBase to integrate any key management system:

import { RegisterClass } from '@memberjunction/global';
import { EncryptionKeySourceBase } from '@memberjunction/encryption';

@RegisterClass(EncryptionKeySourceBase, 'HashiCorpVaultKeySource')
export class HashiCorpVaultKeySource extends EncryptionKeySourceBase {
    get SourceName(): string { return 'HashiCorp Vault'; }

    ValidateConfiguration(): boolean {
        return !!process.env.VAULT_ADDR && !!process.env.VAULT_TOKEN;
    }

    async GetKey(lookupValue: string): Promise<Buffer> {
        // Implement vault API call to retrieve secret
        // Return the key as a Buffer
    }

    async KeyExists(lookupValue: string): Promise<boolean> {
        // Check if secret exists at path
    }
}
Copy

The provider lifecycle is: Construction -> Initialize() (async setup) -> GetKey()/KeyExists() (per-operation) -> Dispose() (cleanup).

Programmatic API

EncryptionEngine

The EncryptionEngine is a singleton accessed via EncryptionEngine.Instance:

import { EncryptionEngine } from '@memberjunction/encryption';

const engine = EncryptionEngine.Instance;

// Encrypt a value
const encrypted = await engine.Encrypt(
    'sensitive-data',
    encryptionKeyId,
    contextUser
);

// Decrypt a value (non-encrypted values pass through unchanged)
const decrypted = await engine.Decrypt(encrypted, contextUser);

// Check if a value is encrypted
if (engine.IsEncrypted(someValue)) {
    const parts = engine.ParseEncryptedValue(someValue);
    console.log(`Encrypted with key: ${parts.keyId}`);
}

// Clear caches (after key rotation or config changes)
engine.ClearCaches();
Copy

Key Rotation

Rotate keys without downtime using the RotateEncryptionKeyAction:

import { RotateEncryptionKeyAction } from '@memberjunction/encryption';

// 1. Deploy new key to environment
// export MJ_ENCRYPTION_KEY_PII_V2=new-base64-key-here

// 2. Run rotation
const action = new RotateEncryptionKeyAction();
const result = await action.Run({
    Params: [
        { Name: 'EncryptionKeyID', Value: 'existing-key-uuid' },
        { Name: 'NewKeyLookupValue', Value: 'MJ_ENCRYPTION_KEY_PII_V2' },
        { Name: 'BatchSize', Value: 100 }
    ],
    ContextUser: currentUser
});

// 3. After rotation completes, update environment to use new key
Copy

The rotation process:

flowchart TD
    A["Validate new key\nis accessible"] --> B["Set key status\nto 'Rotating'"]
    B --> C["Find all fields\nusing this key"]
    C --> D["For each field:\nLoad records in batches"]
    D --> E["Decrypt with\nold key"]
    E --> F["Re-encrypt with\nnew key"]
    F --> G["Save updated\nrecord"]
    G --> H{More records?}
    H -- Yes --> D
    H -- No --> I["Update key metadata\nLookupValue + Version"]
    I --> J["Set status\nback to 'Active'"]
    J --> K["Clear engine\ncaches"]

    style A fill:#2d6a9f,stroke:#1a4971,color:#fff
    style B fill:#b8762f,stroke:#8a5722,color:#fff
    style I fill:#b8762f,stroke:#8a5722,color:#fff
    style J fill:#2d8659,stroke:#1a5c3a,color:#fff
    style K fill:#2d8659,stroke:#1a5c3a,color:#fff
Copy

API Reference

EncryptionEngine

EncryptionKeySourceBase

Interfaces

Actions

Database Schema

The encryption infrastructure uses three metadata entities plus extensions to EntityField:

MJ: Encryption Key Sources -- Where keys are stored (env vars, config files, vaults)

MJ: Encryption Algorithms -- Available algorithms (AES-256-GCM, etc.) with Node.js crypto identifiers

MJ: Encryption Keys -- Configured keys linking a source and algorithm together

EntityField extensions:

• Encrypt -- Enable encryption for this field
• EncryptionKeyID -- Which key to use
• AllowDecryptInAPI -- Whether to return plaintext in API responses
• SendEncryptedValue -- Whether to return ciphertext when decryption is not allowed

Performance

• Key configurations are cached via BaseEngine with auto-refresh on entity changes
• Key material is cached with a 5-minute TTL
• Encryption and decryption use Node.js native crypto module (hardware-accelerated where available)
• Batch processing for key rotation and initial encryption (configurable batch size)
• Lazy loading -- the encryption engine is only activated when needed
• Cloud providers (AWS KMS, Azure Key Vault) use lazy SDK loading to avoid import cost when not used

Security Considerations

1. Key Management

   • Never store keys in the database -- use environment variables or secure vault services
   • Rotate keys regularly (recommended: annually)
   • Generate keys with openssl rand -base64 32

2. Authenticated Encryption

   • AES-256-GCM provides both confidentiality and integrity
   • Auth tag prevents tampering with ciphertext
   • Random IVs for each encryption operation prevent pattern analysis

3. API Security

   • Default: encrypted fields return null to API clients
   • Explicitly enable AllowDecryptInAPI only when needed
   • Use SendEncryptedValue for client-side decryption scenarios

4. Key Rotation

   • Plan for rotation before key compromise
   • Test rotation in a staging environment first
   • Monitor rotation progress for large datasets
   • Keep old keys accessible until rotation completes
   • Key status is set to Rotating during the operation for visibility

Troubleshooting

"Encryption key not found"

• Verify the key exists in the MJ: Encryption Keys table
• Check that IsActive = 1 and Status = 'Active'
• Ensure the referenced algorithm and source are also active

"Key length mismatch"

• Ensure your key is exactly 32 bytes (256 bits) for AES-256
• Generate with: openssl rand -base64 32
• The base64 string should be approximately 44 characters

"Failed to decrypt" / Auth tag mismatch

• The key may have been rotated -- check KeyVersion
• The data may be corrupted
• Auth tag mismatch indicates the data was tampered with or the wrong key was used

API returns null for encrypted fields

• Check the AllowDecryptInAPI flag on the EntityField
• The default is false for security
• Set to true if API clients need plaintext

Dependencies

This package depends on:

• @memberjunction/global -- Class registration and the ENCRYPTION_MARKER constant
• @memberjunction/core -- BaseEngine, RunView, Metadata, UserInfo
• @memberjunction/core-entities -- EncryptionEngineBase and encryption entity types
• @memberjunction/credentials -- Credential management
• @memberjunction/actions-base -- RunActionParams and ActionResultSimple for action definitions

Optional (for cloud key sources):

• @aws-sdk/client-kms -- AWS KMS integration
• @azure/keyvault-secrets + @azure/identity -- Azure Key Vault integration

License

ISC