You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/loadtest-osquery-perf.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ on:
13
13
default: "main"
14
14
required: true
15
15
loadtest_containers:
16
-
description: "Deploys osquery-perf containers all at once. Total number of osquery-perf tasks to run (should be a multiple of 8, if setting loadtest_containers_starting_index). This is also used as the end index in enroll.sh"
16
+
description: "Deploys osquery-perf containers all at once. Total number of osquery-perf tasks to run. This is also used as the end index in enroll.sh"
17
17
type: string
18
18
required: true
19
19
loadtest_containers_starting_index:
@@ -22,7 +22,7 @@ on:
22
22
default: 0
23
23
required: true
24
24
task_size:
25
-
description: "CPU and Memory setting for osquery-perf containers. Example: {\"cpu\":\"4098\",\"memory\":\"8192\"}"
25
+
description: "CPU and Memory setting for osquery-perf containers. Example: {\"cpu\":\"4096\",\"memory\":\"8192\"}"
### Linux adoption is growing. Management hasn't kept up.
2
+
3
+
* macOS and Windows have mature management ecosystems. Linux does not.
4
+
* Compliance frameworks don't grant exemptions by operating system.
5
+
* Security audits don't skip Linux workstations.
6
+
* These create the Linux gap.
7
+
8
+
### Unmanaged devices are unmanaged risk.
9
+
10
+
This guide helps IT leaders understand and close the Linux management gap.
11
+
12
+
### What you'll learn
13
+
14
+
You'll learn about a maturity model for planning your adoption path, a clear framework for defining your requirements, and a concrete evaluation scorecard for comparing management platforms. Whether you manage 50 Linux workstations or 5,000, this guide gives you the structure to make a defensible platform decision and explain it to your team.
15
+
16
+
### Chapter list
17
+
18
+
-**Why Linux devices are important**
19
+
* What's driving enterprise Linux adoption and why management is no longer optional.
20
+
-**The business case for managing Linux devices**
21
+
* Cost, compliance, talent retention, and the price of inaction.
22
+
-**Defining your Linux device management needs**
23
+
* Key questions to ask and a maturity model to map your goals.
24
+
-**Automated provisioning for Linux desktop in the enterprise**
25
+
* The provisioning gap, enrollment approaches, and what zero-touch looks like on Linux.
26
+
-**Security baselines for Linux**
27
+
* Why baselines matter, what to enforce, and how to fight configuration drift.
28
+
-**App and certificate management for Linux**
29
+
* Software distribution challenges, the notarization gap, patching speed, and shrinking certificate lifetimes.
30
+
-**Protecting the Linux device**
31
+
* USB and Bluetooth threats, the sudo problem, and remote lock and wipe.
32
+
-**Controlling your software and your data**
33
+
* Software sovereignty, data sovereignty, and why your management tooling should reflect the values that made Linux worth adopting.
34
+
-**Choosing the right solution**
35
+
* Business and technical requirements, an evaluation criteria table, and a structured way to compare platforms.
36
+
37
+
38
+
39
+
<metaname="articleTitle"value="The IT leader's guide to Linux device management">
<metaname="description"value="Close the Linux management gap. A guide to help IT leaders understand the business case, security, compliance, and choosing the right solution.">
<metaname="formHeadline"value="Learn how to close the Linux management gap">
52
+
53
+
<metaname="introductionTextBlockOne"value="Linux now exceeds 5% of desktop market share. Stack Overflow's 2025 developer survey shows nearly 30% of developers use Linux as their primary work OS.">
54
+
<metaname="introductionTextBlockTwo"value="Your most important contributors, developers, engineers, and security practitioners, are choosing Linux. And in most organizations, those devices sit outside formal IT management.">
Join Brock Walters from Fleet and their customers for a candid conversation around enabling device management in the enterprise at the speed that business demands. Explore how to help your IT teams get out of the way by giving employees their time back, reducing spend, and proving compliance in real time.
2
+
3
+
## Why Modern Device Management Matters
4
+
5
+
This session will cover how to deliver configurations and updates that accelerate work, maintain real-time visibility that keeps IT audit-ready without last-minute scrambles, use live health data to catch issues before they become tickets, and respect end user focus with transparent device management.
6
+
7
+
### The GitOps Advantage
8
+
9
+
The sessions will also cover how a GitOps approach to using device management solutions eliminates manual "click-ops" and prevents configuration drift. Store changes live in a version-controlled workflow - peer-reviewed, transparent, and easy to roll back. Understand how your engineering talent can spend less time on repetitive tasks and more time on work that matters, at scale.
10
+
11
+
12
+
13
+
<metaname="articleTitle"value="Device management that actually works for IT">
<metaname="description"value="Explore how to help your IT teams get out of the way by giving employees their time back, reducing spend, and proving compliance in real time.">
Copy file name to clipboardExpand all lines: articles/how-to-define-your-Linux-device-management-needs.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ To do this, you will need sophisticated and flexible tools. But first, you need
10
10
11
11
In this article, we will discuss key questions to ask as you define your organizational goals for Linux device management. We will also discuss how these goals can be mapped to a maturity model of Linux MDM adoption. Formally defining your Linux needs and understanding your target location on this maturity model will help you adopt robust technical solutions for Linux MDM.
12
12
13
-
## Questions to Consider
13
+
## Questions to consider
14
14
15
15
Every business is different, and every team has its own needs based on team dynamics, regulatory requirements, and other factors. However, you can set yourself up for success by asking a few common questions to understand your Linux device goals:
16
16
@@ -92,13 +92,13 @@ IT teams are not monolithic. A helpdesk technician needs different access than a
92
92
93
93
Define your access control requirements before evaluating platforms. A tool that offers only administrator versus read-only access will create friction as your team grows or your compliance requirements become more specific. This is easy to overlook during a demo and painful to work around in production.
94
94
95
-
## The Linux MDM Maturity Model
95
+
## The Linux MDM maturity model
96
96
97
97
Not every organization needs the same level of Linux device management. This model defines four levels, from basic monitoring to full zero-touch provisioning. Your requirements determine which level is right for you, and not every team needs to reach level 4\.
98
98
99
99
When planning, consider both short and long-term goals. A short-term goal might be to understand which software your Linux users are running. A long-term goal might be automatically provisioning the tools every engineer needs to do their job. Either way, start by knowing where you want to land before deciding how far to climb.
100
100
101
-
### Level 1 \- Monitoring and Auditing
101
+
### Level 1 \- Monitoring and auditing
102
102
103
103
Providing device monitoring, reporting, and insight is the first level in the Linux device management maturity model. All teams need some level of device monitoring to ensure compliance with internal and external policies. You must understand your environment before you can manage it. Robust monitoring provides individual and aggregate metrics to drive intelligent decisions.
104
104
@@ -110,21 +110,21 @@ Monitoring lets you answer questions like:
110
110
111
111
For some organizations, especially small teams with limited Linux footprints, this may be the final level on their journey. If you only have a handful of Linux workstations, then you may not need further device management features. However, everyone can benefit from understanding the state of their environment.
112
112
113
-
### Level 2 \- Security and System Baselines
113
+
### Level 2 \- Security and system baselines
114
114
115
115
Equipped with a solid understanding of your Linux devices, you can begin providing baseline configurations that meet organizational and security policies.
116
116
117
117
Start with something simple, like implementing a specific security policy. For example, you may want to prevent users from adding any local accounts to their workstations. As you gain experience and user trust, you can move on to more advanced configurations that help your users. For example, you can deploy corporate certificates automatically on all of your Linux workstations.
118
118
119
119
Basic system management might be the final stop on your maturity journey. Many organizations are quite happy to provide baseline system management and leave the rest to their highly-skilled end users.
120
120
121
-
### Level 3 \- Self-Service Configuration and Software
121
+
### Level 3 \- Self-service configuration and software
122
122
123
123
Linux users are technically skilled, and most are comfortable installing and managing their own software. But even advanced users who’ve been using Linux on their desktop for years still sigh when they have to install a complex package with custom configuration. This is toil, and Linux users often face the brunt of it due to a lack of robust MDM tooling.
124
124
125
125
This level in the maturity journey is all about providing your Linux users with access to the tools and software to do their job. Consider the complexity of even a simple package installation in a modern organization. A user may have to add an internal company repository, determine the correct version that matches production, install the software itself, and then configure it to match the organization’s preferred configs. Providing a self-service portal, such as [Fleet Desktop](https://fleetdm.com/guides/fleet-desktop), saves hours.
126
126
127
-
### Level 4 \- Zero-Touch Provisioning and Drift Management
127
+
### Level 4 \- Zero-touch provisioning and drift management
128
128
129
129
Level 4 is full zero-touch provisioning and automated, continuous management of devices. A new Linux device can be powered on and immediately put into service by an end-user without any IT involvement (discussed in the next article). Organizations can onboard new Linux employees just as they do Windows and Mac users.
0 commit comments