Skip to main content

📝 Google Identity Aware Proxy (IAP) is not used to enforce access controls 🟢

  • Contextual name: 📝 Identity Aware Proxy (IAP) is not used to enforce access controls 🟢
  • ID: /ce/ca/google/iam/identity-aware-proxy
  • Located in: 📁 Google IAM

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Description​

Open File

Description​

IAP authenticates the user requests to your apps via a Google single sign in. You can then manage these users with permissions to control access. It is recommended to use both IAP permissions and firewalls to restrict this access to your apps with sensitive information.

Rationale​

IAP ensure that access to VMs is controlled by authenticating incoming requests. Access to your apps and the VMs should be restricted by firewall rules that allow only the proxy IAP IP addresses contained in the 35.235.240.0/20 subnet. Otherwise, unauthenticated requests can be made to your apps. To ensure that load balancing works correctly health checks should also be allowed.

Impact​

If firewall rules are not configured correctly, legitimate business services could be negatively impacted. It is recommended to make these changes during a time of low usage.

Audit​

From Google Cloud Console​
  1. For each of your apps that have IAP enabled go to the Cloud Console VPC network > Firewall rules.
  2. Verify that the only rules correspond to the following values:

... see more

Remediation​

Open File

Remediation​

From Google Cloud Console​

  1. Go to the Cloud Console VPC network > Firewall rules.

  2. Select the checkbox next to the following rules:

    o default-allow-http

    o default-allow-https

    o default-allow-internal

  3. Click Delete.

  4. Click Create firewall rule and set the following values:

    o Name: allow-iap-traffic

    o Targets: All instances in the network

    o Source IP ranges (press Enter after you paste each value in the box, copy each full CIDR IP address):

     ▪ IAP Proxy Addresses 35.235.240.0/20
     ▪ Google Health Check 130.211.0.0/22
     ▪ Google Health Check 35.191.0.0/16

    o Protocols and ports:

     ▪ Specified protocols and ports required for access and management of your app. For example most health check connection protocols would be covered by;
     ▪ tcp:80 (Default HTTP Health Check port)
     ▪ tcp:443 (Default HTTPS Health Check port) 
     
     Note: if you have custom ports used by your load balancers, you will need to list them here

  5. When you're finished updating values, click Create.

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS GCP v3.0.0 → 💼 3.10 Use Identity Aware Proxy (IAP) to Ensure Only Traffic From Google IP Addresses are 'Allowed' - Level 2 (Manual)1
💼 Cloudaware Framework → 💼 Secure Access43