DynamicForm Start free trial

Compliance – how it works

Beta

Follow your application's evidence from its profile to an approved report.

Set the scope before collecting evidence. DynamicForm combines repeatable tests with signed statements, then calculates a framework verdict from the results and approved exceptions.

Illustrative screen: Beta compliance workspace shows application classifications, profile details and statement assignments.
Define the application’s scope and assign statements to the people responsible for answering them.

Define the profile

Choose frameworks for the application. Classify every field, including Personal, Financial and Card data. AI suggests classifications during design, and a person confirms them.

Record purposes and lawful basis, identify the data subjects, and describe where data goes outside the application. Add recovery targets so the profile captures the requirements the evidence must address.

The mapped control catalogues are Beta. A regulator's, auditor's or assessor's own examination remains separate.

Generate repeatable tests

Tests come from the application's configuration, the same way every time, without AI. They cover configuration checks, behaviour tests, environment checks and the platform's own security evidence.

Behaviour tests use a temporary application copy and made-up data. They check the configured behaviour through the following areas.

  • Access refusal, masking and injection attempts test how the application handles restricted or unsafe actions.
  • Virus test files and security scanning check application protections.
  • Sign-in rules and maker-checker tests check access and separation of duties.
  • Consent, data-subject export and erasure, and retention tests check personal data handling.
  • Audit-trail tamper checks examine the recorded history's protections.
  • A test checks that the running application makes no AI service calls.

AI is used only while designing, never while the application runs. The test engine is checked against deliberately faulty sample applications that must fail. These checks support confidence in the testing process without proving that no vulnerability exists.

Collect signed statements

Some requirements need evidence from people. Named people receive statement assignments through their inbox and answer within the product. Statements and acknowledgements use fixed wording.

Signers upload evidence, which undergoes virus scanning, and provide answers with validity periods. Company-wide answers can be reused across applications. This keeps shared evidence available while the application retains its own scope.

The report reproduces every statement word for word, with the signer and signing time. Review the wording and supporting material together when assessing what a statement establishes.

Calculate and approve

Review the evidence and exceptions before approval. Every exception needs a reason, an expiry and a different approver.

  • Compliant with the DynamicForm control catalogue for the selected framework.
  • Compliant with the DynamicForm control catalogue for the selected framework, with exceptions. Approved, unexpired exceptions appear on the report's first page.
  • Not compliant with the DynamicForm control catalogue for the selected framework.

The verdict is calculated from tests, signed statements and approved exceptions, never typed.

The PDF brings together scope, every test with evidence, signed statements, acknowledged limitations and exceptions. Two-person sign-off records approval. A QR code and verification code let readers check that the report is genuine and current.

Keep evidence current

The report belongs to an application version. Any application change marks that report superseded, making the version boundary visible to reviewers.

Daily re-checks and a badge for each framework help people follow the current evidence. Publishing can be blocked until the report is approved. Reviewers can check report currency through its verification details.

Illustrative screen: Beta report controls show framework badge labels, approval and a superseded report marker.
Check framework badges, report approval and whether the application version has changed.

Read Compliance questions for the limits of the tests and report. Return to Compliance for the framework overview.

Beta features are available to trial and pilot customers and may change before general release.

Updated 16 November 2026