Engineered to protect internal infrastructure from SSRF, data leakage, and unauthorized access.
Every HTTP and WebSocket route is registered with an explicit permission class. Unmapped or unauthorized requests are rejected immediately.
All outbound HTTP, TCP, and SNMP traffic flows through internal/netx, blocking internal metadata endpoints (169.254.169.254) and forbidden subnets.
Passwords hashed with Argon2id; session & API tokens are 256-bit opaque random values stored as SHA-256 digests; secrets stored in AES-256-GCM envelopes.
Audit records are cryptographically linked using SHA-256 hash chaining, preventing retroactive modification or deletion by unauthorized actors.
Runtime application operates as gokuma_app with restricted DML privileges, while schema migrations run separately under gokuma_owner.
Public status pages strictly render admin-configured display labels and UP/DOWN state. Internal IPs, URLs, latency metrics, and errors are never exposed.
Security is fundamental to GoKuma. If you discover a vulnerability or security issue, please notify the security team directly. We appreciate coordinated disclosure and respond promptly.
Project Approver of Record & Security Contact: Mark Berry (security@vpnspaces.com)