## **Cloud Configuration Review**

Review Cobalt methodologies for a Cloud Configuration Review.


:::info
A Cloud Configuration Review is a configuration assessment of your AWS, Azure or GCP cloud environment against established security standards, including CIS benchmarks. This assessment is focused on reviewing and evaluating potential vulnerabilities without engaging in active exploitation.

:::

We support Cloud Configuration Reviews for the following cloud environments:

* Amazon AWS
* Google Cloud Platform (GCP)
* Microsoft Azure

Cobalt conducts a configuration review of your AWS, Azure, or GCP cloud environment against established security standards, including CIS benchmarks.

The goal of this assessment is to identify misconfigurations. We will outline the potential impact, and provide recommendations for remediation. Example findings include: overly permissive IAM policies, open security groups, and unencrypted storage buckets. **This assessment is focused on reviewing and evaluating potential vulnerabilities without engaging in active exploitation.**

For Cloud Configuration Reviews, our team follows these steps:

* Target scope reconnaissance
* Component enumeration
  * Based on automated component discovery
* Automated component configuration assessment
  * Detail risks, based on Center for Internet Security (CIS) best practices
* Manual review of the identified misconfigurations
* Reporting, triaging, and retesting

In general, the cloud providers that we work with no longer need to know before we perform our audit. However, each cloud provider may have their own procedure.

