Can I map document controls to HIPAA, SOC 2, GDPR, FedRAMP, or ISO 27001?
Use FormKiQ's compliance control mapping to connect access, encryption, audit, retention, and recovery capabilities with your organization's control evidence. The mapping is planning guidance, not a product certification, legal conclusion, or authorization. AWS assurance and customer-managed deployment support the assessment, while application configuration, operating procedures, agreements, and independent review remain part of the customer's compliance program.
Build an evidence register
Start with the specific framework, scope, data classes, and deployment. For each relevant control, record the FormKiQ capability, AWS configuration, responsible owner, evidence artifact, and verification frequency. Include exceptions and any selected third-party processor.
Test actual grants, encryption/key settings, recorded activity, retention/hold behavior, backup restoration, and incident procedures. A feature being available does not establish that it is enabled, correctly operated, or sufficient for a particular control.
Preserve responsibility boundaries
AWS and customer responsibilities vary by service. Review the AWS shared responsibility model alongside the application's operational responsibilities. Hosting in an AWS environment does not automatically certify FormKiQ or the resulting customer workload.
Use the framework's authorized assessment process and the organization's qualified security/privacy advisers for requirements and conclusions. Confirm needed agreements, evidence access, and support obligations in the deployment scope. Refresh the register after a significant module, integration, model, or infrastructure change.
Edition and configuration
Applicable controls depend on installed modules and deployment configuration. Compliance commitments, evidence delivery, support, and maintenance obligations follow the agreed commercial and operational scope.