Cloud Compare / Network protection compared

Network protection compared

Firewall rules, security groups and NSGs; managed firewalls; WAF and DDoS; private access; and admin access without open ports, across Google Cloud, AWS and Azure.

All three clouds protect networks in the same layers: filters on each server, a managed firewall where traffic converges, a web application firewall in front of websites, DDoS protection on public addresses, private access to platform services, and admin access without open ports. The names differ, and so do a few important details, such as where a rule can be set once for the whole organisation.

For the network building blocks themselves, see Networking compared. For a detailed look at the web application firewall layer, starting from Google Cloud Armor, see Cloud Armor, AWS WAF and Azure WAF.

The layers at a glance

LayerGoogle CloudAWSAzure
Stateful filter on each serverVPC firewall rules and network firewall policiesSecurity groupsNetwork security groups (NSGs)
Subnet-level filterNone separate (rules apply network-wide, by target)Network ACLs (stateless)NSG associated with the subnet
Group servers by role in rulesService accounts, secure tags, network tagsSecurity group referencesApplication security groups
Organisation-wide rules no project can overrideHierarchical firewall policiesFirewall Manager security group policies; SCPs for guardrailsSecurity admin rules (Azure Virtual Network Manager)
Managed firewall (FQDN filtering, IDS/IPS)Cloud NGFW Standard / Enterprise; Secure Web ProxyAWS Network FirewallAzure Firewall (Basic, Standard, Premium)
DNS-layer filteringCloud NGFW FQDN objects; Cloud DNS response policiesRoute 53 Resolver DNS FirewallDNS security policy; Azure Firewall DNS proxy
Web application firewallCloud ArmorAWS WAFAzure WAF (Front Door, Application Gateway)
DDoS, included at no chargeInfrastructure protection; Cloud Armor Standard on load balancersShield StandardDDoS infrastructure protection
DDoS, paid tierCloud Armor EnterpriseShield AdvancedDDoS Network Protection or IP Protection
Central policy managementOrganisation and folder policies; Cloud Armor policies per projectAWS Firewall ManagerAzure Firewall Manager; Azure Policy

Filters on each server

GCP firewall rulesAWS security groupsAzure NSGs
Belongs toThe VPC networkThe VPC; attached to interfacesAssociated with subnets and/or NICs
Deny rulesYesNo (allow only)Yes
OrderPriority 0–65535, lowest number winsAll rules evaluated togetherPriority 100–4096, lowest number wins
Default inboundDeny (implied rule)DenyAllow from the VNet and load balancer; deny the rest
Default outboundAllow (implied rule)AllowAllow
StatefulYesYesYes
Pitfall to check firstThe default network's SSH/RDP rules from 0.0.0.0/0One permissive group added "temporarily"; the default groupSubnet and NIC NSGs that both have to allow
Report in these notesGet-GcpFirewallReportGet-AwsSecurityGroupReportGet-AzNsgRuleReport

Managed firewalls

Cloud NGFW (Google Cloud)AWS Network FirewallAzure Firewall
How traffic reaches itBuilt into the network fabric; no routing changes. Enterprise tier uses firewall endpoints per zoneFirewall endpoints in dedicated subnets; route tables send traffic through themDeployed in AzureFirewallSubnet; route tables (UDR) send traffic through it
Rules by domain nameStandard tier (FQDN objects)Yes (domain lists, Suricata rules)Standard and Premium (application rules, FQDN tags)
Threat intelligenceStandard tierAWS managed threat signaturesStandard and Premium
Intrusion prevention (IPS)Enterprise tierYes (stateful Suricata rules, managed groups)Premium (IDPS)
TLS inspectionEnterprise tierYesPremium
Policy objectFirewall policies (hierarchical, global, regional) with security profilesFirewall policy, rule groupsFirewall Policy (parent and child)

A notable difference: Google Cloud's basic firewall (Essentials) needs no appliance or routing at all, so there's no Google Cloud equivalent of the "hub firewall every packet must route through" until you need IPS or TLS inspection. In AWS and Azure, a managed firewall is always an extra hop you design routing around.

