SECURITY / 05

Cloud Platforms.

Security considerations across cloud environments and workloads.

Start a Conversation

SECTION OVERVIEW

About Cloud Platforms

Reviewing and hardening the platforms your workloads run on.

01

Scope

Posture review and hardening for cloud workloads, storage and control planes.

02

Approach

Control-plane permissions are examined alongside workload configuration, because the two fail together.

03

Engagement

Delivered as assessment first, remediation second, and ongoing monitoring where you want it carried.

PLATFORMS WE WORK ACROSS

Comfortable integrating under any of these

Cloud work is only useful if it meets you where your workloads already run. We are comfortable integrating with, assessing and hardening environments on each of the major cloud platforms — using the provider’s own identity, logging and network primitives rather than a layer bolted on top.

Amazon Web Services

IAM policies and roles, S3 exposure, security groups, KMS, and CloudTrail coverage across accounts.

Microsoft Azure

Entra ID and RBAC assignments, storage account access, network security groups, Key Vault and Defender findings.

Google Cloud

IAM bindings and service accounts, Cloud Storage permissions, VPC and firewall rules, organisation policy constraints.

Alibaba Cloud

RAM users and policies, OSS bucket exposure, security groups, and ActionTrail logging.

Oracle Cloud Infrastructure

Compartment design and IAM policies, object storage visibility, and network security lists.

IBM Cloud

IAM access groups, Cloud Object Storage permissions, and VPC security configuration.

OVHcloud

Public cloud instances and bare metal, vRack private networking, object storage permissions and IAM policies.

DigitalOcean

Droplet and cloud firewall configuration, Spaces permissions, managed database exposure and VPC boundaries.

Vultr

Instance and firewall rules, Object Storage access, VPC isolation and snapshot integrity.

Scaleway

IAM applications and policies, Object Storage visibility, security groups and private networks.

All product names, logos and brands are the property of their respective owners and are shown for identification only; their use does not imply endorsement. Running somewhere not listed here? Ask — the approach is the same: control plane first, then the workloads underneath it.

LET'S CONNECT

Want to know more of our solutions?

Contact us to start the conversation.

Contact Us
PROD / v3.0