DHCP leases endpoints

Not yet available

The DHCP lease-feed API described below is planned but not implemented — there are currently no /v1/leases endpoints in the cloud API, and no lease feeder ships in the agents bundle. This page documents the intended design so you can plan for it; do not build against it yet.

The plan: your DHCP server POSTs lease snapshots; the cloud joins them at display time to enrich audit rows with hostnames the collector couldn't resolve.

Until this lands, hostname enrichment comes from the sources that exist today:

• Reverse DNS / mDNS at the collector — automatic where PTR records or Bonjour are present.
• The identity map — push IP→user mappings via POST /v1/identity/upsert (User-ID connector, CSV upload, or manual entries on the Identity page).
• In-agent identity — the kilasec_agent package names traffic from inside the agent process, which beats any network-side join.