Integrations / Proxy log import

Any proxy, one format, the same AI inventory

If your proxy, secure web gateway or log pipeline can write one JSON object per request, Argent can read it. Argent keeps only visits to AI services it recognizes, records who reached which one, and drops all other lines.

JSON log records in braces, with the one record that reaches an AI service highlighted
01 / INTEGRATIONS / PROXY LOG IMPORT

What Argent does with your proxy logs

The same discovery as the [Squid feed](/solutions/integrations/squid-proxy-logs/), for any source that can emit the documented NDJSON schema.

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: a copy of a log you already keep, with nothing installed and no traffic rerouted.

  • 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, denied or unknown.
  • What Argent never keeps. Raw records, URL paths, query strings, user-agent strings, or any host outside its catalog of AI services.
  • A signed record. Each rollup is written as one signed discovery record.
  • Your richer feed is fine. Fields Argent does not use are ignored, so nobody has to trim an export before sending it.
02 / INTEGRATIONS / PROXY LOG IMPORT

The schema

One JSON object per line ([NDJSON](https://github.com/ndjson/ndjson-spec)). Argent reads ten fields and ignores the rest.

FieldWhat it holds
tsRequired. Time of the request: an RFC 3339 string or Unix seconds
userThe login your proxy authenticated, if any
client_ipThe client's IP address
deviceThe device hostname, if your proxy knows it
hostRequired. The destination: a host, host:443 or a URL. Argent keeps only the host
statusHTTP status your proxy returned
bytes_outBytes sent by the client
bytes_inBytes returned to the client
user_agentThe client's user agent. Reduced to a family and version, never stored
actionWhat your proxy did, such as allow or block. If absent, Argent reads it from status

At least one of user, device or client_ip must say who made the request. A missing count reads as zero. When a record names more than one identity, Argent groups by the strongest it carries: login, then device, then client IP. The grouping key is a per-tenant digest, not the raw value.

03 / INTEGRATIONS / PROXY LOG IMPORT

How it connects

Your log pipeline pushes the file to Argent over HTTPS. Argent never reaches into your proxy.

DirectionPush: your side sends, Argent receives
EndpointPOST /_argent/ingest/proxylog on your Argent gateway
Sign-inA bearer token for the log feed, sent as Authorization: Bearer <token>
FormatNDJSON, chosen when you add the feed
CompressionPlain, or gzip with Content-Encoding: gzip
TenantTaken from the token only. Nothing in a record can name a tenant

Send a batch of lines as the body of one POST. The same error codes apply as for the Squid feed: 401 wrong or rotated token, 403 Discovery off, 413 too large, 429 slow down, 503 retry shortly.

04 / INTEGRATIONS / PROXY LOG IMPORT

What you configure

Four steps. Nobody installs anything on a laptop.

  1. Switch Discovery on. It is off until an admin turns it on for the tenant, under Policy > Settings.
  2. Add a log feed. On the Discovery page, under Sources, add a source of kind Log feed with the format Generic (NDJSON). Argent shows its token once and keeps only a hash; rotate the token to get a new one.
  3. Map your fields. Have your pipeline write the ten fields above, one object per line, and send the file to /_argent/ingest/proxylog with the feed's token.
  4. Check the feed. After the first AI request, the source shows Receiving data under Sources; a feed that goes quiet shows No data received.
05 / INTEGRATIONS / PROXY LOG IMPORT

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".
06 / INTEGRATIONS / PROXY LOG IMPORT

From discovery to control

Discovery is the first half. Control is the second, and the two stay separate, so nothing breaks on day one.

  1. 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.
  2. 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.
  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.
  4. 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.
07 / INTEGRATIONS / PROXY LOG IMPORT

Where this fits