Alibaba Cloud
AWS
Google Cloud
Microsoft AzureOverview
Overview
Cyscale looks for buckets that are accessible from functions with HTTP triggers that allow unauthenticated traffic. Most FaaS services have mechanisms to enforce authentication at the service level
Remediation guidance
Depending on the provider and service that you use, check out the following resources:
Alibaba
- You can modify settings of the HTTP trigger based on your business requirements, including the Authentication and Request Method parameters. For more information, see Update the configurations of a trigger
AWS
- You can control access to your Lambda function URLs using the AuthType parameter combined with resource-based policies attached to your specific function. For more information, see Security and auth model for Lambda function URLs
Azure
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.
Azure
SERVICE-WIDE (RECOMMENDED when many resources are affected): Assign Azure Policy initiatives at management group/subscription scope and trigger remediation tasks.
az policy assignment create --name <assignment-name> --scope /subscriptions/<subscription-id> --policy-set-definition <initiative-id>
az policy remediation create --name <remediation-name> --policy-assignment <assignment-id>
ASSET-LEVEL: Apply the resource-specific remediation steps above to the listed non-compliant resources.
PREVENTIVE: Embed Azure Policy checks into landing zones and IaC workflows to block or auto-remediate drift.
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
- Azure Policy overview: https://learn.microsoft.com/en-us/azure/governance/policy/overview
- Azure Policy remediation: https://learn.microsoft.com/en-us/azure/governance/policy/how-to/remediate-resources
- Azure Policy initiative structure: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/initiative-definition-structure
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
- Azure: assign policy initiatives at management group/subscription scope and run remediation tasks.
az policy assignment create --name <assignment-name> --scope /subscriptions/<subscription-id> --policy-set-definition <initiative-id>
az policy remediation create --name <remediation-name> --policy-assignment <assignment-id>
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 accessible from functions with http trigger unauthenticated
Connectors
Covered asset types
Expected check: eq []
{
accessibleBucketsFromAWSFunctions {...AssetFragment}
}Google Cloud Buckets accessible from functions with http trigger unauthenticated
Connectors
Covered asset types
Expected check: eq []
{
accessibleBucketsFromGCPFunctions {...AssetFragment}
}Azure Blob Containers accessible from functions with http trigger unauthenticated
Connectors
Covered asset types
Expected check: eq []
{
accessibleBlobContainersFromAzureFunctions {...AssetFragment}
}Alibaba Buckets accessible from functions with http trigger unauthenticated and system policy
Connectors
Covered asset types
Expected check: eq []
{
accessibleBucketsFromAlibabaFunctionsWithSystemPolicy {...AssetFragment}
}Alibaba Buckets accessible from functions with http trigger unauthenticated and custom policy
Connectors
Covered asset types
Expected check: eq []
{
accessibleBucketsFromAlibabaFunctionsWithCustomPolicy {...AssetFragment}
}
