Offline (on-premise) compliance audit — keeping full data control
Why offline mode matters
For banks and regulated organizations, data control is often a precondition, not an add-on — due to banking secrecy, supervisory expectations and GDPR. Offline/on-premise mode lets you run the audit without moving customer data outside.
When offline mode is needed
- data under banking secrecy or especially sensitive,
- a requirement of no outbound traffic (air-gapped environments),
- a strict cloud policy or a ban on processing outside the infrastructure,
- an audit at an ICT provider where full access control matters.
Benefits of an offline audit
- data and audit material stay in the customer’s infrastructure,
- no outbound traffic by default (flow control),
- a smaller vendor-risk surface,
- consistency with banking secrecy and supervisory expectations,
- a full audit trail and human approval.
What Bank Mode in Audnexa is
Bank Mode is a fully offline mode: audit data and materials can stay in the customer’s infrastructure, with no outbound traffic by default and a local model — customer data is not processed by Virtline or third-party AI providers and is not used to train models. Updates and support access are customer-controlled.
This approach was shaped in Virtline’s real audit practice (ISO/IEC 27001). Audnexa does not replace an auditor’s or lawyer’s opinion.
Frequently asked questions
In offline mode, does data leave the bank?
No. In Bank Mode, audit data and materials can stay within the customer’s infrastructure, with no outbound traffic by default.
Is customer data used to train models?
No — customer data is never used to train models, in any mode.
How does offline differ from cloud mode?
In offline mode data stays with the customer with no outbound traffic; in hybrid/cloud mode we precisely define data categories, subprocessors and processing regions.
Sources
This content is informational and does not constitute a legal opinion, an auditor’s opinion or a formal compliance decision.