OpsCanary
securityzero trustPractitioner

Securing Your Apps with Identity-Aware Proxy: A Zero Trust Approach

5 min read Google Cloud DocsNov 22, 2026Reviewed for accuracy
Share
Practitioner — Hands-on experience recommended

In today’s security landscape, traditional perimeter defenses are no longer sufficient. Identity-Aware Proxy (IAP) addresses this by providing a central authorization layer for applications accessed via HTTPS. It enables an application-level access control model, ensuring that only authenticated and authorized users can reach your resources. This is crucial for organizations adopting a Zero Trust security framework, where trust is never assumed based on network location.

When you protect an application with IAP, it can only be accessed through the proxy by users who possess the correct Identity and Access Management (IAM) role. Upon a user's request to access an IAP-secured resource, IAP conducts authentication and authorization checks. It sends information about the protected resource to the IAP authentication server, which includes the Google Cloud project number and the request URL. If the user is not signed in, they are redirected to sign in using supported methods like Google Account or Workforce Identity Federation. This ensures that access is tightly controlled and monitored.

In production, there are several key considerations. First, ensure that you do not delete the automatically generated OAuth 2.0 credentials, as this will disrupt IAP functionality. Avoid placing a third-party CDN in front of your application, as it can cache content and inadvertently serve it to unauthenticated users. Additionally, if you experience issues with firewall rules, IAP will provide error messages in the Google Cloud console to help you troubleshoot. Lastly, if your backend resource is a Cloud Run service behind a load balancer, consider disabling the run.app URL to ensure all traffic is routed through the load balancer, maintaining security integrity.

Key takeaways

  • →Implement IAP to enforce a central authorization layer for HTTPS applications.
  • →Utilize OAuth 2.0 for secure authentication and authorization checks.
  • →Avoid using third-party CDNs to prevent serving cached content to unauthenticated users.
  • →Monitor firewall rules through the Google Cloud console for potential issues.
  • →Disable the run.app URL for Cloud Run services behind a load balancer to secure ingress.

Why it matters

Implementing IAP significantly reduces the risk of unauthorized access to your applications, aligning with a Zero Trust security model that is essential for modern enterprise environments.

Code examples

plaintext
images.yourapp.com
plaintext
gcloud compute backend-services update

When NOT to use this

If the backend resource is a Cloud Run service behind a load balancer, you can disable the run.app URL to ensure that all ingress comes in through the load balancer.

Want the complete reference?

Read official docs

Test what you just learned

Quiz questions written from this article

Take the quiz →
Linux FoundationSponsor

Industry-standard certifications built by the people behind Linux and Kubernetes. Earn the CKS — the advanced Kubernetes security specialist cert. OpsCanary readers get 30% off year-round with code OPSCANARY3.

Get CKS certified →

Get the daily digest

One email. 5 articles. Every morning.

No spam. Unsubscribe anytime.