For more details on the relevant procedures and policies, visit [Cloud Provider Authorization](https://docs.cobalt.io/methodologies/cloud-provider-auth) documentation.

### **Source IP Addresses**

Cloud providers may need to include IP addresses associated with pentester traffic in their [allowlist](https://cobalt-io.brainfish.ai/en-us/articles/glossary-YfTMKeZ1VM#h-allowlist). We’ll share these addresses when you create a Cloud Configuration Review.

## **Amazon AWS**

Our pentesters need access to review your AWS configurations. You should prepare:

* A dedicated AWS account for each pentester, with access to each target system.
  * Identity and Access Management (IAM) API credentials for each affected AWS account.
    * Include the following managed policies for the pentest user or role:
      * SecurityAudit
      * ViewOnlyAccess

These are the required policy Amazon Resource Names (ARN):

```
arn:aws:iam::aws:policy/SecurityAudit
arn:aws:iam::aws:policy/job-function/ViewOnlyAccess
```

If available, you should also include the architecture of your cloud environment.

### **What is covered**

An AWS Cloud Configuration Review will identify misconfigurations. **This assessment is focused on reviewing and evaluating potential vulnerabilities without engaging in active exploitation.**

Cloud Configuration Reviews meet the Security standards based on the Center for Internet Security (CIS) Benchmarks.

[AWS CIS Benchmarks](https://www.cisecurity.org/benchmark/amazon_web_services) cover IAM, Storage, Logging, Monitoring, and Networking.

Specific services that can be covered as part of the AWS configuration review include:


 1. AWS Cloudtrail
 2. AWS Cloudwatch
 3. AWS EC2
 4. AWS ELB
 5. AWS IAM
 6. AWS RDS
 7. AWS Redshift
 8. AWS Route 53
 9. AWS S3
10. AWS SES
11. AWS SNS
12. AWS SQS
13. AWS VPC

## **Google Cloud Platform (GCP)**

Our pentesters need access to review your GCP configurations. You should prepare: 

* A dedicated GCP account for each pentester, with access to each target system.
  * GCP access keys.
  * Identity and Access Management (IAM) API credentials for each affected GCP account.
    * To provide API credentials, use a (service) account with Viewer and Security Reviewer permissions.

### **What is covered**

A GCP Cloud Configuration Review will identify misconfigurations. **This assessment is focused on reviewing and evaluating potential vulnerabilities without engaging in active exploitation.**

Cloud Configuration Reviews meet the Security standards based on the Center for Internet Security (CIS) Benchmarks.

[GCP CIS Benchmarks](https://www.cisecurity.org/benchmark/google_cloud_computing_platform) address the following areas:


1. GCP Identity and Access Management
2. GCP Logging and Monitoring
3. GCP Networking
4. GCP Virtual Machines
5. GCP Storage
6. GCP Cloud SQL Database Services
7. GCP BigQuery

## **Microsoft Azure**

Our pentesters need access to review your Azure configurations. You should prepare:

* A dedicated Azure account for each pentester, with access to each target system.
  * Identity and Access Management (IAM) API credentials (read-only) for each dedicated account.

### **What is covered**

An Azure Cloud Configuration Review will identify misconfigurations. **This assessment is focused on reviewing and evaluating potential vulnerabilities without engaging in active exploitation.**

Cloud Configuration Reviews meet the Security standards based on the Center for Internet Security (CIS) Benchmarks.

[Azure CIS Benchmarks](https://www.cisecurity.org/benchmark/azure) address the following areas:


1. Identity and Access Management
2. Microsoft Defender
3. Storage Accounts
4. Database Services
5. Logging and Monitoring
6. Networking
7. Virtual Machines
8. Key Vault
9. AppService




Cloud Configuration Review Methodologies

Cobalt Methodologies Overview

Web Methodologies

API Methodologies

External Network Methodologies

Internal Network Methodologies

Mobile Methodologies

Cloud Pentest Methodology

Desktop Methodologies

AI/LLM Methodologies

Digital Risk Assessment Methodology

Secure Code Review Methodologies

Methodologies

How to get started with Cobalt

Getting Started

Risk Advisories

Assets are what we pentest

Asset Types

Create an Asset

Assets

Pentests

Overview

Asset Details

Pentest Details

Scope & Test Period

Preparation

Create a Pentest

Pentest Process

Pentest States

Coverage Checklist

Pentest Expectations

Set Up an In-House Pentest

Complete an In-House Pentest (For Pentesters)

In House Pentests

Finding States

Severity Levels

Remediate Findings

Findings

Customize Your Report

Co-branded Reports

Contents of a Pentest Report

Reports

Engagements Overview

Digital Risk Assessment

Secure Code Review

Engagements

Insights

Planning

Attack Surface Monitoring (ASM)

Attack Surface

DAST Scanner Overview

Best Practices

Integrations

Partial Scans: Reduced Scope

Scans

Sequence recorder

Targets

Target Authentication

Extra Hosts

Blackout Period

DAST Scanner

Account Overview

Account Settings

Password Best Practices

Sign In to Cobalt

Troubleshoot Sign-in Issues

User Account

Collaboration Overview

Collaborate on Pentests

Groups

Manage Pentest Collaborators

Manage Notifications

User Roles and Permissions

Collaboration

Organization Overview

Manage Users

Your Cobalt Contract

Configure SAML SSO

How to Configure SAML 2.0 for Cobalt 

SAML Migration: Update Your Configuration

SCIM Provisioning Setup Guide

Configure Organization Settings

Organization

Track Your Credits

Cobalt Credits

Cobalt PtaaS Tiers

Credits

Cobalt Integrations Overview

Troubleshooting

Create Jira tickets for Findings

Send email notifications for Findings from Outlook

Create GitLab tickets for Findings

Create GitHub tickets for Findings

HTTP Connector

Import Assets from Google Sheets

Map Cobalt Pentest Finding Severity to Jira Issue Priority

Modify Jira Issue Summary to contain Pentest Title

Create Azure DevOps Work Item for Findings

Send MS Teams notifications for Findings

How to Guides

Connect your applications

Integration Builder

Synchronize Cobalt Severity Levels with Jira

Push Cobalt Findings to Jira

Jira Cloud Integration

Jira Data Center Integration

Troubleshoot Your Jira Integration

Switching to a New Jira Instance

Integrate Jira with Cobalt

Slack

Microsoft Teams

Webhooks

DefectDojo

Kenna Security

Vanta

Carried Over Findings

Create Test Finding

Cobalt API Overview

Create a Personal Cobalt API Token

Get an Organization Token

Revoke Your Personal Cobalt API Tokens

Create or Modify an Asset

Import Findings to Google Sheets

Cobalt API

Glossary

March 2026

February 2026

January 2026

November 2025 

August 2025

July 2025

June 2025

May 2025

April 2025

March 2025

January 2025

December 2024

November 2024

October 2024

September 2024

August 2024

July 2024

June 2024

May 2024

April 2024

March 2024

January 2024

What's New

Guide

Cobalt Product Documentation

Cloud Configuration Review Methodologies

Share

Share

Cloud Configuration Review Methodologies

Share

Share