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 |
Follow the data and the responsibilities
A customer-managed deployment puts the primary document and metadata resources in your AWS account. Storage location, processing geography, and operational access are separate configuration decisions.
1. Store and organise
Documents, metadata, indexes, and configured logs live in the selected deployment. Define regions, replication, backups, access policies, and key controls for each resource.
2. Process with defined boundaries
Bedrock requests use the deployment's AWS permissions. The selected model and inference profile determine processing geography. A connected signature, credit, or other external service has its own processing boundary.
3. Retain the result and evidence
Keep generated documents, accepted metadata, review decisions, and returned signature evidence with the business file. Assign access, retention, and operational responsibilities.
| Deployment | Account and operations | FormKiQ access |
|---|---|---|
| Customer-managed | Your AWS account and operational policies. | Access only when you grant it for the agreed support purpose. |
| Vendor-managed Enterprise | A dedicated, segregated AWS account operated by FormKiQ. | Defined operational access, policies, and audit records. |
| Hybrid | Customer-managed production, with agreed support in non-production. | Access scoped to the agreed environment and responsibilities. |
For Bedrock, regional and geographic inference options must match your approved boundary; global profiles may route across supported regions worldwide. Review AWS inference routing and FormKiQ security and governance with your deployment requirements.
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.