Skip to main content

Compliance Control Mapping

Use this map to plan controls and collect evidence for a particular deployment. It explains the technical capabilities behind compliance-related statements on formkiq.com; it is not a certification, attestation, legal determination, or complete framework crosswalk for FormKiQ or a customer system.

AWS infrastructure assurance applies to the services, regions, and scope in AWS's reports. It does not automatically certify an application deployed on AWS. Choose the applicable framework version and scope with your compliance team, and maintain your own control implementation and evidence register.

Deployment control map​

Control objectiveFormKiQ / AWS mechanismEvidence to collectCustomer responsibility
Unique identity and least privilegeCognito/SSO, IAM, site permissions, dedicated management permissions, configured backend policies.Issuer/client configuration, group/site grants, permission-denial tests, access reviews.Joiner/mover/leaver process, MFA/session policy, privileged-access approval and periodic review.
Data separationSeparate AWS accounts, regions, FormKiQ sites, and backend access policies.Architecture, resource inventory, cross-site denial tests, data-flow map.Decide which datasets need isolation. Do not rely on browser-hidden actions or folder metadata secrecy.
Encryption and key managementTLS, S3/DynamoDB encryption, selected customer-key/full-encryption capabilities.Effective encryption settings, key policies, rotation and recovery procedures, transport tests.Choose supported key ownership and algorithms, protect credentials, and review external recipients.
Audit and detectionFormKiQ activity records, CloudWatch, CloudTrail, event consumers, and alerts.Sample audit exports, log destinations/retention, access controls, alert tests and incident records.Define coverage and retention, protect logs, review them, and handle incidents. An audit screen is not immutable storage.
Retention, hold, and deletionNative retention/legal hold, configured disposition, trash, backup lifecycle, deletion reconciliation.Policy assignments, denied-deletion tests, disposal records, backup inventory.Determine legal periods/holds and remove copies from every in-scope destination. Web assignment rules have client-specific limits.
Availability and recoveryAWS service configuration, backups, DynamoDB recovery, S3 versions, monitoring, recovery procedures.Recovery objectives, backup reports, restore exercises, queue-failure recovery.Set RTO/RPO and prove recovery; a backup setting alone is insufficient.
Change and supplier managementVersioned templates, pinned releases, reviewed configuration, AWS and external provider contracts.Change approvals, release/test records, supplier scope and assurance reports.Assess services/models/integrations, manage change, and maintain support and data-processing agreements.

HIPAA​

For ePHI, map access, audit, integrity, authentication, and transmission controls to the applicable HIPAA Security Rule requirements, including §164.312. Identity and permission controls, audit evidence, TLS/encryption, backup/recovery, and operational procedures contribute to that implementation. Administrative and physical safeguards remain part of the full program. HHS Security Rule summary.

Before processing ePHI, confirm the relevant business-associate agreements, AWS service eligibility and configuration, external-service handling, emergency access, workforce procedures, incident response, and evidence requirements. Customer-account deployment does not itself establish HIPAA compliance.

SOC 2​

Map the applicable Trust Services Criteria to the organization's system boundary. Logical access, change management, monitoring, and recovery mechanisms can provide evidence, but the organization still needs operating procedures and evidence over the relevant period. A Type II report evaluates controls over time, rather than certifying an individual software feature. AWS SOC reports and scope.

Obtain applicable provider reports through the authorized channel, identify inherited versus customer controls, and test controls implemented in your deployment. Do not describe AWS's report as a SOC 2 report for the FormKiQ application or your company.

GDPR​

Map purpose limitation, data minimization, storage limitation, security, and data-subject processes to the actual processing. For example, controlled access and encryption support a security design; retention/disposition and an inventory of versions, artifacts, exports, search indexes, and backups support an erasure process. A native document DELETE alone is not an Article 17 procedure.

Document controller/processor roles, legal basis, processing agreements, retention exceptions, transfer safeguards, and access to data from outside the chosen region. Bedrock inference profiles, external signing providers, email, and integrations need their own data-flow review. Consult the GDPR text and data residency guidance.

FedRAMP​

Treat the customer system's boundary, applicable baseline, cloud service scope, and control inheritance as explicit design inputs. Access control, audit, configuration management, contingency planning, and incident-response evidence must be assessed in that system's context. Check the current agency/FedRAMP requirements and the selected AWS service offering's package; deploying on AWS or in GovCloud is not by itself a FormKiQ authorization. FedRAMP guidance for agencies using a cloud service.

Do not assume ordinary commercial-region templates, every module, or every model are approved for a federal deployment. Confirm the target environment, identity, cryptography, dependencies, continuous monitoring, and required authorization evidence before installation.

ISO/IEC 27001​

Use the access, logging, cryptography, change, supplier, and recovery mechanisms above as technical inputs to an information security management system. Scope, risk assessment, the Statement of Applicability, policies, review, corrective action, and audit remain organizational responsibilities. AWS ISO/IEC 27001 assurance applies within AWS's certified scope and does not extend a certificate to customer applications automatically.

Record a defensible implementation​

For each selected control, record its owner, configuration, evidence location, test result/date, exceptions, and next review. Include licensed module availability, token/session and edge controls, and known folder access limitations. Use the regulated production checklist for the deployment review.