Security and good practice
The habits that keep your servers, your keys and your account safe.
Your account
- A long, unique password that you do not use anywhere else. The panel requires at least 8 characters with lowercase, uppercase, digits and a special character: longer is better.
- Changing it (Account → Security) closes sessions open elsewhere. If you receive the email Your Gigakube password was changed and it was not you, reset the password from Forgot password? and write to us.
- Invite people into projects with the lowest role that does the job (Projects and people). Can manage only for those who really need to manage access, consoles and kubeconfigs.
- When someone no longer works with you, Remove access: their API keys for that project stop working too.
- Now and then look at your projects' Recent activity: who did what, and from where.
Servers
- No open ports you do not need. The firewall starts closed: open it one port at a time.
- Never open SSH (22) to the whole internet: open it only from your address or your office network (Me button). That is why the platform always requires a source for ports other than 80 and 443, and only lets Can manage open them to everyone.
- Databases, queues, admin panels: do not open them to the internet. Put them on servers without a public address, or let only the project's other servers reach them, over the private network.
- Keep the servers' systems up to date (
sudo apt update && sudo apt upgradeon Ubuntu and Debian) and keep automatic security updates on. - If you think you will need the console, set a password for the user inside the server while you can still get in with SSH: without a password you cannot log in from the console.
- Watch the Protection section: if an attack Reaches the server on a port you do not need, close it.
- Before deleting anything, read the plan: deleting a server destroys its disk, deleting a cluster destroys its data. There is no undo.
SSH keys
- The private key stays on your computer, protected by a passphrase. Give the panel only the public one.
- One key per computer, with a name that says which. If you lose a laptop, remove its key from the servers (
~/.ssh/authorized_keys) and from the panel.
API keys
- The secret is shown once: keep it in a secrets manager or an environment variable, never in code, a repository, a log or a chat.
- One key per program, with the lowest role that does the job and, for tests, an expiry date.
- For AI agents: Requires my approval for every change. The agent reads and proposes, a person decides (Plans and change requests).
- If a key may have fallen into the wrong hands, revoke it immediately and create another.
Kubernetes
- The kubeconfig gives full rights on the cluster: treat it like a password. Do not send it in a chat, do not put it in a repository.
- Only Can manage and the owner can download it, and every read stays in the project's log.
DNS and domains
- The Cloudflare token you give us: restrict it to the zones you want to manage from here, with the permissions listed on the DNS page.
- If you move a domain to us from another provider that used DNSSEC, switch off DNSSEC at the registrar: otherwise the domain stops answering.
- Keep auto-renewal on for the domains you need, and keep credit in your account if you are on prepaid.
Reporting a security issue
If you find a security issue in gigakube.ch or in the platform, write to security@gigakube.ch: what you found, how to reproduce it, how to reach you. Please do not make it public before we have been able to fix it.