- Add a new "Configuration for contributors" doc page. Move settings that are not recommended for production use - Remove settings modified in the `config` YAML document from the deploying/configuration doc page - Document all keys in `config` and `teams` YAML documents - Add comments to several `.go` files and remove unused struct
2.3 KiB
Fleet Desktop
Fleet Desktop is a menu bar icon available on macOS, Windows, and Linux.
At its core, Fleet Desktop gives your end users visibility into the security posture of their machine. This unlocks two key benefits:
- Self-remediation: end users can see which policies they are failing and resolution steps, reducing the need for IT and security teams to intervene
- Scope Transparency: end users can see what the Fleet agent can do on their machines, eliminating ambiguity between end users and their IT and security teams
Installing Fleet Desktop
For information on how to install Fleet Desktop, visit: Adding Hosts.
Upgrading Fleet Desktop
Once installed, Fleet Desktop will be automatically updated via Orbit. To learn more, visit: Self-managed agent updates.
Custom transparency link
For organizations with complex security postures, they can direct end users to a resource of their choice to serve custom content.
The custom transparency link is only available for users with Fleet Premium
To turn on the custom transparency link in the Fleet GUI, click on your profile in the top right and select "Settings." On the settings page, go to "Organization Settings" and select "Fleet Desktop." Use the "Custom transparency URL" text input to specify the custom URL.
For information on how to set the custom transparency link via a YAML configuration file, see the configuration files documentation.
Securing Fleet Desktop
To prevent brute-forcing, Fleet rate-limits the endpoints used by Fleet Desktop on a per-IP basis. If an IP requests more than 720 invalid UUIDs in a one-hour interval, Fleet will return HTTP error code 429.