Using TuxCare's ePortal as a Proxy for Radar Scans

I wrote this for TuxCare after remembering the airgapped datacenters where getting an update meant sneaker-netting a USB stick across the room. If your systems can’t all talk to the cloud directly, this post shows how to route Radar scan data through ePortal instead.

A few things I wanted people to walk away with:

• It’s a clean n-to-1 setup. Clients talk to a single internal ePortal server, and ePortal forwards scan data securely to the Radar backend, so your hosts don’t each need internet access.
• The config change is small. You enable the Radar proxy in ePortal’s config, point each client’s base-url at ePortal in radar.yaml, and everything else stays as it was.
• It fits compliance needs without new attack surface. There are no inbound ports or extra agents, and you can route to the EU endpoint for GDPR or inspect outbound traffic before it leaves.

For airgap, audit, or just peace of mind, this is a couple of config lines that extend Radar into tightly controlled environments.