Google CloudOverview
In order to maintain the highest level of security all connections to an application should be secure by default.
Rationale
Insecure HTTP connections may be subject to eavesdropping which can expose sensitive data.
Impact
All connections to App Engine will automatically be redirected to the HTTPS endpoint ensuring that all connections are secured by TLS.
Remediation guidance
Add a line to the app.yaml file controlling the application which enforces secure connections. For example:
handlers:
\- url: /.*
**secure: always**
redirect_http_response_code: 301
script: auto
Default Value
By default, both HTTP and HTTP are supported.
References
- https://cloud.google.com/appengine/docs/standard/reference/app-yaml
Google Cloud Console (Asset-Level)
- Open the affected project/resource from the finding details in Google Cloud Console.
- Navigate to the resource security/configuration settings.
- Apply the control-specific secure configuration.
- Save and re-run the check.
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.
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.
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.
App Engine Allowing Plain HTTP
Connectors
Covered asset types
Expected check: eq []
{
appEngineServices(
where: {
serviceVersions_NONE: {
urlHandlers_SOME: {
urlRegex_IN: ["/.*", ".*"]
securityLevel_IN: ["SECURE_ALWAYS"]
}
}
}
) {
...AssetFragment
}
}
