
Find the AI already in use from your Squid logs
Send Argent a copy of the access log your Squid proxy already writes. Argent keeps only visits to AI services it recognizes, records who reached which one, and drops all other lines. Nothing is installed and no traffic is rerouted.
What Argent does with your Squid logs
Your Squid proxy already sees which AI services your people reach. Argent turns that log into an inventory, without touching the traffic.
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 the share of security incidents involving unapproved ("shadow") AI more than doubled, to 43% from 20%, and those breaches averaged $5.39 million (IBM, Cost of a Data Breach Report 2026). NIST's AI Risk Management Framework, GOVERN 1.6, says "Mechanisms are in place to inventory AI systems and are resourced according to organizational risk priorities" (NIST AI RMF Playbook).
This is Level 1 of Argent's Discovery, the step that needs nothing new on anyone's machine.
- What Argent keeps. For each AI service it recognizes, a count of requests and bytes by login, device and client IP, the client family (for example
claude-code/2.0), and what your proxy did: allowed or denied. - What Argent never keeps. Raw log lines, URL paths, query strings, user-agent strings, or any host outside its catalog of AI services. Other lines are dropped before anything is stored.
- Who reached what, never what was said. A proxy log has no prompts in it, and Argent adds none.
- A signed record. Each rollup is written as one signed discovery record, kept apart from AI spend and latency figures.
- Observation only. Your proxy keeps running exactly as it does today. Argent records what it already did.
How it connects
Your log shipper sends the log to Argent over HTTPS. Argent never reaches into your proxy.
| Direction | Push: your side sends, Argent receives |
| Endpoint | POST /_argent/ingest/proxylog on your Argent gateway |
| Sign-in | A bearer token for the log feed, sent as Authorization: Bearer <token> |
| Format | The Argent Squid log format, one line per request |
| Compression | Plain text or gzip |
| Tenant | Taken from the token only. Nothing in a log line can name a tenant |
The log format Argent reads is a Squid logformat you add to squid.conf:
logformat argent %ts.%03tu %>a %un %rm %ru %>Hs %<st %>st "%{User-Agent}>h"
In order: time, client IP, the user name the proxy knows, if any, method, URL, status, bytes sent to the client, bytes received from it, and the user agent. Argent reads each field by position, so the format must match exactly (Squid's own docs: logformat, access_log). The setup guide on Argent's Discovery page adds one more access_log that writes this format to syslog, access_log syslog:local0.info argent, keeping your existing logs as they are, and gives an rsyslog omhttp config that posts the lines to Argent over HTTPS in batches.
If your shipper gets an error back: 401 means the token is wrong or was rotated, 403 means Discovery is switched off for the tenant, 413 means the request was too large, 429 means slow down and retry, and 503 means retry shortly. An unknown, disabled or wrong-kind token gets the same 401, and the token is never echoed or logged.
What you configure
Five steps, in the Argent console and your proxy's config. Nobody installs anything on a laptop.
- Switch Discovery on. It is off until an admin turns it on for the tenant, under Policy > Settings.
- Add a log feed. On the Discovery page, under Sources, add a source of kind Log feed with the format Squid. Argent shows its token once and keeps only a hash; rotate the token to get a new one.
- Add the log format. Add the
logformat argentline above tosquid.conf, plus oneaccess_logthat writes it. - Ship the lines. Point your log shipper, such as rsyslog with
omhttp, at/_argent/ingest/proxylogwith the feed's token as a bearer credential, plain or gzip. - Check the feed. Browse to an AI tool from a machine behind the proxy. The source then shows Receiving data under Sources; a feed that goes quiet shows No data received.
Feeds can be disabled at any time from the same Sources panel, and a disabled feed's token stops working.
Built to take a hostile log line
A log line is data from outside. Argent treats every one as untrusted.
- Only the fields it needs. Every value that reaches a record is checked against a closed character set first. A login outside that set drops the line; it is never rewritten into a different person.
- Secrets never read. A CONNECT target or a URL is cut down to its host. The path, query string and any user name or password inside the URL are discarded unread.
- No user-agent strings kept. The user agent is reduced to a client family and version, such as
claude-code/2.0, so no token, hostname or build path in it reaches the record. - Size and rate limits. Bodies are capped before and after decompression, so a compressed bomb is refused, and each line has its own cap. Each feed has its own rate limit, and one tenant cannot take every slot.
- All or nothing. A push is counted only when the whole body was read within the limits. A refused or retried push leaves nothing behind, so a retry never double counts.
- Silence is not safety. Each feed has its own health counters. A feed that goes quiet reads "No data received", never "no AI usage".
From discovery to control
Discovery is the first half. Control is the second, and the two stay separate, so nothing breaks on day one.
- Review what turned up. Every client Argent sees but nobody registered appears in the Agent inventory tagged Discovered and "Seen via proxy log feed", with types, versions and counts.
- Add managed machines. Level 2 puts the Argent certificate and proxy settings on company machines through your device management: Jamf, Kandji or Microsoft Intune. Only machines from ranges an administrator approved are admitted.
- 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.
- Watch, then enforce. In a new tenant, 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.
Where this fits
Pages that go deeper.
- Same ingest, any proxy: if your proxy or log pipeline is not Squid, send the generic NDJSON format instead.
- Capabilities: Shadow AI Discovery, Watch Before You Enforce, One-Click Audit Evidence and all capabilities.
- Goals: See all AI in your company, audit and accountability, compliance evidence and all goals.
- Use cases: securing AI coding agents, rolling out copilots and chat safely and AI in regulated and air-gapped environments.
- Where it runs: air-gapped on-premises, private cloud or your public cloud VPC. Compare them on deployment options.
- Industries: Financial Services, Insurance, Healthcare, Public Sector and all industries.
- More integrations: every system Argent connects to, grouped by type, on the integrations page.
Want this running on your own use cases?
All downloads