Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
mukul975/performing-aws-account-enumeration-with-scout-suiteLinux, cloud and containers

performing-aws-account-enumeration-with-scout-suite

⁨Run the agentless, open-source ScoutSuite tool (via pip install and the `scout` CLI)⁩

v1.03 installs+3 in 7 days36.3K StarsApache-2.0synced 12 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/performing-aws-account-enumeration-with-scout-suite

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
eshdpBXXoR…jm7J6wBQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package2eb09781…3cc1ac73
2eb097818668…a53b3cc1ac738 files · ⁦14.4 KB⁩
ScanMedium3 findings
  • Executable script shipped with the skillscripts/agent.py
  • Executable script shipped with the skillscripts/process.py
  • Links to outside domains
See the full scan
Sourcegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/performing-aws-account-enumeration-with-scout-suite@54a7988

Overview

ScoutSuite is an open-source multi-cloud security auditing tool developed by NCC Group that enables comprehensive security posture assessment of AWS environments. It queries AWS APIs to gather configuration data across all services, stores results locally, and generates interactive HTML reports highlighting high-risk areas. ScoutSuite is agentless and works by analyzing how cloud resources are configured, accessed, and monitored.

When to Use

  • When conducting security assessments that involve performing aws account enumeration with scout suite
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Python 3.6+ installed
  • AWS CLI configured with appropriate IAM credentials
  • Read-only IAM permissions across target AWS services (SecurityAudit managed policy recommended)
  • pip package manager for ScoutSuite installation
  • Network access to AWS API endpoints

Installation and Setup

Install ScoutSuite

bash
pip install scoutsuite

Verify installation

bash
scout --version

Configure AWS credentials

bash
aws configure
# Or use environment variables:
export AWS_ACCESS_KEY_ID=<your-key>
export AWS_SECRET_ACCESS_KEY=<your-secret>
export AWS_DEFAULT_REGION=us-east-1

Required IAM Policy

Attach the AWS managed policy SecurityAudit and ViewOnlyAccess to the IAM user or role running ScoutSuite. For comprehensive scanning, a custom policy may be needed:

json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "acm:Describe*",
        "acm:List*",
        "cloudformation:Describe*",
        "cloudformation:Get*",
        "cloudformation:List*",
        "cloudtrail:Describe*",
        "cloudtrail:Get*",
        "cloudtrail:List*",
        "cloudwatch:Describe*",
        "cloudwatch:Get*",
        "cloudwatch:List*",
        "config:Describe*",
        "config:Get*",
        "config:List*",
        "dynamodb:Describe*",
        "dynamodb:List*",
        "ec2:Describe*",
        "ec2:Get*",
        "elasticloadbalancing:Describe*",
        "iam:Generate*",
        "iam:Get*",
        "iam:List*",
        "iam:Simulate*",
        "kms:Describe*",
        "kms:Get*",
        "kms:List*",
        "lambda:Get*",
        "lambda:List*",
        "logs:Describe*",
        "logs:Get*",
        "rds:Describe*",
        "rds:List*",
        "redshift:Describe*",
        "route53:Get*",
        "route53:List*",
        "s3:Get*",
        "s3:List*",
        "ses:Get*",
        "ses:List*",
        "sns:Get*",
        "sns:List*",
        "sqs:Get*",
        "sqs:List*",
        "ssm:Describe*",
        "ssm:Get*",
        "ssm:List*"
      ],
      "Resource": "*"
    }
  ]
}

Running ScoutSuite

Full AWS scan

bash
scout aws

Scan specific services only

bash
scout aws --services s3 iam ec2 rds

Scan specific regions

bash
scout aws --regions us-east-1 us-west-2 eu-west-1

Use an assumed role for cross-account scanning

bash
scout aws --profile target-account-profile

Exclude specific services from scan

bash
scout aws --skip iam ec2

Specify output directory

bash
scout aws --report-dir /tmp/scoutsuite-reports/

Report Analysis

ScoutSuite generates an interactive HTML report stored locally. The report includes:

  1. Dashboard: Overview of findings by severity (danger, warning, good)
  2. Service-level findings: Grouped by AWS service (IAM, S3, EC2, RDS, etc.)
  3. Rule-based checks: Each finding maps to a security best practice rule
  4. Resource inventory: Complete listing of enumerated resources

Key areas to review in the report

Service Critical Checks
IAM Root account MFA, password policy, unused credentials, overprivileged policies
S3 Public buckets, unencrypted buckets, versioning disabled, logging disabled
EC2 Security groups with 0.0.0.0/0, unencrypted EBS volumes, public IPs
RDS Public accessibility, unencrypted databases, backup retention
CloudTrail Logging disabled, log file validation, multi-region disabled
Lambda Public access, environment variable secrets, VPC configuration

Interpreting Findings

Severity Levels

  • Danger (Red): Critical security issues requiring immediate remediation (e.g., S3 buckets with public write access)
  • Warning (Orange): Moderate risk findings that should be addressed (e.g., unused IAM access keys)
  • Good (Green): Security best practices that are properly configured

Common High-Risk Findings

  1. IAM root account without MFA: The AWS root account has no multi-factor authentication enabled
  2. S3 bucket policy allows public access: Bucket policies with Principal set to "*"
  3. Security group allows unrestricted SSH: Inbound rule allowing 0.0.0.0/0 on port 22
  4. CloudTrail not enabled in all regions: Audit logging gaps allow unmonitored API activity
  5. RDS instance publicly accessible: Database endpoints reachable from the internet

Remediation Workflow

  1. Run ScoutSuite scan to establish baseline
  2. Export findings and prioritize by severity
  3. Create remediation tickets for danger and warning findings
  4. Implement fixes (update security groups, enable encryption, restrict access)
  5. Re-run ScoutSuite to verify remediation
  6. Schedule regular scans (weekly or after infrastructure changes)

Integration with CI/CD

bash
# Run ScoutSuite in CI/CD pipeline and fail on danger findings
scout aws --services s3 iam ec2 --no-browser --report-dir ./scout-report/

# Parse results programmatically
python -c "
import json
with open('./scout-report/scoutsuite-results/scoutsuite_results.json') as f:
    results = json.load(f)
    for service in results.get('services', {}):
        findings = results['services'][service].get('findings', {})
        for finding_id, finding in findings.items():
            if finding.get('flagged_items', 0) > 0 and finding.get('level') == 'danger':
                print(f'CRITICAL: {finding_id} - {finding.get(\"description\", \"\")}')
"

Multi-Cloud Capability

ScoutSuite supports multiple cloud providers using the same framework:

bash
# Azure
scout azure --cli

# GCP
scout gcp --user-account

# AWS with specific profile
scout aws --profile production

References

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesYesYes
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/agent.py
  2. MediumFile · Executable script shipped with the skillscripts/process.py
  3. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0Nov 13, 202654a79882eb09781Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login