Security

Security and access control

Access, outbound agent enrollment, least privilege and secrets handling in whycloud.

Identity and role separation

Organization roles and agent permissions are checked for sensitive operations. Treat short-lived enrollment tokens as secrets.

Outbound connections

Agents and operators initiate outbound connections. Enable Shell, install and monitoring permissions only where required.

Secrets boundaries

Secret environment values should not be returned in normal API responses. Use dedicated secret-management and rotation systems for sensitive production workloads; this release is not a complete secrets platform.

Production configuration

Set COOKIE_SECURE=true, enforce TLS, use an exact PUBLIC_ORIGIN, disable OTP_DEV_MODE and monitor audit events.

Related guides