Endpoint management
From inventory to control of every machine
Inventory, remote access and execution at scale, on your own server.
The problem
Each machine is still handled at the desk, one by one, or through remote access that takes the session, the credentials and the inventory to a vendor’s cloud. When legal calls asking where that data sits, there is no answer.
In action
See it happen
- Inventory
- Agents
- Remote session
- Audit trail
What it does
What your team stops doing
-
Takes inventory
Machines, software and versions, kept current on their own: what exists in the fleet, without a spreadsheet.
-
Gives access
A remote console for support, with a record of who entered which machine.
-
Executes at scale
The same configuration reaches every workstation through the directory, without visiting machine by machine.
-
Stays with you
The server sits in your own environment. Sessions, credentials and inventory do not go through a third party’s cloud.
In practice
In production at Grupo NTK
Endpoint Management runs today at Grupo NTK, alongside the other six solutions. What seven years of modernization changed is in the case.
What you get
What ends up running in your environment
- Server in your own environment: the session does not go through a third party’s cloud
- Deployment of the inventory of machines, software and versions, kept current on its own
- Remote console for support, with a record of who entered which machine
- Execution at scale: the same configuration reaches every workstation through the directory, without visiting machine by machine
- Logs reaching detection, so remote access is auditable too
How it works
From installation to audit trail, step by step
-
The server goes into your environment
On the internal network, with restricted access and a second factor.
-
Agents reach the workstations
Each machine shows up in the inventory, with software and versions kept current on their own.
-
Support connects
Through the console, with a record of who entered which machine.
-
The trail goes to detection
The remote access log reaches the SIEM, so remote access is auditable too.
What you should know first
The server that controls the fleet is as sensitive as a domain controller: the agent runs with full privilege on every machine. So it sits on the internal network, with restricted access and a second factor. We explain this before installing.
Further reading (in Portuguese)
The whole fleet under control, on your own server, with a record of who entered each machine.