Cloud

Security testing and configuration review of AWS, Azure, Google Cloud and Kubernetes environments, within each provider's published testing rules and the shared responsibility model.

AWS security assessment

Configuration review and penetration testing of an AWS environment within the AWS testing policy: IAM, network exposure, storage, logging and the CIS AWS Foundations Benchmark, plus what needs AWS approval and how accounts are scoped.

Azure security assessment

Review and testing of Azure subscriptions and Entra ID-connected workloads against the CIS Microsoft Azure Foundations Benchmark, within Microsoft's rules of engagement, covering role assignments, network exposure, storage and logging.

Google Cloud security assessment

Review and testing of Google Cloud projects and organizations against the CIS Google Cloud Platform Foundation Benchmark: IAM bindings, service accounts and keys, network and firewall rules, storage exposure and audit logging.

Cloud IAM review

A focused review of identities, roles and policies across one or more clouds to find privilege escalation paths, unused or over-broad permissions and long-lived keys; lighter than a full assessment and often the first cloud engagement buyers commission.

Serverless security testing

Testing functions and their triggers, such as Lambda behind API Gateway, for injection through event data, over-privileged execution roles, secrets handling and SSRF to metadata services, and how it differs from testing servers.

Kubernetes security assessment

Assessment of a managed Kubernetes cluster (EKS, AKS or GKE) against the CIS benchmarks, Pod Security Standards and the NSA and CISA hardening guide: RBAC, workload isolation, network policies, secrets and cloud identity integration.

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.