Security and governance are structural in FormKiQ. Whether you deploy customer-managed, vendor-managed, or hybrid, the same governance primitives are available for high-control workloads.
What FormKiQ supports
- Customer-controlled AWS deployment and IAM ownership options.
- Segregated access boundaries using RBAC/ABAC patterns.
- Auditable metadata and workflow trails for assurance activities.
- Retention, legal hold, and defensible disposition controls.
- Encryption at rest and in transit with customer-managed key options.
| Capability | Customer-Managed | Vendor-Managed | Hybrid |
|---|---|---|---|
| KMS ownership | Customer | Shared/negotiated | Customer (production) |
| IAM ownership | Customer | FormKiQ | Split |
| Production FormKiQ access | None unless granted | Operational | None |
Important guardrail
FormKiQ provides architecture and controls. It does not claim blanket compliance with any specific law or certification by default. Legal/compliance outcomes depend on implementation and validation by your teams.