Identities and permissions
Over-privileged users and roles, access keys and multi-factor authentication.
Most cloud breaches come from a setting, not a software flaw. We review your AWS, Azure and Google Cloud accounts with that in mind.
In the cloud the provider protects the infrastructure, but the settings inside your account are your responsibility. A storage bucket left public, a user with more rights than needed or a management port open to the internet can each cause a major data leak. In a cloud security review we go through identity, network, data and logging, rank the findings by priority and show how to fix each one.
Over-privileged users and roles, access keys and multi-factor authentication.
Public or unencrypted storage and backups.
Ports open to the internet, security groups and management access.
Whether audit logs are on and retained, and alert rules.
Cluster access, image security and how secrets are stored.
Roles and app permissions in identity systems such as Entra ID and Google Workspace.
A read-only, time-limited access is set up for the review.
Accounts are checked automatically against the CIS Benchmarks.
Architecture, permissions and data flows are reviewed by hand and false positives removed.
Findings are ranked by priority, each with the steps to fix it.
If you like, we fix the settings together and check again.
A read-only, time-limited access is enough. We change nothing during the review; fixes are made separately with your approval.
We review AWS, Microsoft Azure and Google Cloud accounts. If you use more than one, they all go into a single report.
The provider protects the data centres and infrastructure. Users, permissions, storage and network settings are your responsibility; this is called the shared responsibility model. Most leaks come from that second part.
Twinlike · Live chat
Real people, no bots. We usually reply within a few minutes.
This chat has ended.