Security Policy
k-msg provides a shared fieldCrypto policy layer for security-audit readiness.
This section covers encryption-at-write, hash-based lookup, key rotation, failure modes, and retention rules from an operator-focused perspective.
Question this page answers: In what order should non-security users read the fieldCrypto docs?
Documents
Section titled “Documents”- Security Glossary: plain-language terms
- Field Crypto v1: crypto model, AAD, failure handling, and metrics
- Key Management and Rotation: KeyResolver model and zero-downtime rotation
- Migration Orchestrator: operational flow for plan/apply/status/retry
- Auto Mitigation: scope-level isolation for key-error bursts
- Security Recipes: safe copy-paste configuration patterns
- KR B2B Retention: baseline legal retention and tenant-contract priority
Core principles
Section titled “Core principles”- Default is
secure; plaintext storage is denied by default. failModedefaults toclosed.- Lookups use
HMAC-SHA256hashes, not deterministic encryption. - Tenant early-deletion terms override legal baseline defaults.
Source of truth: