Risk Level: Medium
Cloud Entity: Virtual Machine Instances
CloudGuard Rule ID: D9.GCP.NET.AG2.7.VMInstance.3306.TCP
Covered by Spectral: No
VMInstance where isPublic=true and nics contain-any [inboundRules contain [ destinationPort<=3306 and destinationPortTo >=3306 and protocol in ('TCP','ALL')]] should not have nics contain-any [inboundRules allowedPublicHostsForPort(3306) > 8 and inboundRules allowedPublicHostsForPort(3306) <= 32]
Configure your database to only allow access from internal networks and limited access scope.
If public interface exists, remove it and limit the access scope within the network only to applications or instances that requires access.
See https://cloud.google.com/compute/docs/networking for further reading about GCP networking and Firewall rules.
Compute Engine instances can run the public images for Linux and Windows Server that Google provides as well as private custom images that you can create or import from your existing systems. You can also deploy Docker containers, which are automatically launched on instances running the Container-Optimized OS public image.
You can choose the machine properties of your instances, such as the number of virtual CPUs and the amount of memory, by using a set of predefined machine types or by creating your own custom machine types.
- GCP CloudGuard Best Practices
- GCP CloudGuard Network Security
- GCP LGPD regulation
Updated 4 days ago