Overview
Overview
Cyscale looks for buckets that are accessible from virtual machines with open management ports.
Remediation guidance
Remediation strategy
- Close public management ports on VMs.
- Restrict storage access permissions of VM-attached identities.
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>
Azure
az network nsg rule update --resource-group <rg> --nsg-name <nsg> --name <rule> --source-address-prefixes <trusted-cidr>
References
- https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html
- https://cloud.google.com/firewall/docs/using-firewalls
- https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview
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.
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.
Alibaba Cloud
Use Resource Directory guardrails, account baselines, and IaC modules so the secure setting is applied consistently across environments.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
AWS Buckets accessible from VMs with open management ports
Connectors
Covered asset types
Expected check: eq []
{
accessibleBucketsFromAWSVMs {...AssetFragment}
}Google Cloud Buckets accessible from VMs with open management port
Connectors
Covered asset types
Expected check: eq []
{
accessibleBucketsFromGCPVMs {...AssetFragment}
}Azure Blob Accessible from vms with open management port
Connectors
Covered asset types
Expected check: eq []
{
accessibleBlobContainersFromAzureVMs {...AssetFragment}
}Alibaba Buckets accessible from VMs with open management port
Connectors
Covered asset types
Expected check: eq []
{
accessibleBucketsFromAlibabaVMs {...AssetFragment}
}
Alibaba Cloud
AWS
Google Cloud
Microsoft Azure