Revise deployment steps for Santa at Fleet (#43239)

Removed the section on deploying the Santa osquery extension manually,
as we now include that in Fleet by default.

Slack thread for context:
https://fleetdm.slack.com/archives/C08PCMKAFTP/p1775065630945889
This commit is contained in:
kitzy 2026-04-08 11:10:48 -04:00 committed by GitHub
parent 642f98a59e
commit dbc9959c94
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -79,15 +79,7 @@ Here's a snippet from our [Santa rules configuration profile](https://github.com
</array>
```
**Step 3. Deploy Santa Extensions**
Policy to check if extensions exist: https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/macos/policies/install-santa-extension.yml
Script to install the extensions: https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/macos/scripts/install-santa-extension.sh
We chose to deploy these via policy automation since the Santa extensions don't exist natively in Fleet. We have a policy that checks for the existence of the Santa extension. If it is not found, Fleet will immediately run a remediation script that handles the download and configuration of fleetd to start using the extension.
**Step 4. Collect Santa Events**
**Step 3. Collect Santa Events**
Collect Santa denied logs: https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/macos/queries/collect-santa-denied-logs.yml