MCP Server ↔ Database Server ↔ CAKM Provider/Library ↔ CipherTrust Manager
Note: This MCP server communicates only with database servers. The CAKM providers installed on database servers handle all communication with CipherTrust Manager.
Oracle TDE Enablement Logic
The server uses Oracle-documented logic to determine TDE status based on wallet configurations and TDE parameters:
✅ TDE is ENABLED when:
Any wallet shows OPEN status AND Master Encryption Keys (MEKs) exist
📊 Wallet Order Types (from Oracle V$ENCRYPTION_WALLET):
SINGLE: Only one wallet type configured
PRIMARY: Primary wallet in a dual-wallet configuration
SECONDARY: Secondary wallet in a dual-wallet configuration
🔧 TDE Configuration Parameter Values:
FILE: TDE configured to use FILE wallets only
HSM: TDE configured to use HSM wallets only
HSM|FILE: TDE configured with HSM as primary, FILE as secondary
FILE|HSM: TDE configured with FILE as primary, HSM as secondary
📊 Supported TDE Scenarios:
HSM-only TDE: HSM wallet OPEN (SINGLE), TDE_CONFIGURATION=HSM
HSM with Auto-login (Migrated): HSM wallet OPEN (PRIMARY), auto-login wallet OPEN (SECONDARY), TDE_CONFIGURATION=HSM|FILE
HSM with Auto-login (Not Migrated): HSM wallet OPEN (PRIMARY), auto-login wallet OPEN_NO_MASTER_KEY (SECONDARY), TDE_CONFIGURATION=HSM|FILE
FILE wallet TDE: PASSWORD wallet OPEN (SINGLE), TDE_CONFIGURATION=FILE
FILE with Auto-login (Reverse Migrated): PASSWORD wallet OPEN (PRIMARY), auto-login wallet OPEN (SECONDARY), TDE_CONFIGURATION=FILE|HSM
FILE with Auto-login: PASSWORD wallet OPEN (PRIMARY), auto-login wallet OPEN (SECONDARY), TDE_CONFIGURATION=FILE
🔍 Migration Detection Logic:
Forward Migration: HSM becomes PRIMARY (HSM|FILE configuration) → Database migrated from FILE to HSM
Reverse Migration: FILE becomes PRIMARY (FILE|HSM configuration) → Database migrated from HSM back to FILE
WALLET_ORDER and TDE_CONFIGURATION are correlated to determine the migration state
📋 Status Information:
TDE configuration parameters validate the expected wallet hierarchy
Wallet order and TDE_CONFIGURATION together determine the deployment scenario
🔧 Oracle TDE Operations Guide
The oracle_tde_deployment tool provides different operations for various TDE setup scenarios:
"Show me the TDE status of all my databases"
"For my 'prod_sql' connection, list all the asymmetric keys using the 'manage_sql_keys' tool"
"Rotate the master key on the 'Db05' database using the 'prod_sql' connection"
"Encrypt the 'SalesDB' database on my 'prod_sql' server"
"What is the wallet status for my 'oracle_cdb2' connection?"
Important Notes
Automatic Database Restarts: When specified in prompts, MCP tools can automatically restart Oracle databases as part of TDE operations
SSH Authentication: Oracle connections support both private key and password authentication
Private key: Use "private_key_path": "/path/to/key.pem" in ssh_config
Password: Use "password": "your_ssh_password" in ssh_config (instead of private_key_path)
Supported Databases: Microsoft SQL Server and Oracle Database are supported
Belum ada daftar tool. Server remote mendapatkannya setelah pemeriksaan kesehatan pertama.
FAQ
Pertanyaan
Bagaimana cara menginstal Thales Cdsp Cakm?
Salin konfigurasi stdio untuk Cursor, Claude Desktop, Claude Code, atau VS Code di halaman ini. Konfigurasi ini memakai instalasi dari penerbit, bukan proxy PlugMCP.
Apakah Thales Cdsp Cakm memerlukan kunci API?
Tidak ada variabel lingkungan wajib yang tercantum di catatan ini.
Transport apa yang digunakan Thales Cdsp Cakm?
Thales Cdsp Cakm berjalan secara lokal melalui stdio.
Kapan Thales Cdsp Cakm terakhir diperiksa?
Terakhir diperiksa 2026-10-28. MCP Server to manage encryption for Ms SQL and Oracle databases using Thales CAKM connector