We’re pleased to announce Fleet 4.10.0. Check out the full changelog or continue reading to summarize what’s new.
For update instructions, see our upgrade guide in the Fleet docs.
As a progression from our host-specific software inventory, Fleet 4.10.0 introduces a new Software page in Fleet UI. Users can see an aggregated list of software installed throughout their entire organization or filter by individual teams as needed.
Vulnerability analysts, who manage many devices, can check for software affected by vulnerabilities (CVEs) and get the number of devices impacted — handy for tracking the status of patching efforts across their fleet.
💡 Since we’ve added the new “Software” nav item, we tidied away the Settings page under the Account dropdown to keep the navigation clear and simple.
When vulnerability automation is enabled, users can tell Fleet to reach out when a new vulnerability (CVE) is detected and automate the process of notifying device owners or creating a ticket to track the vulnerability.
To keep signal noise to a minimum, Fleet only sends notifications for new vulnerabilities published within the last two days.
IT administrators can monitor the status of MDM enrollment across all devices and see the number of devices with specific Munki versions installed to track upgrade efforts.
MDM enrollment data is only available on macOS and will expand to Windows and Linux devices later.
SHOW ENGINE INNODB STATUS
.fleetctl
’s new simplified implementation everywhere.GET/software
is now returning the expected amount of results.Visit our upgrade guide in the Fleet docs for instructions on updating to Fleet 4.10.0
Find out how Fleet can benefit your organization by exploring our docs and community.
Want to get up and running quicker? Then try out Fleet locally on your device - you’ll be up and running in minutes.