Skip to content

Commit d406b73

Browse files
committed
Add changes
1 parent 82f1068 commit d406b73

File tree

1 file changed

+41
-72
lines changed

1 file changed

+41
-72
lines changed

docs/Configuration/agent-configuration.md

Lines changed: 41 additions & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# Agent configuration
22

3-
Agent configuration options (agent options) update the settings of [Fleet's agent (fleed)](https://fleetdm.com/docs/get-started/anatomy#fleetd) installed on all your hosts.
3+
Agent configuration (agent options) updates the settings of the [Fleet agent (fleed)](https://fleetdm.com/docs/get-started/anatomy#fleetd) installed on all your hosts.
44

55
You can modify agent options in **Settings > Organization settings > Agent options** or via Fleet's [API](https://fleetdm.com/docs/rest-api/rest-api#modify-configuration) or [YAML files](https://fleetdm.com/docs/configuration/yaml-files).
66

77
## config
88

99
The `config` section allows you to update settings like performance and and how often the agent checks-in.
1010

11-
####Example
11+
#### Example
1212

1313
```yaml
1414
config:
@@ -45,10 +45,6 @@ config:
4545
- /Users/wxs/sigs/baz.sig
4646
```
4747
48-
- `decorators`
49-
- `yara`
50-
- `auto_table_contructions`
51-
5248
### options and command_line_flags
5349
5450
- `options` include the agent settings listed under `osqueryOptions` [here](https://github.com/fleetdm/fleet/blob/main/server/fleet/agent_options_generated.go). These can be updated without a fleetd restart.
@@ -94,63 +90,16 @@ In the `decorators` key, you can specify queries to include additional informati
9490

9591
### yara
9692

97-
You can use Fleet to configure the `yara` and `yara_events` osquery tables. Fore more information on YARA configuration and continuous monitoring using the `yara_events` table, check out the [YARA-based scanning with osquery section](https://osquery.readthedocs.io/en/stable/deployment/yara/) of the osquery documentation.
98-
99-
### auto_table_construction
100-
101-
You can use Fleet to query local SQLite databases as tables. For more information on creating ATC configuration from a SQLite database, check out the [Automatic Table Construction section](https://osquery.readthedocs.io/en/stable/deployment/configuration/#automatic-table-construction) of the osquery documentation.
102-
103-
If you already know what your ATC configuration needs to look like, you can add it to an options config file:
104-
105-
```yaml
106-
agent_options:
107-
config:
108-
options:
109-
# ...
110-
overrides:
111-
platforms:
112-
darwin:
113-
auto_table_construction:
114-
tcc_system_entries:
115-
# This query and columns are restricted for compatability. Open TCC.db with sqlite on
116-
# your endpoints to expand this out.
117-
query: "SELECT service, client, last_modified FROM access"
118-
# Note that TCC.db requires fleetd to have full-disk access, ensure that endpoints have
119-
# this enabled.
120-
path: "/Library/Application Support/com.apple.TCC/TCC.db"
121-
columns:
122-
- "service"
123-
- "client"
124-
- "last_modified"
125-
```
126-
127-
If you're editing this directly from the UI consider copying and pasting the following at the end of your agent configuration block:
128-
129-
```
130-
overrides:
131-
platforms:
132-
darwin:
133-
auto_table_construction:
134-
tcc_system_entries:
135-
# This query and columns are restricted for compatability. Open TCC.db with sqlite on
136-
# your endpoints to expand this out.
137-
query: "SELECT service, client, last_modified FROM access"
138-
# Note that TCC.db requires Orbit to have full-disk access, ensure that endpoints have
139-
# this enabled.
140-
path: "/Library/Application Support/com.apple.TCC/TCC.db"
141-
columns:
142-
- "service"
143-
- "client"
144-
- "last_modified"
145-
```
93+
You can use Fleet to configure the `yara` and `yara_events` osquery tables. Learn more about YARA configuration and continuous monitoring [here](https://fleetdm.com/guides/remote-yara-rules#basic-article).
14694

14795
## extensions
14896

149-
> This feature requires [Fleetd, the Fleet agent manager](https://fleetdm.com/announcements/introducing-orbit-your-fleet-agent-manager), along with a custom TUF auto-update server (a Fleet Premium feature).
97+
> This feature requires a custom TUF auto-update server (available in Fleet Premium). Learn more [here](https://fleetdm.com/guides/fleetd-updates).
15098

15199
The `extensions` key inside of `agent_options` allows you to remotely manage and deploy osquery extensions. Just like other `agent_options` the `extensions` key can be applied either to a team specific one or the global one.
152100

153-
This is best illustrated with an example. Here is an example of using the `extensions` key:
101+
#### Example
102+
154103
```yaml
155104
agent_options:
156105
extensions: # requires Fleet's agent (fleetd)
@@ -205,15 +154,16 @@ Fleet recommends deploying extensions created with osquery-go or natively with C
205154

206155
### Targeting extensions with labels
207156

208-
_Available in Fleet Premium v4.38.0_
157+
_Available in Fleet Premium_
209158

210159
Fleet allows you to target extensions to hosts that belong to specific labels. To set these labels, you'll need to define a `labels` list under the extension name.
211160
The label names in the list:
212161
- must already exist (otherwise the `/api/latest/fleet/config` request will fail).
213162
- are case insensitive.
214163
- must **all** apply to a host in order to deploy the extension to that host.
215164

216-
Example:
165+
#### Example
166+
217167
```yaml
218168
agent_options:
219169
extensions: # requires Fleet's agent (fleetd)
@@ -232,24 +182,27 @@ agent_options:
232182
channel: 'stable'
233183
platform: 'windows'
234184
```
185+
235186
In the above example:
236187
- the `hello_world_macos` extension is deployed to macOS hosts that are members of the 'Zoom installed' label.
237188
- the `hello_world_linux` extension is deployed to Linux hosts that are members of the 'Ubuntu Linux' **and** 'Zoom installed' labels.
238189

239190
## update_channels
240191

241-
_Available in Fleet Premium v4.43.0 and fleetd v1.20.0_
192+
_Available in Fleet Premium_
242193

243194
Users can configure fleetd component TUF auto-update channels from Fleet's agent options. The components that can be configured are `orbit`, `osqueryd` and `desktop` (Fleet Desktop). When one of these components is omitted in `update_channels` then `stable` is assumed as the value for such component. Available options for update channels can be viewed [here](https://fleetdm.com/docs/using-fleet/enroll-hosts#specifying-update-channels).
244195

245-
Examples:
196+
#### Examples
197+
246198
```yaml
247199
agent_options:
248200
update_channels: # requires Fleet's agent (fleetd)
249201
orbit: stable
250202
osqueryd: '5.10.2'
251203
desktop: edge
252204
```
205+
253206
```yaml
254207
agent_options:
255208
update_channels: # requires Fleet's agent (fleetd)
@@ -281,10 +234,14 @@ B. Upgrading channel `B` to >= `1.20.0`.
281234

282235
The `overrides` key allows you to segment hosts, by their platform, and supply these groups with unique osquery configuration options. When you choose to use the overrides option for a specific platform, all options specified in the default configuration will be ignored for that platform.
283236

284-
In the example file below, all Darwin and Ubuntu hosts will **only** receive the options specified in their respective overrides sections.
237+
Note that the `command_line_flags` key is not supported in the `overrides`.
238+
239+
In the example file below, all macOS hosts will **only** receive the options specified in their respective overrides sections.
285240

286241
If a given option is not specified in a platform override section, its default value will be enforced.
287242

243+
#### Example
244+
288245
```yaml
289246
agent_options:
290247
overrides:
@@ -308,22 +265,34 @@ agent_options:
308265
- /Users/%/Documents/%%
309266
etc:
310267
- /etc/%%
268+
auto_table_construction:
269+
tcc_system_entries:
270+
# This query and columns are restricted for compatability. Open TCC.db with sqlite on
271+
# your endpoints to expand this out.
272+
query: "SELECT service, client, last_modified FROM access"
273+
# Note that TCC.db requires fleetd to have full-disk access, ensure that endpoints have
274+
# this enabled.
275+
path: "/Library/Application Support/com.apple.TCC/TCC.db"
276+
columns:
277+
- "service"
278+
- "client"
279+
- "last_modified"
311280
```
312281
313-
Note that the `command_line_flags` key is not supported in the `overrides`.
282+
### auto_table_construction
283+
284+
You can use Fleet to query local SQLite databases as tables. For more information on creating ATC configuration from a SQLite database, check out the [Automatic Table Construction section](https://osquery.readthedocs.io/en/stable/deployment/configuration/#automatic-table-construction) of the osquery documentation.
314285
315286
## script_execution_timeout
316287
317-
The `script_execution_timeout` allows you to change the default script execution timeout.
288+
The `script_execution_timeout` allows you to change the default script execution timeout (default: `300`, maximum: `3600`).
289+
290+
#### Example
318291

319-
- Optional setting (integer)
320-
- Default value: 300
321-
- Maximum value: 3600
322-
- Config file format:
323-
```yaml
324-
agent_options:
325-
script_execution_timeout: 600
326-
```
292+
```yaml
293+
agent_options:
294+
script_execution_timeout: 600
295+
```
327296

328297
<meta name="pageOrderInSection" value="300">
329298
<meta name="description" value="Learn how to use configuration files and the fleetctl command line tool to configure agent options.">

0 commit comments

Comments
 (0)