Web and DDoS protection

Google CloudAWSAzure
WAF serviceCloud Armor security policiesAWS WAF protection packs (web ACLs)Azure WAF policies
Attaches toBackend services of Application Load Balancers and Network Load Balancers; Cloud CDNCloudFront, ALB, API Gateway, AppSync, Cognito, App Runner, Verified Access, AmplifyFront Door, Application Gateway, Application Gateway for Containers
Managed rulesPreconfigured rules from the OWASP Core Rule SetAWS managed rule groups, Marketplace rule groupsDefault Rule Set (DRS), based on the OWASP CRS
BotsBot management with reCAPTCHABot Control; Fraud Control (account takeover, fake sign-ups)Bot Manager rule set
L7 DDoS assistanceAdaptive Protection (Enterprise)Shield Advanced automatic application-layer mitigationFront Door and WAF rate limiting; DDoS Protection for L3/L4
Paid DDoS tierCloud Armor Enterprise: Paygo or AnnualShield Advanced: about $3,000 a month per organisation, 1-year termDDoS Network Protection (per 100 public IPs) or IP Protection (per IP)

The full comparison, with features, pricing and how to move rules between them, is in Cloud Armor, AWS WAF and Azure WAF.

Private access and data exfiltration

NeedGoogle CloudAWSAzure
Platform services without public endpointsPrivate Service Connect; Private Google AccessVPC endpoints (PrivateLink)Private endpoints; public network access disabled
Stop data leaving through the provider's APIs, even with valid credentialsVPC Service Controls perimetersVPC endpoint policies plus resource-based policies and RCPs with aws:SourceVpce / aws:PrincipalOrgID conditionsNetwork security perimeter (for supported PaaS services); private endpoints with service firewalls
Block public storagePublic access prevention (org policy)S3 Block Public Access (account level)Storage accounts with blob public access disallowed (Azure Policy)

Admin access without open ports

Google CloudAWSAzure
Brokered SSH/RDPIAP TCP forwarding (allow 35.235.240.0/20 only)Session Manager (no inbound port at all); EC2 Instance Connect EndpointAzure Bastion (Developer, Basic, Standard, Premium)
Identity-based Linux loginOS LoginSession Manager with IAM; EC2 Instance ConnectMicrosoft Entra login for VMs
Time-limited port openingIAM conditions on IAP accessNot built in (use Session Manager instead)Just-in-time VM access (Defender for Servers Plan 2)
Session recordingCloud Audit Logs for IAP; no screen recordingSession Manager session logsBastion Premium session recording

Detection and visibility

NeedGoogle CloudAWSAzure
Network threat detectionSecurity Command Center (Event Threat Detection); Cloud NGFW Enterprise IPSGuardDuty (from VPC flow logs and DNS logs)Defender for Cloud; Microsoft Sentinel
Posture findings for open portsSecurity Health Analytics (OPEN_SSH_PORT, OPEN_FIREWALL)Security Hub CSPM controls; Config rules restricted-sshDefender for Cloud recommendations; Azure Policy
Flow logsVPC Flow Logs; firewall rules loggingVPC Flow Logs; Network Firewall logsVirtual network flow logs; Azure Firewall logs

A common baseline for all three

BaselineGoogle CloudAWSAzure
No SSH or RDP from the internetDelete default network rules; IAPSecurity groups; Session ManagerNSGs; Bastion or JIT
No public IPs on serversOrg policy compute.vmExternalIpAccessSCP / VPC Block Public AccessAzure Policy deny on public IPs
Managed outboundCloud NATNAT gatewayNAT Gateway
WAF on every public websiteCloud ArmorAWS WAFAzure WAF
Private platform servicesPrivate Service ConnectInterface endpointsPrivate endpoints
Flow logs on productionVPC Flow LogsVPC Flow LogsVNet flow logs

Compared as of October 2026. Service names, tiers and prices change; check the provider's documentation before deciding.