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
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 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}
}
