> For the complete documentation index, see [llms.txt](https://docs.vega365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vega365.com/tandem/hardening-guide.md).

# Hardening Guide

What Tandem exposes, how each channel is protected, and how to harden it.

### What Tandem exposes

Tandem adds three listening ports to a deployment, all of them on the recording servers.&#x20;

| Channel        | Port  | Carries                                      | Reachable from                                                |
| -------------- | ----- | -------------------------------------------- | ------------------------------------------------------------- |
| Clustering API | 36763 | Pairing, configuration replication, status   | The paired recording server, and the Management Client host   |
| Backfill API   | 45322 | Backfill job control and status              | The paired recording server,  and the Management Client host. |
| SMB            | 445   | Shared configuration data and media transfer | The paired recording server                                   |

### Encryption in transit

#### Clustering API and Backfill API

Ports 36763 and 45322 use HTTP by default. Supply a certificate on each to run it over HTTPS. Do this on any deployment where the pair communicates across a network segment you do not fully control.

See [Clustering Service](https://docs.vega365.com/tandem/configuration/on-each-recorder/clustering-service.md#security) and [Backfill Service](https://docs.vega365.com/tandem/configuration/on-each-recorder/backfill-service.md#security-settings) to set up secure communication via TLS.

#### SMB

SMB traffic is not encrypted by default. See [Backfill Service](https://docs.vega365.com/tandem/configuration/on-each-recorder/backfill-service.md#shared-folder-access) to enable encrypted media transfer.

{% hint style="info" %}
**Expect a throughput cost.** Encryption carries a measurable performance cost compared with unencrypted transfer.&#x20;
{% endhint %}

### Network isolation

Restrict each port to the smallest set of sources that need it:

* **36763** — the paired recording server, and the Management Client hosts that administer the pair. Not the whole management VLAN.
* **45322** — the paired recording server, and the Management Client hosts that administer the pair.&#x20;
* **445** — the paired recording server only. This is the rule most worth scoping tightly, since a broad SMB rule on a recording server exposes far more than Tandem.

### Hardening checklist

* Supply certificates and run the Clustering API and Backfill API over HTTPS.
* Enable SMB encryption between the pair, unless the segment is dedicated and trusted.
* Scope the firewall rules for 36763, 45322, and 445 to named peers, not subnets.
* Apply identical rules to both members—roles swap at failover, so a rule that exists on only one of them stops working the moment it matters.
