Cloud security and posture

Find risky configuration, protect cloud networks and workloads, and keep one view across accounts.

The problem

“We need to know our cloud accounts and networks are configured safely.”

Cloud resources are created in minutes. A single permissive rule or public storage bucket can expose data before anyone reviews it.

Organisations often run several cloud accounts or providers, each with its own settings, logs and owners. Responsibility between provider and customer is rarely documented.

Proposed approach

  1. Step 1

    Inventory accounts, workloads and owners

    List every cloud account and what runs in it, and name an owner for each. Anything without an owner is the first risk to resolve.

  2. Step 2

    Turn on baseline controls and posture checks

    Use the provider's built-in services and a posture tool to flag exposed storage, open ports and over-permissive roles, and fix the highest risks first.

  3. Step 3

    Protect networks and workloads, and send findings to one place

    Apply network security and workload protection where it matters, and forward findings to the monitoring platform so cloud events appear in incident timelines.

Implementation considerations

  • Cloud providers and number of accounts in scope
  • Shared responsibility between provider, vendor and your team
  • Infrastructure-as-code pipelines where fixes should happen
  • Compliance requirements such as data residency

Expected operational benefits

  • Fewer exposed services caused by misconfiguration
  • One view of cloud risk across accounts
  • Cloud events included in incident investigations

Products that address this

Products we work with for this requirement. Details are draft summaries pending vendor confirmation.

Amazon Web Services logo

AWS Security Services

Amazon Web Services · Cloud and network

Cloud-native identity, threat detection and protection for AWS workloads

Other solutions