HYPHAby S33D
Documentation › Administer

Security

What HYPHA does to limit what an agent, a key or an account can do, and where your data goes.

The agent

Signed updates

Every published binary is listed in SHA256SUMS, signed with ed25519. The agent checks the signature with the public key built into it, then the binary's sum, then runs it to check its version and the configuration, before installing it. A missing or wrong signature stops the update. See Fleet and updates.

Script installation checks the SHA-256 sum of the downloaded binary.

Read-only connectors

Each connector asks for the smallest read permission the provider offers:

ConnectorPermission requested
AWSec2:DescribeInstances, ec2:DescribeInstanceStatus, ec2:DescribeVolumes, cloudwatch:DescribeAlarms, sts:GetCallerIdentity
AzureReader role on the subscription
Google Cloudroles/compute.viewer
OVHcloud"consumer" key limited to GET
ScalewayInstancesReadOnly, ElasticMetalReadOnly
vSphereReadOnly role
Proxmox VEtoken with the PVEAuditor role
Kubernetesget, list, watch on nodes, pods, events, workloads; no secrets, logs or exec
Databasespg_monitor, PROCESS and REPLICATION CLIENT, clusterMonitor, RabbitMQ monitoring tag; read-only sessions
SNMPread-only v3 account, authPriv recommended

Allow-listed repairs

Remote actions are off by default. When on, they only pass named actions, on the services allowed by the host's configuration, with a deny list (SSH, the agent itself, systemd). No free command; a script is designated by its name, its path comes from the host. An action must be approved by an administrator and expires if no one picks it up. See Explain and repair.

Accounts, keys and records

Data

Personal data processing is described in the privacy policy.

Report a vulnerability

Write to contact@s33d.fr with the steps to reproduce it. Please give us time to fix it before any disclosure.

Updated: 19 November 2026