HBX Access · Human Access
Your technicians reach the customer's device. Nobody reaches the customer's network.
Your people sign in with your directory and land on the device's own screen. Access opens on the customer's terms and ends with the ticket.
The problem
Every customer handed you a VPN and a shared password.
Standing access to networks that are not yours
A VPN account or a shared password stays valid long after the job is done, and it reaches far more than the one device the ticket was about.
No proof of who used it, or when
A shared login has no name behind it. When a customer asks who was on that device last Tuesday, nobody can say.
Revoking a technician means going customer by customer
When someone leaves, their access has to be found and removed one customer at a time, and nobody is sure the list is complete.
The console
One console for every customer, site and device your technicians are cleared for.
The technician signs in, picks a device from the catalog by customer and site, and lands on its own management screen.
What you get
Access that ends when the job ends.
One hierarchy per customer, site and device
Each technician sees only the devices they are cleared for. There is no lateral movement from one device, site or customer to another.
A session that dies with the ticket
Access opens on the customer's terms and ends with the ticket. Nothing permanent is left on the device.
The credential stays with the connector
The connector holds the password. The technician never sees it, so there is nothing to copy, share or leak.
Revoking a person is one click
Remove someone once and their access ends across every customer at the same time.
One record per session
The customer can read who connected, to which device, when, and who approved it.
Telemetry stays local
How the site is laid out and what the device reports stay on the customer's network. None of it passes through HBX.
Use cases
Where people reach systems they don't own.
Talk to us
Bring one customer network and who needs to reach it.
Thirty minutes is enough to see how it would work for you. If software has to reach the same equipment without a person in the chair, that is the same engine authorizing the software instead: see HBX Agent Access.