How to configure context-aware IP restriction policy for Google Workspace

This blog post describes the benefits of setting context-aware policy in Google Workspace and provides vital steps for configuring IP address restrictions for G Suite. SaaS Gatekeeper from AppStrict enables IP address restriction and fortifies security by conducting device and user context checks.

HOW-TO

10/13/20242 min read

grayscale photo of water lily
grayscale photo of water lily

Context-Aware Access is a security feature in Google Workspace that allows administrators to create and enforce granular access policies for their organization's apps and resources. The article describes how to set up an IP address enforcement policy using Context-Aware Access levels.

Purpose and Reason

The primary purpose of using Context-Aware Access with IP address enforcement is to enhance security by restricting access to specific apps based on the user's IP address. This feature is particularly useful for organizations that want to:

1. Ensure that sensitive data and applications are only accessed from trusted networks

2. Comply with data protection regulations that require strict access controls

3. Prevent unauthorized access from potentially compromised or unsecured networks

Setting Up IP Address Enforcement

To create and implement an IP address enforcement policy:

1. Sign in to the Google Admin console

2. Navigate to Security > Access and data control > Context-Aware Access

3. Create a new access level with an appropriate name (e.g., "IP address enforcement")

4. Add an IP subnet attribute to define allowed IP addresses or ranges

5. Assign the access level to specific apps and organizational units

Key Points

- Supported IP Addresses: The policy supports both IPv4 and IPv6 addresses, as well as CIDR block notation[1].

- Dynamic IP Addresses: To accommodate dynamic IPs, administrators must define a static IP subnet that covers the expected range[1].

- Application: The policy can be applied to various Google Workspace apps, such as Drive, Docs, Gmail, and Google Chat[1].

- User Experience: Administrators can customize messages users receive when access is blocked, including remediation options and helpful instructions[1].

Implementation Considerations

- Private IP addresses (including home networks) are not supported[1].

- It may take up to 24 hours for access level assignments to propagate for large organizational units[1].

- Administrators should be cautious when assigning access levels to avoid accidentally restricting access to the Admin console[1].

By implementing Context-Aware Access with IP address enforcement, organizations can significantly improve their security posture and maintain better control over who can access their Google Workspace resources and from where.

Citations:

[1] https://support.google.com/a/answer/12642752?hl=en

Minimize Attack Surface with SaaS Gatekeeper

AppStrict's SaaS Gatekeeper fully managed service minimizes your SaaS application's attack surface by adding multiple layers of access controls beyond MFA. Its service forces the use of VPN to access SaaS applications, providing its customers with dedicated static IP addresses to whitelist in their SaaS applications. This drastically reduces the attack surface from the billions of IP addresses that can attempt logins to only a handful of AppStrict's IP addresses. In addition, only authorized devices can connect to the VPN after authentication with digital certificates. Additional security controls, like checks on the device's location and the security hygiene of the device, can also be added.