Is document storage encrypted at rest and in transit?
FormKiQ uses AWS storage and transport encryption in customer-managed deployments, with exact coverage determined by the configured services and endpoints. Core already uses AWS encryption; commercial Full Encryption extends configured coverage and key controls. Verify documents, metadata, indexes, derived files, backups, and external transfers individually rather than treating an edition label as proof of complete encryption.
Inspect storage and transfer settings
Check the actual S3 bucket encryption, DynamoDB configuration, search backend, logs, backups, and any derived output. Confirm HTTPS API and Web delivery, signed transfer URLs, certificates, and allowed clients. A secure API URL does not make an unrelated export or integration encrypted.
Review the installed Full Encryption configuration and whether customer-managed KMS keys apply to each selected service. Key policy, rotation, grants, workload permissions, and recovery ownership must be planned together.
Test key and endpoint behavior
Verify normal uploads/downloads using the workload identity, then inspect which keys protect the resulting resources. Test denied access with an unauthorized role and document how key changes affect background processors, restore jobs, and stored versions.
Protect secrets and temporary transfer URLs separately. Encryption at rest does not decide who is authorized to read a document through the application, and it does not revoke a URL already issued to a permitted caller.
Edition and configuration
Core uses AWS encryption. Full Encryption is included from Essentials and requires configuration; service-level KMS coverage and customer-managed key responsibilities depend on the deployed resources.