Skip to main content

A tool for AWS security assessments

Project description

Kite - Cloud Security Assessments

Kite is a tool designed to help perform AWS security assessments efficiently. It provides a suite of commands to analyze and assess security configurations and best practices. The checks align closely with the security pillar of the AWS Well-Architected framework.

Installation

pip install hyperscale-kite

Usage

Run the help command to get an overview of the available commands:

kite --help

kite works by assuming a role in each target account in order to check AWS configuration. A CloudFormation template with the required permissions is available to help setting this up. This can be deployed as a regular CloudFormation stack, or as a stack set to deploy across multiple accounts using AWS Organizations.

Deploying the Assessment Role

Single Account Deployment

To deploy the assessment role in a single account:

# Download the template
curl -O https://raw.githubusercontent.com/hyperscale-consulting/kite/refs/heads/main/permissions/kite-assessment-role.yaml

# Deploy the stack
aws cloudformation deploy \
    --template-file kite-assessment-role.yaml \
    --stack-name kite-assessment-role \
    --capabilities CAPABILITY_NAMED_IAM \
    --parameter-overrides \
        Assessor="arn:aws:sts::<ASSESSOR-ACCOUNT-ID>:assumed-role/<ROLE-NAME>/<USER>" \
        ExternalId="<EXTERNAL-ID>" \
        AssessmentEnd="2025-12-31T23:59:59Z"

Replace:

  • <ASSESSOR-ACCOUNT-ID> with the AWS account ID of the assessor
  • <ROLE-NAME> with the name of the role the assessor will use
  • <USER> with the username or session name of the assessor
  • <EXTERNAL-ID> with a unique identifier for this assessment
  • The AssessmentEnd date with when the assessment should end

Multi-Account Deployment using Stack Sets

You can easily deploy the template across the entire AWS Organization - just remember you need to deploy to the management account separately using the instruction above.

To deploy the assessment role across multiple accounts using AWS Organizations:

# Download the template
curl -O https://raw.githubusercontent.com/hyperscale-consulting/kite/refs/heads/main/permissions/kite-assessment-role.yaml

# Create the stack set
aws cloudformation create-stack-set \
    --stack-set-name kite-assessment-role \
    --template-body file://kite-assessment-role.yaml \
    --capabilities CAPABILITY_NAMED_IAM \
    --permission-model service-managed \
    --auto-deployment Enabled=true,RetainStacksOnAccountRemoval=false \
    --parameters \
        ParameterKey=Assessor,ParameterValue="arn:aws:sts::<ASSESSOR-ACCOUNT-ID>:assumed-role/<ROLE-NAME>/<USER>" \
        ParameterKey=ExternalId,ParameterValue="<EXTERNAL-ID>" \
        ParameterKey=AssessmentEnd,ParameterValue="2025-12-31T23:59:59Z"

# Create stack instances (deploy to accounts)
aws cloudformation create-stack-instances \
    --stack-set-name kite-assessment-role \
    --accounts <ACCOUNT-ID-1> <ACCOUNT-ID-2> \
    --regions <REGION> \
    --operation-preferences FailureToleranceCount=0,MaxConcurrentCount=1

# Alternatively, deploy to all accounts in the organization
aws cloudformation create-stack-instances \
    --stack-set-name kite-assessment-role \
    --deployment-targets OrganizationalUnitIds=<OU-ID> \
    --regions <REGION> \
    --operation-preferences FailureToleranceCount=0,MaxConcurrentCount=1

# Or deploy to the entire organization (including the root)
aws cloudformation create-stack-instances \
    --stack-set-name kite-assessment-role \
    --deployment-targets OrganizationalUnitIds=r-<ROOT-ID> \
    --regions <REGION> \
    --operation-preferences FailureToleranceCount=0,MaxConcurrentCount=1

Replace:

  • <ASSESSOR-ACCOUNT-ID> with the AWS account ID of the assessor
  • <ROLE-NAME> with the name of the role the assessor will use
  • <USER> with the username or session name of the assessor
  • <EXTERNAL-ID> with a unique identifier for this assessment
  • <MANAGEMENT-ACCOUNT-ID> with your AWS Organizations management account ID
  • <ACCOUNT-ID-1> <ACCOUNT-ID-2> with the target account IDs (if using specific accounts)
  • <OU-ID> with the ID of the organizational unit to deploy to (if using OUs)
  • <ROOT-ID> with your organization's root ID (if deploying to entire organization)
  • <REGION> with the AWS region to deploy to
  • The AssessmentEnd date with when the assessment should end

Note that the above create-stack-set command assumes that you are using service-managed permissions. You can also use self-managed permissions.

