Integrations / Managed-device rollout

Every managed Mac, in view through Jamf

Argent builds one script for your tenant. Jamf Pro runs it on the Macs you scope, and the command-line AI tools and SDKs on each one start sending their traffic through Argent's proxy, so the AI in use shows up without anyone installing anything by hand.

Jamf logo on a framed card
01 / INTEGRATIONS / MANAGED-DEVICE ROLLOUT

What Argent does with Jamf

Your Jamf already reaches every managed Mac. Argent gives it one script that puts the command-line AI on those machines in view.

Most of the AI in a company arrives before anyone registers it. Microsoft found 78% of AI users bring their own AI tools to work (Microsoft and LinkedIn, 2024 Work Trend Index). IBM found shadow AI was involved in security incidents at 43% of the breached organizations it studied, up from 20% a year earlier, and those breaches averaged $5.39 million (IBM, Cost of a Data Breach Report 2026). NIST's AI Risk Management Framework asks for an inventory of AI systems, under GOVERN 1.6 (NIST AI RMF Playbook).

This is Level 2 of Argent's Discovery, the step after reading your proxy logs. Argent builds the script for your tenant; Jamf runs it on every machine in scope.

  • What the script sets. The Argent certificate, a combined certificate bundle, and the standard proxy settings that command-line AI tools and SDKs read: HTTPS_PROXY pointed at Argent's proxy, NO_PROXY, and the certificate variables each tool reads, such as NODE_EXTRA_CA_CERTS, SSL_CERT_FILE and REQUESTS_CA_BUNDLE.
  • What it never carries. No private key, no agent key and no password. The proxy setting has no credentials in it: a managed machine is admitted by the network it connects from.
  • What Argent sees. Which AI services each managed machine reaches, as a discovered client in the Agent inventory, tagged "Seen via managed network".
  • Machine scope, safe to repeat, reversible. Running it again converges to the same state, and the uninstall option removes what it added.

The same push kit also comes for Kandji (now Iru) and Microsoft Intune, Group Policy and Linux.

02 / INTEGRATIONS / MANAGED-DEVICE ROLLOUT

What the script changes on each Mac

One shell script, run as root. Here is everything it touches.

On the MacWhat changes
System keychainArgent's tenant certificate added as a trusted root (left alone when your tenant uses a company-signed chain)
/Library/Argentargent-ca.pem, and argent-ca-bundle.pem: the system roots plus Argent's, for tools that replace the trust store
LaunchDaemonai.argent.fleet-env sets the proxy and certificate variables for every process at startup
/etc/zshenvThe same variables for shells, in one marked block the script can find and remove
  • Internal sites stay direct. Fill in the INTERNAL_DOMAINS line with a comma list such as .corp.example.com,.internal. Loopback, Argent's own hosts and the proxy itself are already excluded.
  • Undo is one command. sh argent-fleet-jamf.sh uninstall removes the variables, the LaunchDaemon, the marked block, the certificate it added and the folder.
  • Re-run after root updates. The bundle holds a copy of the system roots, so run the script again after a macOS root-certificate update. It is safe to run any number of times.
03 / INTEGRATIONS / MANAGED-DEVICE ROLLOUT

How it connects

You download the script from the Argent console; your device management pushes it. Argent never signs in to your management server.

DirectionDownload from Argent, push from your device management. Nothing calls back into it
Where to get itDiscovery page, Level 2 "Push to managed machines". Behind it: GET /v1/noc/setup/fleet?os=mac&format=jamf
Who can download itA TenantAdmin gets a script for their own tenant only. A SuperAdmin must pick one tenant first
Fileargent-fleet-jamf.sh, built for your tenant on each download and never cached
What is insideArgent's proxy address and your tenant's public certificate. Anything other than a public certificate is refused before a script is built
Traffic pathCommand-line tools on managed machines send their traffic to Argent's forward proxy. Only machines from network ranges an administrator approved are admitted

If the forward proxy is not switched on for the tenant, the download is refused with a plain reason instead of producing a script that cannot work.

04 / INTEGRATIONS / MANAGED-DEVICE ROLLOUT

What you configure

