mirror of
https://github.com/fleetdm/fleet
synced 2026-05-24 09:28:54 +00:00
b1ea2121da
Closes https://github.com/fleetdm/fleet/issues/41798 Changes: - Added an "About Fleet" section to the case study article template page. - Removed the "About Fleet" sections from case study articles. FYI @irenareedy: After this change is merged, you will not need to include an "About Fleet" section on new case study articles.
72 lines
3.3 KiB
Markdown
72 lines
3.3 KiB
Markdown
# Identity platform improves Linux visibility with Fleet
|
||
|
||
An enterprise identity platform provides single sign-on, multi-factor authentication, and directory services for organizations around the world. Security and trust are central to its business, which makes device visibility critical.
|
||
|
||
The company’s engineering teams rely heavily on Linux systems. However, many of those devices remain unmanaged, creating gaps for IT and security teams.
|
||
|
||
## At a glance
|
||
|
||
* **Industry:** Identity and access management
|
||
|
||
* **Devices managed:** ~80 Linux hosts (growing)
|
||
|
||
* **Primary requirements:** Linux management, osquery visibility, API integrations
|
||
|
||
* **Previous challenge:** Unmanaged Linux devices created visibility gaps
|
||
|
||
## The challenge
|
||
|
||
Before Fleet, Linux systems operated largely outside of centralized device management.
|
||
|
||
Because the company supports a flexible BYOD model for Linux, many machines are not enrolled in any management platform. This creates blind spots for both IT and security teams.
|
||
|
||
Without a consistent way to monitor system state, it becomes difficult to enforce security standards or understand the health of the fleet.
|
||
|
||
The team needs a way to bring these devices into a single system without disrupting developer workflows.
|
||
|
||
## The evaluation criteria
|
||
|
||
The team identified three capabilities that were required:
|
||
|
||
1. **Linux device management**
|
||
Bring unmanaged Linux hosts into a centralized device management system.
|
||
|
||
2. **osquery visibility**
|
||
Collect detailed telemetry to understand device state and security posture.
|
||
|
||
3. **API integrations**
|
||
Sync device data with internal IT asset management (ITAM) systems.
|
||
|
||
## The solution
|
||
|
||
Fleet provided a lightweight way to enroll Linux devices and collect real-time telemetry.
|
||
|
||
Using Fleet’s API, the team automated synchronization between Fleet and their IT asset management platform. Device data now updates automatically, which simplifies reporting and compliance tracking.
|
||
|
||
Fleet’s open development model also played a role in the decision. For a company focused on identity and security, transparency into how device data is collected and processed increased confidence in the platform.
|
||
|
||
## The results
|
||
|
||
Fleet gave the team immediate visibility into systems that were previously unmanaged.
|
||
|
||
* **Improved Linux visibility:** Previously unmanaged systems are now monitored in real time.
|
||
|
||
* **Automated asset tracking:** Fleet API integrations keep IT asset management data synchronized daily.
|
||
|
||
* **Faster incident response:** Live telemetry helps teams detect and resolve issues sooner.
|
||
|
||
## Why Fleet
|
||
|
||
For this organization, the biggest benefit was simple: reliable Linux management.
|
||
|
||
By centralizing device data and enabling automation, Fleet helps the team maintain security standards while supporting the flexible infrastructure their engineers rely on.
|
||
|
||
|
||
<meta name="articleTitle" value="Identity platform improves Linux visibility with Fleet">
|
||
<meta name="authorFullName" value="Irena Reedy">
|
||
<meta name="authorGitHubUsername" value="irenareedy">
|
||
<meta name="category" value="case study">
|
||
<meta name="publishedOn" value="2026-03-14">
|
||
<meta name="description" value="An identity platform improves Linux visibility with Fleet, bringing unmanaged systems into centralized device management.">
|
||
<meta name="useBasicArticleTemplate" value="true">
|
||
<meta name="cardTitleForCustomersPage" value="Identity platform">
|