Endpoint Updates

Update management keeps your endpoints secure and up to date by detecting available OS patches and outdated software, then letting you install them on demand or automatically through policies. Moftgate discovers real updates across macOS, Linux, and Windows using each platform’s native update mechanism - no manual scanning required.

Every endpoint detail page includes an Updates tab (in the Manage group) with four sub-tabs: Available, Automations, Logs, and History. The active sub-tab is reflected in the URL, so you can bookmark it or share it with your team.

Close image

• macOS - uses the built-in Apple software update tool to discover available system updates
• Linux - uses the native package manager (apt) on Debian and Ubuntu to find pending package updates
• Windows - uses the Windows Update Agent to detect available OS patches and cumulative updates

To see which updates are available on an endpoint, open the endpoint detail page and navigate to the Updates tab, then the Available sub-tab. This view lists all OS patches and outdated software discovered on the device.

1. 1
   Open the endpoint detail page

   From the endpoint list, click on the endpoint you want to inspect. The sidebar badge shows how many updates are pending before you even open it.

2. 2
   Go to the Updates tab

   In the Manage group on the endpoint detail page, click the Updates nav item. The URL updates to include ?tab=updates so the tab is bookmarkable.

3. 3
   Select the Available sub-tab

   The Available sub-tab shows a table of OS patches and outdated software. Use the search box to filter by name, and sort columns by clicking column headers.

4. 4
   Trigger a fresh check (optional)

   To make sure the list is current, use the "Check for updates" action. The panel sends a command to the agent, which queries the OS and reports back - no polling required.

You can install updates one at a time or in batches. Every installation creates a tracked task, so you can follow its progress in the Logs sub-tab and review the outcome in the History sub-tab.

Installing a single update

1. 1
   Select the update

   In the Available sub-tab, check the box next to the update you want to install.

2. 2
   Click "Download and install"

   The panel sends an install command to the agent over the command channel. The agent downloads and installs the update using the OS’s native tool.

3. 3
   Track progress in Logs

   Switch to the Logs sub-tab to see the active task. The status updates in real time as the agent works.

4. 4
   Review the result in History

   Once the task completes, it moves to the History sub-tab with its outcome (success or failure) and timestamp.

Installing multiple updates (batch)

1. 1
   Select multiple updates

   Check the boxes next to all the updates you want to install together. You can select any combination of OS patches and software updates.

2. 2
   Use the bulk "Download and install" action

   With multiple items selected, the bulk action button becomes active. Click it to send all selected updates to the agent in a single install task.

3. 3
   Monitor in Logs and History

   The batch task appears in Logs while running and in History once complete, with the overall outcome for the group.

Instead of installing updates manually on each endpoint, you can create update automation policies that enforce a consistent patching strategy across groups of endpoints. The Automations sub-tab shows which policies are applied to the current endpoint.

What an automation policy controls

Viewing policies on an endpoint

1. 1
   Open the endpoint detail page

   Navigate to the endpoint you want to inspect.

2. 2
   Go to Updates → Automations

   The Automations sub-tab lists all update automation policies that apply to this endpoint, shown as cards.

3. 3
   Review what is enforced

   Each card shows the policy name, what it enforces (OS patches, software updates, or both), and how it is scheduled.

Password telemetry helps you spot stale or expired user credentials on your endpoints. The agent collects password metadata - when each user last changed their password and when it will expire - and reports it during its regular heartbeat. No plaintext passwords are ever read, stored, or transmitted.

How it works per platform

Viewing password telemetry

1. 1
   Open the endpoint detail page

   Navigate to the endpoint whose users you want to inspect.

2. 2
   Go to the Users tab

   The Users tab lists all users discovered on the endpoint, including their password information.

3. 3
   Check the password columns

   The "Password Changed" column shows when each user last changed their password. The "Password Expires" column shows the expiry date. Dates appear as both relative (e.g., "30 days ago") and absolute.

4. 4
   Spot expired passwords

   Expired passwords are highlighted in red, so you can quickly identify users with stale credentials that may need attention.