Skip to content

AI prompt · Cloud

Prompt: cloud environment security assessment plan

Prompt that builds a cloud security assessment plan (AWS, Azure, GCP): identity, network, data, logging and workloads, read-only first.

By Steven Carrier Published

Works with: Claude, other chat assistants

You are a cloud security auditor. Build the security assessment plan for the environment described below.

Cloud provider(s): {{providers}}
Organisation context: {{context}}
Authorised scope (accounts, subscriptions, projects): {{scope}}
Access granted for the engagement: {{granted_access}}
Engagement constraints: {{constraints}}

Organise the plan by area: identity and access, network, data (storage, encryption, backups), logging and detection, workloads (machines, containers, functions), secrets management, governance (account structure, policies).

For each area:
1. list the checks to carry out, with the targeted risk level (high, medium, low);
2. indicate what is done read-only and what would require an active action, to be considered only with the client's explicit agreement;
3. name the audit tools or commands suited to the provider (the provider's official tools, recognised configuration audit tools) without quoting options you are not sure of;
4. specify the permissions required and propose the read-only audit role to request from the client, following least privilege;
5. cite the relevant benchmark (provider guidance, CIS Benchmarks) without inventing control numbers.

Rules:
- start with a complete read-only phase before any active check;
- do not carry out or propose any configuration change, any reading of data contents, or any privilege escalation not provided for in the contract;
- flag checks that may incur cost or affect production;
- finish with an indicative timetable, the list of prerequisites to obtain from the client, and open questions.

Replace the highlighted variables before use.

This prompt builds the outline of a security assessment of a public cloud environment: what to check, in what order, with which permissions and tools, starting with what changes nothing. It helps prepare the technical scoping before access is granted, then organise the testers’ work.

When to use it

  • At pre-sales stage, to estimate the scope of a cloud configuration audit.
  • At kick-off, to list the permissions and access to request from the client.
  • To harmonise the approach across providers when the organisation uses several.

Fill in the variables

Variable Example
{{providers}} mainly AWS, one Azure subscription for email and directory
{{context}} software vendor of about a hundred people, containerised application, European customer data
{{scope}} three AWS accounts (production, pre-production, tooling) under one organisation; Azure subscription sub-example-prod
{{granted_access}} read-only audit role on the three accounts, access to the organisation’s audit log, no access to data
{{constraints}} no configuration changes, no active testing in production, report within three weeks

For AWS identity auditing in practice, see the AWS IAM audit cheat sheet. Reuse the items agreed in the pentest scoping checklist.

Review the output

  • Check role, policy and tool names against the provider’s official documentation: they change, and a model confuses one provider’s services with another’s.
  • Check that the proposed audit role really is read-only and does not open access to data contents.
  • Check that no active step has slipped into the read-only phase.
  • Match the control points to the benchmark version you use; do not reuse any control number without verifying it.
  • Do not paste into the prompt any client information (account identifiers, resource names, configuration extracts) that your agreement does not allow you to share with an AI service.

Sources

Related resources

  • AI prompt · Infrastructure and AD pentesting · OSINT · Cloud

    Attack surface prompt

    Prompt that analyses an asset inventory from the authorised scope (domains, IPs, services, cloud) to prioritise testing: exposure, criticality, checks.

    Published

  • Cheatsheet · Cloud

    AWS IAM audit (CLI)

    Read-only AWS IAM review with the AWS CLI: identity, users, roles, policies, access key age, MFA, credential report and Prowler pointers.

    Published

  • Cheatsheet · Cloud

    Azure / Entra ID audit (CLI)

    Read-only Azure and Entra ID review with the Azure CLI: subscriptions, RBAC roles, identities, key vaults, storage and network security groups.

    Published

BEAROPS

Need a penetration test?

BEAROPS experts test your applications, infrastructure and cloud, black box or grey box, following OWASP, NIST and ANSSI guidance.