Skip to content

Commit c592c2b

Browse files
rachaelshawmarko-lisicanoahtalermangetvictorgeorgekarrv
authored
Docs v4.66.0 (#27844)
Documentation changes for the 4.66.0 release. --------- Co-authored-by: Marko Lisica <[email protected]> Co-authored-by: Marko Lisica <[email protected]> Co-authored-by: Noah Talerman <[email protected]> Co-authored-by: Victor Lyuboslavsky <[email protected]> Co-authored-by: George Karr <[email protected]> Co-authored-by: RachelElysia <[email protected]> Co-authored-by: Ian Littman <[email protected]> Co-authored-by: Eugene <[email protected]> Co-authored-by: Victor Lyuboslavsky <[email protected]> Co-authored-by: Scott Gress <[email protected]> Co-authored-by: Dante Catalfamo <[email protected]>
1 parent 9b73f62 commit c592c2b

10 files changed

+346
-39
lines changed

articles/filtering-software-by-vulnerability.md

+20-6
Original file line numberDiff line numberDiff line change
@@ -13,21 +13,35 @@ This filtering capability is particularly useful in environments where patch man
1313
* Fleet version 4.56 or later
1414
* Premium users have access to advanced filters by severity level and known exploited vulnerabilities
1515

16-
### Filtering Software by Vulnerability
16+
### Filtering software by vulnerability
1717

1818
1. **Navigate to the Software page**: In your Fleet dashboard, go to the **Software** tab. This will display a list of all the software detected in your environment.
1919

20-
2. **Add filters**: Click on the **Add Filters** button. This will open options for filtering the software list based on specific criteria.
20+
2. **Filtering by vulnerability name**: You can use the search bar to filter software by its name or by a CVE vulnerability name associated with it.
2121

22-
3. **Choose severity level**: From the dropdown menu, select the **Severity level** of vulnerabilities you're interested in. This allows you to focus on software with the highest severity of vulnerabilities, such as "Critical" or "High."
22+
3. **Add filters**: Click on the **Add Filters** button. This will open options for filtering the software list based on specific criteria.
2323

24-
4. **Toggle "Has known exploit"**: You can refine your filter by toggling the **Has known exploit** option. This will filter the software list to show only those with vulnerabilities that have known exploits, enabling you to prioritize these for patching.
24+
4. **Choose severity level**: From the dropdown menu, select the **Severity level** of vulnerabilities you're interested in. This allows you to focus on software with the highest severity of vulnerabilities, such as "Critical" or "High."
2525

26-
5. **Review filtered results**: Once you've applied your filters, the software list will update to show only the software that meets your criteria. This filtered view will help you prioritize which software needs immediate attention in your patching strategy.
26+
5. **Toggle "Has known exploit"**: You can refine your filter by toggling the **Has known exploit** option. This will filter the software list to show only those with vulnerabilities that have known exploits, enabling you to prioritize these for patching.
27+
28+
6. **Review filtered results**: Once you've applied your filters, the software list will update to show only the software that meets your criteria. This filtered view will help you prioritize which software needs immediate attention in your patching strategy.
29+
30+
### Filtering software by vulnerability on the Host details page
31+
32+
In Fleet version 4.66 or later, the same vulnerability filtering functionality is available on the Host details page. To access this:
33+
34+
1. **Navigate to the Hosts page**: In your Fleet dashboard, go to the **Hosts** tab.
35+
36+
2. **Select a host**: Click on a particular host to view its details.
37+
38+
3. **Access the Software tab**: On the Host details page, click on the **Software** tab. This will display a list of all software detected on the host.
39+
40+
4. **Filter software**: Follow steps 3 through 6 from the previous section to filter software by severity, known exploit, etc.
2741

2842
### Using the REST API to filter software for vulnerabilities
2943

30-
Fleet provides a REST API to filter software for vulnerabilities, allowing you to integrate this functionality into your automated workflows. Learn more about Fleet's [REST API](https://fleetdm.com/docs/rest-api/rest-api#vulnerabilities).
44+
Fleet provides a REST API to filter software for vulnerabilities, allowing you to integrate this functionality into your automated workflows. You can use the [REST API documentation for vulnerabilities](https://fleetdm.com/docs/rest-api/rest-api#vulnerabilities) to get started, and the [get host's software](https://fleetdm.com/docs/rest-api/rest-api#get-hosts-software) endpoint to retrieve software information for specific hosts.
3145

3246
## Conclusion
3347

articles/queries.md

+5
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,11 @@ How to create a query:
3232
3333
4. Select **Save**, enter a name and description for your query, select the frequency that the query should run at, and select **Save query**.
3434

35+
## Targeting hosts using labels
36+
37+
_Available in Fleet Premium._
38+
39+
When creating or editing a query, you can restrict the set of hosts that it will run on by using [labels](https://fleetdm.com/guides/managing-labels-in-fleet). By default, a new query will target all hosts, indicated by the **All Hosts** option being selected beneath the **Targets** setting. If you select **Custom** instead, you will be able to select one or more labels for the query to target. Note that the query will run on any host that matches __any__ of the selected labels. To learn more about labels, see [Managing labels in Fleet](https://fleetdm.com/guides/managing-labels-in-fleet).
3540

3641
## View a query report
3742

articles/role-based-access.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ GitOps is an API-only and write-only role that can be used on CI/CD pipelines.
9696
| View all [MDM settings](https://fleetdm.com/docs/using-fleet/mdm-macos-settings) | | | |||
9797
| Edit [macOS setup experience]([https://fleetdm.com/docs/](https://fleetdm.com/guides/macos-setup-experience))\* | | ||||
9898
| Add and edit identity provider for end user authentication, end user license agreement (EULA), and end user migration workflow\* | | | || |
99-
| Add and edit Simple Certificate Enrollment Protocol (SCEP) server\* | | | |||
99+
| Add and edit certificate authorities (CA)\* | | | |||
100100
| Run scripts on hosts | | ||| |
101101
| View saved scripts\* ||||| |
102102
| Edit/upload saved scripts\* | | ||||
@@ -130,6 +130,7 @@ Users with access to multiple teams can be assigned different roles for each tea
130130
| Filter hosts using [labels](https://fleetdm.com/docs/using-fleet/rest-api#labels) ||||| |
131131
| Target hosts using labels ||||| |
132132
| Add/remove manual labels to/from hosts | | ||||
133+
| Create and edit self-authored labels | | | | ||
133134
| Add and delete hosts | | ||| |
134135
| View software ||||| |
135136
| Add and delete software | | ||||
@@ -140,7 +141,7 @@ Users with access to multiple teams can be assigned different roles for each tea
140141
| Filter software ||||| |
141142
| Run queries designated "**observer can run**" as live queries against hosts ||||| |
142143
| Run any query as [live query](https://fleetdm.com/docs/using-fleet/fleet-ui#run-a-query) | |||| |
143-
| Create, edit, and delete only **self authored** queries | | ||||
144+
| Create, edit, and delete self-authored queries | | ||||
144145
| View team queries and their reports ||||| |
145146
| View global (inherited) queries and their reports\** ||||| |
146147
| Manage [query automations](https://fleetdm.com/docs/using-fleet/fleet-ui#schedule-a-query) | | ||||
@@ -155,7 +156,7 @@ Users with access to multiple teams can be assigned different roles for each tea
155156
| Add and remove team users | | | |||
156157
| Edit team name | | | |||
157158
| Create, edit, and delete [team enroll secrets](https://fleetdm.com/docs/using-fleet/rest-api#get-enroll-secrets-for-a-team) | | ||| |
158-
| Read organization settings\* ||||| |
159+
| Read organization settings\* ||||| |
159160
| Read agent options\* ||||| |
160161
| Edit agent options | | | |||
161162
| Initiate [file carving](https://fleetdm.com/docs/using-fleet/rest-api#file-carving) | | ||| |

articles/secrets-in-scripts-and-configuration-profiles.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ The dollar sign (`$`) can be escaped so it's not considered a variable by using
8383

8484
## Known limitations and issues
8585

86-
- Windows profiles are currently not re-sent to the device when the GitHub action (or GitLab pipeline) runs: [issue #25030](https://github.com/fleetdm/fleet/issues/25030)
86+
- After changing a secret used by a Windows profile, that profile is currently not re-sent to the device when the GitHub action (or GitLab pipeline) runs: [story #27351](https://github.com/fleetdm/fleet/issues/27351)
8787
- Fleet does not hide the secret in script results. DO NOT print/echo your secrets to the console output.
8888
- There is no way to explicitly delete a secret variable. Instead, you can overwrite it with any value.
8989
- Do not use deprecated API endpoint(s) to upload profiles containing secret variables. Use endpoints documented in [Fleet's REST API](https://fleetdm.com/docs/rest-api/rest-api).

0 commit comments

Comments
 (0)