TensorOne

Read-only access requirements · v1

Exactly what a TensorOne service account is granted on each platform, so your security team can review it before anything is provisioned — not after.

Least privilege, read-only, everywhere. Every account described here is read-only. TensorOne never writes to your infrastructure — it does not power, reconfigure, migrate, or snapshot anything, does not browse datastore or disk contents, and does not touch guest operating systems, memory, or application data. It collects configuration and event state through the interfaces below and nothing else.

Credentials you provision are stored encrypted on the collector VM and used only for the reads listed. No credential leaves your network, and the collector installs nothing on your hypervisors.

Two ways we collect — and what each needs

Passive syslog — no account

Point hypervisor and appliance syslog at the collector. This needs no service account and no inbound access to your hosts: your devices send to us. Most of the security signal arrives this way.

Read-only API polling — scoped account

For inventory, configuration, and posture state, the collector polls each platform's management API with a dedicated read-only account, scoped as below. One account per platform you enable.

Per-platform grants

VMware (Broadcom) vSphere / vCenter

HTTPS · vCenter :443 · vSphere API session
  • GrantA dedicated Read-only role, assigned to the service account at the vCenter root object with propagation to children. No write, administrator, datastore-browse, console, or guest-operation privileges.
  • We readProduct version and build; active sessions and installed extensions; virtual-machine inventory (power state, guest tools/IP, UUIDs); hosts and clusters (hardware, firewall rulesets, running services, advanced and security-hardening settings, virtual networking, CDP/LLDP neighbors); datastores (capacity and type); alarm definitions; and the vCenter event stream.
  • NoteThe account creates transient, server-side container views and an event collector, which the Read-only role already permits; both are destroyed when the session closes. No inventory object is ever modified.
  • We neverReconfigure or power VMs, browse or read datastore files, or access any guest OS.

Nutanix Prism (Central & Element)

HTTPS · Prism :9440 · v4 REST
  • GrantA Prism Central account (local or IdP) with the built-in Viewer role — or a custom role with read access — scoped to the target clusters. All calls are HTTP GET.
  • We readPrism Central and cluster identity and version; AHV hosts (hardware, CPU/memory, hypervisor/CVM/IPMI addresses); virtual machines (power, sizing, NIC addresses, guest tools); storage containers; audit records; and alert policies.
  • We neverWrite to Prism, change configuration, or read guest data. A viewer role that lacks scope on a cluster simply returns nothing — it cannot escalate.

Proxmox VE

HTTPS · Proxmox :8006 · API token
  • GrantAn API token assigned the built-in PVEAuditor role at path / with propagation. PVEAuditor is read-only by design — it carries no VM.* write, Sys.Modify, or console privileges.
  • We readNode, VM, and container inventory; cluster and storage configuration; and task/log history.
  • We neverCreate, modify, migrate, or control guests; open a console; or change cluster configuration.

OpenShift Virtualization / KubeVirt

Kubernetes API · ServiceAccount token
  • GrantA ServiceAccount bound via ClusterRoleBinding to the built-in view ClusterRole, plus a small custom ClusterRole granting get/list/watch on kubevirt.io and cdi.kubevirt.io resources. No create/update/delete, no secrets read, no exec/console.
  • We readNodes; VirtualMachines and VirtualMachineInstances; namespaces; and Kubernetes events.
  • We neverMutate objects, read Secrets, or exec into pods or VMs.

KVM / libvirt

libvirt · qemu:///system · read-only
  • GrantA service account with read-only libvirt access — the read-only connection / socket (virConnectOpenReadOnly). No define, start, stop, or migrate rights.
  • We readDomain (VM) inventory and host capabilities.
  • We neverDefine, start, stop, or migrate domains, or write host configuration.

Cloud — AWS CloudTrail

AWS API · IAM role · read-only
  • GrantAn IAM role or policy with read-only access: cloudtrail:LookupEvents, and — if reading from the trail's delivery target — s3:GetObject on the trail bucket or sqs:ReceiveMessage on its queue. No management or write actions.
  • We readCloudTrail management events for the account/region you scope.
  • We neverTake management actions, modify resources, or read data-plane object contents.

Verify it yourself

Each role above is a standard, named read-only role on its platform — auditable by your team before you grant it and at any time after. If a grant here exceeds what your policy allows, tell us; we would rather narrow the scope than have you approve something you can't fully account for.