Connect a repo or start from a template — we build, deploy, and route it with SSL.
Docs, an API, and a CLI — wired to the same platform your services run on.
Cloud Security Infrastructure: 6 Best Practices & Benefits

In the cloud, the security work that's left to you is where a stolen password, an access key with too much power or an API that returns other users' data turns into a breach. Your provider secures the data centers and the platform. What runs on top, including who can sign in and what they can reach, is yours. These six practices cover the parts that are yours, roughly in the order they pay off.
An earlier version of this post listed practices and benefits in general terms, with no sources. We've rewritten it around guidance from CISA, OWASP and the providers' own shared-responsibility model.
AWS describes the split as security "of" the cloud, which it handles, and security "in" the cloud, which is the customer's, and which depends on the services the customer chooses. The less infrastructure you run yourself, the less sits on your side. On a managed platform, patching the operating system is the provider's job; on a virtual machine you rent, it's yours.
Whatever the platform, three things stay on your side: who can sign in, what each person and service can do once inside, and the code you deploy.
1. Turn on phishing-resistant MFA. CISA calls phishing-resistant MFA "the standard all industry leaders should strive for," and adds that "any MFA is better than no MFA." It also notes that "the only widely available phishing-resistant authentication is FIDO/WebAuthn," which means security keys and passkeys. Start with the accounts that can change production: cloud consoles, source control and your domain registrar.
2. Give every person and service the least access it needs. Use roles instead of shared accounts, give each service its own credentials scoped to what it uses, and remove access the day someone leaves. Review who has administrator rights every quarter; the list grows on its own.
3. Keep secrets out of code. API keys and database passwords belong in your platform's secrets store or environment configuration, never in the repository. Rotate any secret that has been committed, even briefly, because history keeps it.
4. Check authorization on every API request. OWASP ranks "Broken Object Level Authorization" first in its 2023 API Security Top 10: APIs expose object identifiers, and if the server doesn't check that the caller may access that specific object, changing an ID in a request returns someone else's data. Test for it explicitly.
5. Encrypt in transit and at rest. Serve everything over HTTPS, including internal service calls where you can, and use storage and databases that encrypt data at rest. Many managed services do this by default; confirm it for each one rather than assume it.
6. Log what matters and keep a backup attackers can't delete. Record sign-ins, permission changes and deploys somewhere the production credentials can't erase. Our disaster recovery post covers backups and restore tests.
The tradeoff with every control above is friction. MFA prompts, narrow permissions and secrets stores all add steps, and a team under deadline pressure will work around steps that feel pointless: a shared admin account, a key pasted into a config file. The fix is to make the secure path the easy one. Use single sign-on so MFA happens once, give the deploy pipeline the permissions instead of people, and keep secrets in the platform so nobody needs to copy them.
If you do only two things this week, turn on phishing-resistant MFA for every account that can change production, and remove administrator access nobody needs. Those two close the easiest ways into an account. ComputeSphere runs your containers, databases and networking; the Docker deploy guide shows what you deploy and configure yourself.
Last checked November 14, 2026.
Fixed price per spherelet, flat plan per team — ship without DevOps or surprise bills.
Start free trial14-day free trial
Predictable per-spherelet pricing, a flat plan per team, and managed primitives built in — no DevOps, no surprise bills.
Browse Some Related Blogs
Connect a repo or start from a template — live URL, SSL, and zero DevOps, on predictable monthly pricing. 14-day free trial.