MCP servers (AI tooling)
TMA-MCP-6.2
Ensure tokens and keys are protected in clients and servers
Deskripsi
All credentials (API tokens, OAuth client secrets, service-account keys) are stored in system keychains, managed secret stores, or KMS-backed stores. As a CIS hardening position, secret values are not embedded in deployed configuration or artifacts in any form, including encrypted, and are referenced from the managed store at runtime instead. Automated credential rotation is in place, with alerts for credentials approaching expiry. Credentials embedded in deployed configuration or artifacts are a leading cause of compromise: they propagate through backups and images and are a primary target of automated scanning by attackers. A managed secret store keeps secret material out of configuration, supports rotation, and centralizes access control.
Cara pemeriksaan
Metode audit: Perintah shell
cfg="${MCP_CONFIG:-/etc/mcp/server.json}"; [ -f "$cfg" ] || { echo "missing $cfg (set MCP_CONFIG)"; exit 1; }; grep -Eq '"cis_6_2"|"protocolVersion"|"capabilities"|"auth"' "$cfg" && echo compliant || echo "non-compliant: section 6.2"- Output yang diharapkan
compliant
Cara perbaikan
Metode perbaikan: Panduan atau patch infrastruktur
Migrate all inline or embedded secrets to a managed secret store or system keychain, and update deployment configuration to reference them from the store at runtime rather than inline. This is a deployment and configuration change, and the exact store is environment-specific. Implement automated rotation with alerts for credentials approaching expiry. Rotate any secret that was previously embedded in deployed configuration or an artifact since it must be treated as compromised.
Properti
- Sistem operasi
- Apa saja
- Tag
- aiauthcryptomcpmcp-server
- Referensi
- CIS MCP Server Benchmark v1.0.0 - 6.2 Ensure tokens and keys are protected in clients and servers
Periksa host ini
Jalankan ini pada mesin yang diizinkan untuk Anda audit. Pemindaian bersifat hanya baca.
tmaegis scan --target mcp-server