SSHepherd® · Air-gapped ZTNA

Close the port.Keep the access.

The isolation of an air gap, the access of Zero Trust. SSHepherd removes the exposed listening ports on your servers, across SSH, RDP, databases and file transfer, while your administrators keep working exactly as before.

Animation: a port scan runs past a server without SSHepherd, where five ports answer, and a server with SSHepherd, where nothing answers. The port you are trying to reach is not in service.
The usual fixes

Every usual fixstill answers the door.

Every open port is an invitation. To administer a server you leave something listening, and that is the first thing an attacker’s scanner finds.

Move the port

Port 22 becomes port 2222. A scanner finds it seconds later, version banner and all.

Lock it down

Keys only, rate limits, fail2ban. Fewer guesses get through, but the service still answers every probe and every new CVE.

Put a gateway in front

A VPN or RDP gateway narrows the way in. Now the gateway is the thing on the internet, and the thing that needs patching tonight.

SSHepherd doesn’t guard the door.It removes it.

SSHepherd® by Full Armor · published figures
0
Externally exposed listening ports on a protected host
10
Minutes to deploy and protect a server
5M+
Users rely on Full Armor technology
1,500
Organisations rely on Full Armor technology
How it works

Invisible to attackers.Open to you.

Step 01
Ports go dark

The exposed SSH, RDP, database and application ports are no longer reachable inbound. Nothing to scan or discover.

Step 02
Access via broker

The host connects outbound to the broker. Nothing initiates a connection to it, so there is no inbound path to exploit.

Step 03
Verified & watched

Only authorised identities are admitted. Every session is monitored, recorded and can be killed on demand.

Developed by Full Armor Corporation. Distributed, deployed and supported across Southeast Asia by Auris.

Attacker scanNo inbound path
Permitted · outboundBlocked · inbound
Protected serversNo inbound listening ports
SSHepherd®Broker
Authorised usersAdmins & vendors
  • Nothing listens inbound
  • Access via broker only
  • Every session monitored
Portless architecture. Servers and users both connect outbound to the SSHepherd® broker, so the protected host never accepts an inbound connection.

“If a hacker can find a port, they can attack it.
SSHepherd makes sure there’s nothing to find.”

SSHepherd®

Control & visibility.

Zero-Trust containment
Access for authorised identities only, never by default.
Real-time monitoring
Session monitoring of SSH and RDP, with live view.
Immediate kill-switch
Terminate any session on demand.
Session recording
Clean, exportable audit trail and records.

Deploys anywhere, fast.

On-prem, cloud, physical, virtual
One consistent model.
No re-architecture
Sits over the infrastructure you already run.
Patented technology
Genuine port closure, not obfuscation.
Use cases

Every port you can close.

SSHepherd works at the port, not inside the protocol, so one model covers every service you expose to run your estate.

How SSHepherd® was born

Meet the people who built it.

Charles Davis, VP of Engineering at Full Armor, on the problem SSHepherd was built to remove and why closing the port is different from hiding it.

How to buy

Start with us.We’ll take it from there.

Engineers in Malaysia deploy it, support it, and pick up the phone.

Step 01
Book a demo

See SSHepherd on servers like yours, with an Auris engineer on the call to answer the hard questions.

Step 02
Get a quote and a partner

SSHepherd is sold through authorised partners. We arrange the pricing and the right partner for your organisation.

Step 03
Deployed and supported locally

Auris engineers scope, deploy and support it in-region. About ten minutes per server once the plan is agreed.

See it

Nothing to find.

Twenty seconds on what SSHepherd does to a port scan, and how your team still gets in.

SSHepherd® in action
Questions

What buyers ask first.

Isn't this just a VPN?

No. A VPN is itself an internet-facing service that has to be patched and can be attacked. With SSHepherd, protected servers have no inbound listening port at all. They connect outward to the broker, so there is nothing on the perimeter to find.

How SSHepherd compares with ZTNA products

How is this different from other Zero Trust (ZTNA) products?

Traditional ZTNA verifies identity but still exposes an access endpoint that can be found and attacked. SSHepherd adds the missing half: the protected server exposes no inbound listening port at all, so verified access happens with zero inbound exposure. Air-gap-grade isolation, enforced in software.

Compare with Zscaler ZPA, Cloudflare, Teleport and Twingate

Do my administrators have to change how they work?

No. They keep their SSH client, Remote Desktop client and existing tooling. What changes is that the server no longer listens for inbound connections.

Does it work in the cloud and on-premise?

Yes. On-premise, cloud, physical and virtual hosts all use the same model, and SSHepherd sits over your existing infrastructure without re-architecting the network.

How long does deployment take?

About ten minutes to deploy and protect a server. A full environment depends on how many hosts and which access paths, but the per-host work is small.

Who supports it in Malaysia?

Auris. Our engineers in Malaysia handle implementation, integration and ongoing support across Southeast Asia, alongside the partner who looks after your account.

How is it priced?

Per protected server, billed annually or quarterly. Tell us roughly what you run and we will come back with a quote.

Book a demo

See it onyour own servers.

Tell us roughly what you run: how many servers, and whether they are on-premise or in the cloud. We will set up a demo with an engineer and reply within one business day.

We use these details only to reply to your request, usually within one business day.