Once you've set up the role, you can switch to the AWS account / role from which you will be doing the assessment. The only permission this role needs is to be able to assume the assessment role in whichever account it is, for example:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowAssumeKiteAssessmentRoleInAnyAccount",
            "Effect": "Allow",
            "Action": [
                "sts:AssumeRole"
            ],
            "Resource": [
                "arn:aws:iam::*:role/KiteAssessmentRole"
            ]
        }
    ]
}

Next, configure kite:

kite configure

kite can utilise the output of Prowler checks, and the role you created above can be used with prowler. If you're using AWS Organizations you can configure prowler to get the most out of the prowler checks - take a copy of the config file and update organizations_enabled_regions to your enabled regions, and organizations_trusted_delegated_administrators to the trusted administrator accounts for your organization (e.g. your security tooling account).

Once installed and configured, you can run the prowler CLI for a standalone account:

prowler aws \
    -R arn:aws:iam::<ACCOUNT-ID>:role/KiteAssessmentRole --external-id <EXTERNAL-ID>

Or for a list of accounts in an AWS Organization:

ACCOUNT_IDS=$(kite list-accounts)
for ACCOUNT in ${(f)ACCOUNT_IDS} ; do
    prowler aws \
        -O arn:aws:iam::<MGMT-ACCOUNT-ID>:role/KiteAssessmentRole \
        -R arn:aws:iam::${ACCOUNT}:role/KiteAssessmentRole \
        --external-id <EXTERNAL-ID> \
        --config-file prowler.yaml
done

While prowler is running you can tell kite to collect the data it will need for the assessment:

kite collect

Then, when prowler has finished scanning and kite has collected the data it needs, you can start an assessment:

kite assess

After completing the assessment, you can generate a HTML report from the results:

kite report

This will create an HTML report in the <data_dir>/html/index.html directory that you can open in your web browser. The report includes:

  • Executive Summary: Overview of all checks with pass/fail statistics
  • Interactive Chart: Visual representation of assessment results
  • Detailed Results: Organized by security themes with individual check details

The report provides a professional presentation of your security assessment results that can be shared with stakeholders or used for compliance reporting.

Development

Prerequisites

  • Install uv via the official instructions
  • Configure AWS credentials (via AWS CLI or environment variables)

Running kite

  1. Clone the repo:
git clone https://github.com/hyperscale-consulting/kite
cd kite
  1. Run using uv:
uv run kite collect
uv run kite assess

Running tests and linters

uv run ruff check --fix
uv run pre-commit run --all-files
uv run pytest

Dashboard Assets

The assets used by the generated report live in the directory hyperscale/kite/dashboard/. This is the output from a react-vite-app from https://github.com/hyperscale-consulting/kite-dashboard/.

To make changes, clone that repo, make any changes and then build the app.

npm run build

and then copy the contents of the folder dist/* to hyperscale/kite/dashboard/.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

hyperscale_kite-0.5.1.tar.gz (1.7 MB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

hyperscale_kite-0.5.1-py3-none-any.whl (505.7 kB view details)

Uploaded Python 3

File details

Details for the file hyperscale_kite-0.5.1.tar.gz.

File metadata

  • Download URL: hyperscale_kite-0.5.1.tar.gz
  • Upload date:
  • Size: 1.7 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for hyperscale_kite-0.5.1.tar.gz
Algorithm Hash digest
SHA256 972a0bd45820d4d40aee56396d94a706c96a538188fde098080bbaafd1134943
MD5 b41b80cb85401a27dd8f13ef7111e624
BLAKE2b-256 07774e2f642c9c724e603aed2e4f6a0ee6afc716a2aa140db5ee7beaecd6d5d9

See more details on using hashes here.

Provenance

The following attestation bundles were made for hyperscale_kite-0.5.1.tar.gz:

Publisher: pypi-publish.yaml on hyperscale-consulting/kite

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file hyperscale_kite-0.5.1-py3-none-any.whl.

File metadata

  • Download URL: hyperscale_kite-0.5.1-py3-none-any.whl
  • Upload date:
  • Size: 505.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for hyperscale_kite-0.5.1-py3-none-any.whl
Algorithm Hash digest
SHA256 39a6826b46c6477f48975cd3d049aa6ad29e0a453cbb5730e1d231146ed3c07c
MD5 c9bdab7e3f94e62cabe150929b86e27f
BLAKE2b-256 468c3155b6678d9cd6391fe080270140d2f127fdd55e7050e90d36b2a8bb3503

See more details on using hashes here.

Provenance

The following attestation bundles were made for hyperscale_kite-0.5.1-py3-none-any.whl:

Publisher: pypi-publish.yaml on hyperscale-consulting/kite

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page