Skip to main content
Use this page as the Claude-specific Jamf entry point. For complete managed forwarding setup, follow the destination-specific self-serve guide:

Deploy Beacon With Jamf And S3

Install Beacon with Jamf Pro, inject AWS provider settings through MDM, configure Claude Code hooks, and forward runtime plus inventory JSONL to S3.

Deploy Beacon With Jamf And CrowdStrike Falcon

Install Beacon with Jamf Pro, configure Claude Code hooks, and forward runtime JSONL to CrowdStrike Falcon LogScale HEC.

​
What The Jamf Claude Flow Installs

The packaged Claude Jamf helpers configure:
  • the Beacon system endpoint collector
  • Claude Code hooks for the logged-in console user
  • /var/log/beacon-agent/runtime.jsonl for runtime activity
  • /var/log/beacon-agent/inventory_state.jsonl for metadata-only inventory snapshots
  • optional Vector forwarding for supported destinations such as AWS S3 or Falcon LogScale
End users should not need to run Beacon commands or edit local Beacon configuration when the Jamf policy is configured correctly.

​
Packaged Helper Scripts

The macOS package includes these Claude-specific helpers:
Use repair-hooks.sh when you only need to repair the system endpoint and reinstall Claude hooks. Use s3/repair-hooks-and-forwarder.sh when one Jamf policy should repair the endpoint, reinstall Claude hooks, and configure S3 forwarding. Use falcon/repair-hooks-and-forwarder.sh when one Jamf policy should repair the endpoint, reinstall Claude hooks, and configure CrowdStrike Falcon LogScale HEC forwarding.

Jamf Pro Overview

Review the general Beacon Jamf deployment model and package layout.

S3 Log Forwarding

Review the generated S3 content pack and Vector forwarding behavior.

CrowdStrike Falcon LogScale

Review Falcon parser setup, HEC settings, and validation steps.