Security is a core feature of the Google Cloud Platform, but there are still steps you should take to protect your App Engine app and identify vulnerabilities.
Use the following features to ensure that your App Engine app is secure. To learn more about the Google Security Model and the available steps that you can take to secure your GCP projects, see Google Cloud Platform Security.
Use HTTPS requests to access to your App Engine app securely. Depending on how your app is configured, you have the following options:
Simply use the
httpsURL prefix to send HTTPS request to the
defaultservice of your GCP project, for example:
To target specific resources in your App Engine app, you use the
-dot-syntax to separate each resource you want to target, for example:
Tip: You convert an HTTP URL to HTTPS by simply replacing the periods between each resource with
-dot-, for example:
For more information about HTTPS URLs and targeting resources, see How Requests are Routed.
- Custom domains
To send HTTPS requests with your custom domain, you can use the managed SSL certificates that are provisioned by App Engine. For more information, see Securing Custom Domains with SSL.
Identity and access management
You can set access control using Identity and Access Management (IAM) roles at the GCP project level. Assign a role to a GCP project member or service account to determine the level of access to your GCP project and its resources. For details see, Access Control.
App Engine firewall
The App Engine firewall enables you to control access to your App Engine app through a set of rules that can either allow or deny requests from the specified ranges of IP addresses. You are not billed for traffic or bandwidth that is blocked by the firewall. Create a firewall to:
- Allow only traffic from within a specific network
- Ensure that only a certain range of IP addresses from specific networks can access your app. For example, create rules to allow only the range of IP addresses from within your company's private network during your app's testing phase. You can then create and modify your firewall rules to control the scope of access throughout your release process, allowing only certain organizations, either within your company or externally, to access your app as it makes its way to public availability.
- Allow only traffic from a specific service
- Ensure that all the traffic to your App Engine app is first proxied through a specific service. For example, if you use a third-party Web Application Firewall (WAF) to proxy requests directed at your app, you can create firewall rules to deny all requests except those that are forwarded from your WAF.
- Block abusive IP addresses
- While Google Cloud Platform has many mechanisms in place to prevent attacks, you can use the App Engine firewall to block traffic to your app from IP addresses that present malicious intent or shield your app from denial of service attacks and similar forms of abuse. You can blacklist IP addresses or subnetworks, so that requests routed from those addresses and subnetworks are denied before it reaches your App Engine app.
For details about creating rules and configuring your firewall, see Controlling App Access with Firewalls.
The Google Cloud Security Scanner discovers vulnerabilities by crawling your App Engine app, following all that links within the scope of your starting URLs, and attempting to exercise as many user inputs and event handlers as possible.
In order to use the security scanner, you must be an owner of the GCP project. For more information on assigning roles, see Granting Project Access.
You can run security scans from the Google Cloud Platform Console to identify security vulnerabilities in your App Engine app. For details about running the Security Scanner, see the Security Scanner Quickstart.