AWS
Google CloudOverview
Overview
Cyscale looks for buckets that contain policy permissions that are too broad or unrestricted and allow a wide range of users to access the buckets.
Remediation guidance
Depending on the provider and the service you use, check out the following resources:
AWS
Google Cloud
Multiple Remediation Paths
AWS
SERVICE-WIDE (RECOMMENDED when many resources are affected): Deploy centralized guardrails and remediation using AWS Config Conformance Packs and (if applicable) AWS Organizations SCPs.
aws configservice put-organization-conformance-pack --organization-conformance-pack-name <pack-name> --template-s3-uri s3://<bucket>/<template>.yaml
ASSET-LEVEL: Apply the resource-specific remediation steps above to only the affected assets.
PREVENTIVE: Add CI/CD policy checks (CloudFormation/Terraform validation) before deployment to prevent recurrence.
Google Cloud
SERVICE-WIDE (RECOMMENDED when many resources are affected): Enforce Organization Policies at org/folder level so new resources inherit secure defaults.
gcloud org-policies set-policy policy.yaml
ASSET-LEVEL: Use the product-specific remediation steps above for only the impacted project/resources.
PREVENTIVE: Use org policy constraints/custom constraints and enforce checks in deployment pipelines.
References for Service-Wide Patterns
- AWS Config Conformance Packs: https://docs.aws.amazon.com/config/latest/developerguide/conformance-packs.html
- AWS Organizations SCP examples: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps_examples.html
- GCP Organization Policy overview: https://cloud.google.com/resource-manager/docs/organization-policy/overview
- GCP Organization policy constraints catalog: https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints
- gcloud org-policies: https://cloud.google.com/sdk/gcloud/reference/org-policies
Operational Rollout Workflow
Use this sequence to reduce risk and avoid repeated drift.
1. Contain at Service-Wide Scope First (Recommended)
- AWS: deploy/adjust organization conformance packs and policy guardrails.
aws configservice put-organization-conformance-pack --organization-conformance-pack-name <pack-name> --template-s3-uri s3://<bucket>/<template>.yaml
- Google Cloud: apply organization policy constraints at org/folder scope.
gcloud org-policies set-policy policy.yaml
2. Remediate Existing Affected Assets
- Execute the control-specific Console/CLI steps documented above for each flagged resource.
- Prioritize internet-exposed and production assets first.
3. Validate and Prevent Recurrence
- Re-scan after each remediation batch.
- Track exceptions with owner and expiry date.
- Add preventive checks in IaC/CI pipelines.
Query logic
These are the stored checks tied to this control.
AWS buckets with permissive access policy
Connectors
Covered asset types
Expected check: eq []
{
buckets(
where: {
OR: [
{ policyDocument_MATCHES: ".*arn:aws:iam::[0-9]+:root.*" }
{
bucketPolicy: {
statements_SOME: { effect: "Allow", principals_INCLUDES: "AWS|*" }
}
}
{ hasBucketACLGrant_SOME: {
OR: [
{ granteeURI: "http://acs.amazonaws.com/groups/global/AllUsers" }
{ granteeURI: "http://acs.amazonaws.com/groups/global/AuthenticatedUsers" }
]
}}]
}
) {...AssetFragment}
}Google Cloud buckets with permissive access policy
Connectors
Covered asset types
Expected check: eq []
{
buckets(
where: {
OR: [
{ iamPolicyDocument_MATCHES: ".*domain:.*" }
{
iamBindings_SOME: {
OR: [
{ members_INCLUDES: "allAuthenticatedUsers" }
{ members_INCLUDES: "allUsers" }
]
}
}
]
}
) {...AssetFragment}
}
