Bardin Gate ADSAir-Gap Database Synchronization

The problem it solves

Some data has to exist on both sides of a boundary: reference data an isolated network needs, or operational records an analysis network has to see. Opening a database connection across the boundary undoes the separation, and exporting and importing by hand is slow and error-prone. ADS carries the changes for you, under rules you write, and nothing else crosses.

Changes, not connections

Your databases are never connected to each other.

You set the scope

Which databases, tables and fields take part is written down; the rest stays where it is.

You set the direction

One way, or both ways, for each flow.

On record

Every change carried, refused or held is recorded.

What you get

• Direction control

  Each flow is one-way or two-way, as you decide, and a direction that is not written is refused.

• Scope control

  Synchronisation is limited to the databases, tables, records or fields you choose.

• Checks before crossing

  Data, direction and schema are checked against your rules before a change leaves its side.

• Traceability

  Every synchronisation, its status and every exception can be reviewed afterwards.

Where it fits

• Reporting and analysis

  Selected operational data reaches a separate reporting network.

• Government and regulated data

  Selected records are shared between separated domains.

• Industrial systems

  Selected changes move between the plant network and the enterprise network.