Solutions · BFSI

The bundle a vendor receives is data leaving the bank's control.

Banks and market infrastructure run large firewall and identity estates, and every vendor case sends a bundle that carries the branch and core-banking network structure, the addressing behind payment and core systems, and the identities of staff in logs. LogVeil is being built so that what reaches the vendor is rewritten under the bank's own policy, with a signed attestation and an audit log the IT-risk function can file.

Inside your perimeter, the estate — the branches, the core and the payment systems — produces a diagnostic bundle that carries the branch and core network structure, the addressing behind payments, staff identities in logs, certificates and secrets; LogVeil, in your own virtual machines under your policy and your key, rewrites every sensitive value and signs the attestation you file with the audit log; only the sanitised bundle and the attestation cross the perimeter to the vendor’s technical assistance centre. The release decision stays with you. INSIDE YOUR PERIMETER OUTSIDE Your estate branches, the core,payment systems The diagnostic bundle branch and core structureaddressing behind paymentsstaff identities in logscertificates and secrets LogVeil, in your own VMs your policy, your keyevery sensitive valuerewritten; the attestationand the audit log, filed The vendor's TAC the sanitised bundle andthe attestation arrive;custodial data never does THE RELEASE DECISION STAYS WITH YOU · NOTHING LEAVES WITHOUT A RECORD Inside your perimeter, the estate — the branches, the core and the payment systems — produces a diagnostic bundle that carries the branch and core network structure, the addressing behind payments, staff identities in logs, certificates and secrets; LogVeil, in your own virtual machines under your policy and your key, rewrites every sensitive value and signs the attestation you file with the audit log; only the sanitised bundle and the attestation cross the perimeter to the vendor’s technical assistance centre. The release decision stays with you. INSIDE YOUR PERIMETER Your estate branches, the core,payment systems The diagnostic bundle branch and core structureaddressing behind paymentsstaff identities in logscertificates and secrets LogVeil, in your own VMs your policy, your keyevery sensitive valuerewritten; the attestationand the audit log, filed OUTSIDE The vendor's TAC the sanitised bundle andthe attestation arrive;custodial data never does THE RELEASE DECISION STAYS WITH YOU

Drawn by code from the description of the estate; not a screen.

The bundle

What a bundle from this estate carries

  • branch and core-banking network structure
  • the addressing behind payment and core systems
  • staff identities in logs — usernames, e-mail addresses, phone numbers, names in filenames
  • certificates and secrets from the security estate

Before it leaves

The release decision falls on the bank's own policy

data leaving the bank's control

custodial data at third-party vendors

personal data of staff

What has to be true before anything leaves — in the words of the people who decide.

The maintenance an OEM provides for its own equipment usually sits outside the outsourcing arrangements a bank controls by contract, so those controls do not reach the bundle its technical assistance centre receives. The release decision falls on the bank's own information-security policy. LogVeil's policy, attestation and audit log are how the bank shows that its leakage-prevention strategy covered that channel: the people class — usernames, e-mail addresses, phone numbers, engineers' names in filenames — is rewritten like any other value, and a software bill of materials ships with every image of the kit.

The fit

How LogVeil is designed to fit

Your policy, your dictionary, your key

in development

The customer writes the rules and holds the key; Zindagi never sees either.

The policy and the key →

Verified — and honest about what isn’t

in development

A separate verification stage re-scans the output with independent scanners, fails closed, and signs an attestation that also says what is not claimed.

The attestation, field by field →

Reversible under control

in development

When the TAC replies about a masked address, your engineer can translate it back — and nobody else can.

How it works, in depth →

Built for the air gap

in development

An offline kit for your own VMs; nothing phones home; AI is optional, off by default, and never touches the result.

The offline kit →

The path

From a proof-of-concept on your own bundles to your own operation

  1. First

    Early access

    Early access is a free, guided proof-of-concept on your own bundles inside your own network: you choose the bundles, you write the policy with our help, and you keep the key; we hand over the offline kit, run the first jobs with your engineers, and leave you with the attestations.

  2. Then

    The offline kit, for your own operation

    in development

    An offline kit for your own VMs; nothing phones home; AI is optional, off by default, and never touches the result.

  3. On the roadmap

    An appliance

    planned

    A server with a local GPU for local AI and TPM-sealed keys. No bill of quantities, no price — it is a roadmap item.

Status, and the next step

LogVeil is in development. An early-access programme opens after our first field trial.

Request early access