Compliance – questions
Beta
Understand what the evidence shows and where separate services or examinations remain necessary.
Use these answers when planning an application's review. DynamicForm keeps testing evidence, signed statements and limitations together so reviewers can examine the stated scope.
Scope and verdicts
What does testing establish?
DynamicForm tests and documents a configured application against controls mapped to selected frameworks. Evidence combines tests, signed statements and approved exceptions. The report records its scope and limitations, helping reviewers understand what the evidence covers.
How are verdicts expressed?
The report gives an outcome for each selected framework.
- 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.
Who approves an exception?
An exception needs a reason, an expiry and a different approver.
Examination and testing
Does this replace examinations?
No. A regulator's, auditor's or assessor's own examination remains separate. The report does not replace an external VAPT, a QSA assessment or an auditor's opinion. It does not replace a SOX opinion, SOC 2 or ISO 27001.
Does a passing report mean there are no vulnerabilities?
No test report proves that no vulnerability exists. DynamicForm records tests and their evidence, acknowledged limitations and exceptions. Read those details alongside the report scope when deciding what further examination you need.
Does AI run inside my live application?
No. AI is used only while designing. Compliance tests are generated from the saved configuration without AI. A behaviour test checks that the running application makes no AI service calls.
Data and services
Does DynamicForm store card numbers?
Card fields hold only a token and the last 4 digits. DynamicForm does not store full card numbers, CVV or PIN. These boundaries matter when designing which information your application collects.
Are screening services included?
DynamicForm does not supply sanctions or politically exposed person list data. It does not supply transaction monitoring. The Beta KYC onboarding template includes a screening connection and a suspicious-transaction case with approval.
Are identity services included?
DynamicForm connects to licensed Aadhaar e-KYC, CKYC and V-CIP services; it does not provide those services. The Beta KYC template includes e-KYC and CKYC connections and a V-CIP session screen.
Evidence and boundaries
Are infrastructure controls included?
No. DynamicForm does not provide a web application firewall or protection against distributed denial-of-service attacks. It provides neither a security operations centre nor a disaster recovery site. The report includes environment checks alongside application tests and platform security evidence.
How are statements collected?
Named people receive assignments through their inbox and sign fixed-wording statements in the product. Evidence uploads undergo virus scanning. Statements have validity periods, and company-wide answers can be reused across applications.
When does evidence change?
A report belongs to an application version. Any application change marks it superseded. Daily re-checks and framework badges help track currency. Publishing can be blocked until the report is approved. Readers can verify the report using its QR code or verification code.
Beta features are available to trial and pilot customers and may change before general release.
Explore DynamicForm
Compliance · How it works · Rules and calculations · Security and identity · Company Admin · Applications
Updated 16 November 2026