Your Web Admin Consoles Are Privileged Access, Too

When companies think about privileged access, they picture SSH to Linux servers or Remote Desktop to Windows. Yet much of today's critical administration happens in a web browser.
The firewall management page. The Zabbix or monitoring dashboard. The NAS, storage and hypervisor consoles. The cloud portal and the SaaS back office. Whoever can log in to these pages can change rules, delete data or turn off alerts.
The everyday reality
In many Thai SMEs we visit, access to these consoles looks like this:
One admin account shared by the whole IT team, and sometimes by an outside vendor
Passwords saved in browsers, spreadsheets or chat groups
Consoles reachable from any PC on the office network
No record of who logged in, when, or what they changed
If a staff member leaves or a vendor contract ends, the password often stays the same. If a setting is changed by mistake, nobody can say who did it.
What good looks like: a single, audited front door
A Privileged Access Management (PAM) platform, also called a bastion host, puts one controlled entry point in front of these systems. Users sign in to the PAM platform, ideally with MFA, and then open only the assets they are authorised to use.
Three principles matter most:
Users never see the real password. Credentials stay in the vault and are filled in on the user's behalf.
Access follows least privilege. Each person sees only the systems their role needs.
Every session is recorded. Activity can be replayed and reviewed during an audit or an incident.
What changes in JumpServer v5
JumpServer is a widely used open-source PAM platform. It has long treated web consoles as "web assets", managed with the same permissions and recording as SSH, RDP and database sessions.
Until now, opening a web asset needed a relay machine to run the browser. That was either a Windows server with Remote Desktop licensing, or a Linux host running browser containers. For a team that only wanted to reach a dashboard, that meant one more server to build, license and patch.
According to JumpServer's October 2026 announcement, the v5 desktop client now includes a built-in browser. Web consoles open in a tab inside the same client used for SSH, RDP and databases, with no relay host required.
Before v5 | With the v5 built-in browser | |
Where the browser runs | On a Windows or Linux relay host | Inside the JumpServer client on the admin's PC |
Extra servers to maintain | At least one relay host | None for web access |
Login | Autofill configured per site | Autofill, plus a prompt for CAPTCHA or one-time codes |
Audit and recording | Yes | Yes, unchanged |
Security benefits that stay the same
The convenience is new, but the security model is not. The target address stays hidden behind the platform. Usernames and passwords are filled in automatically, so staff never learn them. Sessions are recorded and can be replayed, just like SSH and RDP.
The autofill feature handles simple login forms and more complex multi-step logins. When a site asks for a CAPTCHA or verification code, the client asks the user for it inside the same window.
Removing the relay host also removes one more server from your attack surface and your patching list.
When you still need a relay host
JumpServer notes two cases where the older publisher approach still fits:
Desktop-only tools, such as some database clients that run only on Windows.
Strict browser control, when a site must run on a managed browser, from a specific network location, or isolated from the admin's own PC.
Five questions to ask about your own consoles
Do you have a list of every web admin console in your company?
Does each person use their own account, or a shared one?
Who outside your company, such as vendors, can log in today?
Can these pages be reached from any PC on the network?
If a setting changed last night, could you prove who changed it?
If any answer is "no" or "not sure", your web consoles need the same protection as your servers.
How Greenwill can help
Greenwill Solution helps organisations design and deploy privileged access control, including JumpServer. We inventory your admin consoles and servers, set up role-based access with MFA and session recording, and hand over audit-ready reports. Talk to our team about bringing your critical consoles under control.
Based on Connecting to Web Assets in JumpServer V5, JumpServer blog. Product details may vary by version and edition.






Comments