Bardin Gate ARP
Capabilities and specifications
Each route, with its own policy
In ARP every route has its own complete policy: what may cross, from where, to where and under which rules. You define it once and it then runs without you; every change is versioned and audited. Each route is exactly as strict as the organisation intends: no looser by accident and no stricter than needed.
| Setting | What it decides |
|---|---|
| Source, destination and direction | The host and folder on each side. Direction follows from the hosts' sides, and the opposite direction is a separate route, because sending data out is not the same risk as bringing it in. |
| Validation profile | Which deterministic rules run on the admitted bytes. “No validation” is a deliberate choice, never a default. |
| Inspection profile | Which engines run, and whether each one is required or optional. |
| Data-leak profile | Which detectors look for leaking data. |
| Duplicates | What happens when content the route has carried before arrives again: deliver it again, replace the earlier copy, or keep both under distinct names. None of them discards content. |
| Retention | How long the appliance keeps its own copy after an item ends, for each outcome. |
| Source disposition | What is done with the original at the source, and when. Deletion is never the default. |
Human approval, only where a route asks for it
Approval belongs to the route. It does not replace the machine's ruling: a file reaches the approval gate only after policy has accepted it as clean.
- A gate is a set of requirements, each naming a group or people and a count. All are open at once.
- One person satisfies at most one requirement, so nobody in two groups can open a two-person gate alone.
- The first rejection ends the item. A gate has a deadline, and expiry rejects.
- Every decision asks for the password again, and two decisions at once cannot collide.
Who may do what
| Action | Who | Control |
|---|---|---|
| Change a route or its policy | Administrator | Permission to activate configuration, and the password again |
| See route health and backlog | Operator, administrator | Permission to view routes |
| Approve or reject an item | The assigned approver | Membership in that item's requirement, and the password again |
| Export evidence | Operator, auditor | Metadata and evidence only, never file content |
| Release quarantined content | Nobody | No such permission or way exists |
Route health at a glance
| State | Meaning |
|---|---|
| Ready | Enabled, and work is flowing. |
| Degraded | Working, but something is wrong: an optional engine is down or the backlog is growing. |
| Blocked | Enabled but unable to run. No new work is admitted until an operator acts. |
| Disabled | Turned off in the configuration. Not an error. |
The appliance
| Item | Value |
|---|---|
| Form | One 2U rack-mount appliance |
| Networks | Safe, Unsafe and management; the first two are never joined |
| Connection to your systems | rsync over SSH, SFTP, and SMB3 with Kerberos |
| Inspection | 17 validation rules; data-leak detection, ClamAV, YARA and the AI model |
| Console | In a browser, in fourteen languages |
| Configuration | One versioned file holding every route and policy, without secrets |
Talk to our specialists
Tell us about your environment and what you need. One of our specialists will answer you.