EN · DE Request an offer
Services

Cloud Security

Security tests of the components within a cloud environment.

Overview

AWS, GCP, Azure and their configuration

During a cloud security test, the settings of the environment at the cloud provider (e.g. AWS, GCP, Azure) are verified and checked for misconfigurations. In addition, vulnerabilities in the APIs, applications and cloud instances used are identified.

For example, our analysts search for tokens that grant access to resources of the cloud environment and for exposed, unprotected APIs.

Focus areas

  • Identity and access management
  • Publicly accessible resources
  • Network security
  • Secrets and key management
  • Compute, container and serverless services
  • Data encryption
  • Logging and monitoring
  • Infrastructure as code
Scope

What we test

Depending on your environment and the agreed scope, we examine in particular:

Cloud environment (AWS, GCP, Azure)

Identity and Access Management

Review of users, roles, groups, policies, service accounts and managed identities for excessive permissions, privilege escalation paths and insecure trust relationships (e.g. between accounts or tenants), and of the protection of privileged accounts by multi-factor authentication (MFA) and conditional access policies (e.g. in Microsoft Entra ID).

Publicly Accessible Resources

Identification of resources that can unintentionally be reached from the internet, such as storage buckets, databases, snapshots, virtual machines and management ports.

Network Security

Review of virtual networks, security groups, firewall rules, private endpoints and connections to on-premises and other networks (e.g. VPN, peering, AWS Direct Connect or Azure ExpressRoute).

Secrets and Key Management

Review of the handling of passwords, access keys and certificates, for example in key management services, environment variables, start-up scripts and deployment templates.

Compute, Container and Serverless Services

Review of virtual machines (e.g. protection of the instance metadata service), container platforms (e.g. Kubernetes services and container registries) and serverless functions for insecure configurations.

Data Encryption

Review of the encryption of data at rest and in transit and of the management of the keys used.

Logging and Monitoring

Review of whether security-relevant events are logged and retained (e.g. AWS CloudTrail, Azure Activity Log) and whether security services of the cloud provider are used to detect attacks.

Backup and Recovery

Review of the backup and recovery mechanisms, in particular whether backups are protected against deletion or manipulation by an attacker.

Infrastructure as Code

On request, review of templates for automated provisioning (e.g. Terraform, CloudFormation or Bicep) for insecure configurations.

Security Policies and Compliance

Review of whether existing security policies are enforced technically (e.g. through Azure Policy or AWS Service Control Policies).

Approach

How it works

  1. 1
    Scoping

    Objectives, rules of engagement and time frame, agreed in writing.

  2. 2
    Testing

    Hands-on testing by experienced analysts, supported by tools.

  3. 3
    Reporting

    Management summary, reproducible findings and remediation advice.

  4. 4
    Retest

    On request, we verify your fixes and update the report.

Results

What you receive

  • Management summary, understandable without prior technical knowledge
  • Overview of all findings with their risk rating
  • Technical details for each vulnerability: affected systems, evidence and specific remediation advice
  • Description of the procedure, the tools used and the rating scheme
  • Report in English or German
  • On request a retest of your fixes and an updated report
From the field

An attack path from our projects

Anonymised attack paths from our projects, step by step, and what helped against them.

Cloud security test

From a public bucket to the cloud account

Starting point: only the company name, no access.

  1. Public bucket

    A storage bucket with build artefacts could be read without authentication.

  2. Key in the artefact

    A deployment package contained a valid access key.

  3. Permissions too broad

    The key was allowed to change IAM policies, including its own.

  4. Account administrator

    Full control over the cloud account.

What helped: bucket made private, key rotated and replaced by roles, least-privilege permissions and secret scanning in the build pipeline.

FAQ

Frequently asked questions

Questions we often hear about this service.

All questions
Which cloud providers do you test?

Environments with the common providers, for example AWS, Google Cloud (GCP) and Microsoft Azure: their configuration as well as the APIs, applications and cloud instances in use.

What do you look for in a cloud environment?

Among other things, we look for misconfigurations, for tokens that grant access to resources of the environment and for exposed, unprotected APIs.

Not sure where to start?

Tell us about your environment, and we will propose a scope that fits.

Talk to us
@nullseclabs

Follow us on X for more information and current topics.