Fleet and install keys

Visibility → Fleet lists every machine enrolled into the current tenant.

Column	Meaning
Machine	Hostname the machine enrolled with
User	The person who enrolled it (the console user when enrolled elevated)
OS	darwin, linux or windows, and amd64 or arm64
Version	Collector (CLI) version
Last seen	Time of the last report of any kind
Responses	AI responses reported from the machine in the selected window
Status	Active, Quiet (enrolled but not reporting recently), or Revoked

A quiet machine is off, asleep, or no longer running the collector. From the outside these look identical, and Shield360 doesn’t guess between them.

Revoking a machine

Revoke a machine to reject its token immediately. It can’t report again until it’s re-enrolled with a valid install key. Data it already reported is kept.

GET    /api/collector/devices
DELETE /api/collector/devices/{id}

Install keys

Install keys are managed under Visibility → Setup.

GET    /api/collector/install-keys
POST   /api/collector/install-keys
DELETE /api/collector/install-keys/{id}

A key is shown once, when it’s created, and can be given an expiry date. Shield360 stores only its SHA-256 hash. An expired or revoked key can’t enrol new machines. Revoking a key stops new enrolments with it. Machines already enrolled with it keep their own tokens and keep reporting.