Back to controls

Ensure KMSKeys are not exposed through publicly accessible VMs

### Overview

Category

Controls

High

Applies to

Alibaba CloudAWSGoogle CloudMicrosoft Azure

Coverage

4 queries

Asset types

1 covered

Overview

Overview

This control looks for KMSKeys that are accessible by IAM policies or roles which are attached to VMs that allow public access from the internet.

Remediation guidance

Remediation strategy

  1. Remove public management exposure from VMs.
  2. Limit KMS key access to approved identities only.

AWS

aws ec2 revoke-security-group-ingress --group-id <sg-id> --protocol tcp --port 22 --cidr 0.0.0.0/0
aws ec2 revoke-security-group-ingress --group-id <sg-id> --protocol tcp --port 3389 --cidr 0.0.0.0/0

GCP

gcloud compute firewall-rules update <rule-name> --source-ranges=<trusted-cidr>
gcloud kms keys remove-iam-policy-binding <key-name> --location <location> --keyring <keyring> --member="allUsers" --role="roles/cloudkms.cryptoKeyEncrypterDecrypter"

Azure

az network nsg rule update --resource-group <rg> --nsg-name <nsg> --name <rule> --source-address-prefixes <trusted-cidr>
az role assignment delete --assignee <principal-id> --role "Key Vault Crypto User" --scope <key-vault-or-key-scope>

References

  • https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html
  • https://cloud.google.com/kms/docs/reference/permissions-and-roles
  • https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-guide

Service-wide remediation

Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.

AWS

Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.

Google Cloud

Use organization or folder policies where available, shared project templates, logs and alerting baselines, and IaC modules so new resources inherit the secure setting.

Alibaba Cloud

Use Resource Directory guardrails, account baselines, and IaC modules so the secure setting is applied consistently across environments.

Azure

Use management group or subscription Azure Policy assignments, remediation tasks where supported, landing-zone standards, and IaC modules so drift is prevented at scale.

Operational rollout

  1. Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
  2. Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
  3. Re-scan and track approved exceptions with an owner and expiry date.

Query logic

These are the stored checks tied to this control.

AWS KMSKeys Exposed Through Vulnerable VMs

Connectors

AWS

Covered asset types

KMSKey

Expected check: eq []

vms( where: { securityGroups_SOME: { rules_SOME: { direction: "Inbound" action: "Allow" AND: [ { OR: [ { sources_INCLUDES: "cidr:0.0.0.0/0" } { sources_INCLUDES: "cidr:::/0" } ] } { destFromPort_LTE: 22, destToPort_GTE: 22 } ] } } iamRoles_SOME: { iamPolicies_SOME: { iamPolicyStatements_SOME: { effect: "Allow" } } } } ) { iamRoles { iamPolicies { iamPolicyStatements { permissions { isOwnedByIAMAssetType { includesKMSKey {...AssetFragment} } } } } } }
Google Cloud KMSKeys Exposed Through Vulnerable VMs

Connectors

Google Cloud

Covered asset types

KMSKey

Expected check: eq []

vms( where: { firewalls_SOME: { rules_SOME: { direction: "Inbound" action: "Allow" AND: [ { OR: [ { sources_INCLUDES: "cidr:0.0.0.0/0" } { sources_INCLUDES: "cidr:::/0" } ] } { destFromPort_LTE: 22, destToPort_GTE: 22 } ] } } } ) { serviceAccount { serviceAccountRoles { hasIAMPermissions { isOwnedByIAMAssetType { includesKMSKey {...AssetFragment} } } } } }
Alibaba KMSKeys Exposed Through Vulnerable VMs

Connectors

Alibaba Cloud

Covered asset types

KMSKey

Expected check: eq []

{
  alibabaKMSKeysExposedThroughVMs {...AssetFragment}
}
Azure KMSKeys Exposed Through Vulnerable VMs

Connectors

Microsoft Azure

Covered asset types

KMSKey

Expected check: eq []

{ vms( where: { networkInterfaces_SOME: { securityGroups_SOME: { rules_SOME: { direction: "Inbound" action: "Allow" AND: [ { OR: [ { sources_INCLUDES: "cidr:0.0.0.0/0" } { sources_INCLUDES: "cidr:::/0" } { sources_INCLUDES: "tag:Internet" } { sources: [] } ] } { destFromPort_LTE: 22, destToPort_GTE: 22 } ] } } } } ) { vmRoles { hasIAMPermissions { isOwnedByIAMAssetType { includesKMSKey {...AssetFragment} } } } } }
Cyscale Logo
Cyscale is an agentless cloud-native application protection platform (CNAPP) that automates the contextual analysis of cloud misconfigurations, vulnerabilities, access, and data, to provide an accurate and actionable assessment of risk.

Stay connected

Receive new blog posts and product updates from Cyscale

By clicking Subscribe, I agree to Cyscale’s Privacy Policy


© 2026 Cyscale Limited

LinkedIn icon
Twitter icon
Facebook icon
crunch base icon
angel icon