Cloud Security Pentest Readiness Check

Fifteen yes/no questions that measure how ready your cloud environment (AWS, GCP, Azure) is for configuration and IAM security testing.

  • 15 questions
  • ± 6 minutes
  1. 1Details
  2. 2
  3. 3
Before you start

Before you start

Four short fields so we can send you the result and follow up if you wish.

The result summary is sent to this address.

By continuing you agree that these details are used to send your result and to follow up, per our Privacy Policy.

15 questions · ± 6 minutes

What this questionnaire covers

Questions are grouped by area. Open any area to see its questions before you start.

How the score is read

The score is the percentage of yes answers across all questions, mapped to one of these three levels.

0–39%

Not Test-ready

Basic cloud governance and configuration are not ready. Tidy the account inventory, IAM, and public storage exposure first.

40–74%

Partially Ready

Your cloud environment is ready to be tested with some caveats. Complete the lowest-scoring areas before testing begins.

75–100%

Test-ready

Your cloud environment is ready for effective security testing. Next: agree the scope and secure any required provider authorisation.

Cloud scope and governance5 questions
  1. Is the inventory of accounts/subscriptions, services, and cloud assets (compute, storage, database) complete?
  2. Does the organisation understand the security boundary between the cloud provider and the customer (shared responsibility model)?
  3. Has authorisation for cloud security testing been obtained from the provider where their policy requires it?
  4. Is a separate account structure per environment (production, staging, development) in place?
  5. Is a cloud security configuration baseline (CIS Benchmark) established as a reference?
IAM and configuration5 questions
  1. Does cloud IAM access follow least privilege and get reviewed periodically?
  2. Is the root/primary admin account protected by MFA and rarely used for daily operations?
  3. Are public buckets/storage reviewed to ensure no sensitive data is accidentally exposed?
  4. Are credentials and API keys managed through a secrets manager rather than embedded in code or configuration?
  5. Are cloud security groups/firewalls restricted to only the ports and sources required?
Detection and follow-up5 questions
  1. Is native cloud audit logging (CloudTrail, Cloud Audit Logs, Activity Log) enabled and centrally stored?
  2. Is configuration monitoring (CSPM) or automated alerting for risky changes active?
  3. Are backups and disaster recovery plans for cloud workloads tested periodically?
  4. Have findings from previous cloud testing been remediated and re-verified?
  5. Is every finding tracked in a central register with an owner and deadline?

Frequently asked questions

Does this include penetration testing of the cloud provider's core infrastructure?

No. Providers such as AWS, GCP and Azure prohibit testing of their core infrastructure; testing focuses on the configuration and applications you manage within the shared responsibility boundary.

What is CSPM?

Cloud Security Posture Management, a category of tools that continuously monitors cloud configuration against a baseline such as the CIS Benchmark and alerts on deviations.

Is provider authorisation needed before testing?

Each cloud provider's security testing policy differs and can change; some activities, such as simulated DDoS, generally remain prohibited across all providers. Confirm your provider's current policy before testing begins.

How long does a cloud test take?

Usually 1 to 2 weeks depending on the number of accounts, services, and cloud platforms covered.

Plan the cloud security test with our team

Cloud security testing (AWS, GCP, Azure) covering configuration, IAM and data exposure, based on the CIS Benchmark, with a free retest.