Five steps across the Argent console and Jamf Pro. Nobody touches a laptop by hand.

  1. Switch Discovery on. It is off until an admin turns it on for the tenant, under Policy > Settings.
  2. Add your managed networks. On the Discovery page, under Sources, add a managed network with the office or VPN ranges your machines connect from. A SuperAdmin approves it; until then Argent admits nothing from those ranges.
  3. Download the Jamf script. On the Discovery page, open Level 2 "Push to managed machines" and download the Jamf script. Fill in INTERNAL_DOMAINS if you have internal sites.
  4. Add it to Jamf Pro. Under Settings > Computer management > Scripts, choose New and paste the script (Jamf: adding a script). Then create a policy under Computers > Policies, add the script in the Scripts payload, set the trigger to Recurring Check-in in the General payload and scope it to your Macs (Jamf: running scripts using a policy). In-scope Macs run it the next time they check in.
  5. Check it worked. Run an AI tool on a managed Mac. The managed network shows Receiving data under Sources.

Give the policy a frequency that runs it again from time to time. The script is safe to repeat, and a re-run picks up macOS root-certificate updates.

05 / INTEGRATIONS / MANAGED-DEVICE ROLLOUT

Which certificate it installs

The script installs whichever certificate your tenant uses, and it follows the active one by default.

OptionWhat the machine getsWhen to use it
Argent tenant certificateArgent's per-tenant certificate added as a trusted root, plus the bundleYou have not had your own certificate authority sign Argent's
Company-signed chainThe chain under your own company root. No new root is added, because your machines already trust itYour certificate authority signed Argent's certificate
  • Narrow by design. Argent's certificate can only issue for the AI services in its catalog, written into the certificate as name constraints. A stolen copy of its key could not impersonate your email, your intranet or any site outside that catalog.
  • No accidental root. When your tenant runs a company-signed chain, Argent refuses to build a script that would install it as a root.
  • Your own root, if you prefer. Download a signing request from the Discovery page, sign it with your company root, upload the chain, then download the script with the company-signed option. Downloading the signing request and uploading the chain each need a fresh passkey check.
06 / INTEGRATIONS / MANAGED-DEVICE ROLLOUT

What Argent sees, and what it never reads

Discovery and control stay separate: Discovery records which AI services each machine reaches and changes no request it admits.

  • Admitted by network, not by key. A managed machine holds no Argent key. Argent admits it only if it connects from a range listed as a managed network for your tenant. A new range reads "Awaiting SuperAdmin approval" and admits nothing until it is approved, and a range that overlaps another tenant's is refused by the database.
  • Tunnelled, never decrypted. For a machine admitted this way, each connection is a plain tunnel on port 443: Argent records which AI service it reached, never what was said. Connection caps per machine and per tenant keep one noisy machine from crowding out the rest.
  • Shown as discovered. Each client turns up in the Agent inventory tagged Discovered and "Seen via managed network", with type, version and counts.
  • Honest status. The Discovery page shows each level as Off, Awaiting approval, No data received or Receiving data. Silence never reads as "no AI usage".
  • Ready for registration. The certificate settings are the same ones Argent gives a registered agent, so the machine-wide push and a developer's registered agent never disagree.
07 / INTEGRATIONS / MANAGED-DEVICE ROLLOUT

From discovery to control

The script makes the AI on managed machines visible. Registration and enforcement bring it under control, one step at a time.

  1. Start with logs if you like. Level 1 reads a copy of the access log your proxy already writes, with nothing installed: Squid proxy logs or any proxy as NDJSON.
  2. Review what turned up. Every client Argent sees but nobody registered appears in the Agent inventory tagged Discovered.
  3. Register what you keep. Developers register agents with a named human owner, so each gets an identity and a signed record of every request. See Identity Tethering and Keyless Agents.
  4. Watch, then enforce. Registered agents start in watch: requests pass unchanged and what each control would have refused or changed goes on the signed record. Then switch controls to enforce, one at a time. See Watch Before You Enforce.
08 / INTEGRATIONS / MANAGED-DEVICE ROLLOUT

Where this fits

Pages that go deeper.