Skip ahead to the main page
Partner Huddle
Pages

Client data access controls: 4 tools for a firm WISP

Partner Huddle Editorial Team · Published · 11 min read

Client data access controls differ by tool and resource, with GitHub explicitly restricting private organizational resources through an IP allow list GitHub Docs.

Key takeaways

  • Google Account: create an app password only after 2-Step Verification is on, and revoke it if you lose a device or stop using the app Google Account Help.
  • Microsoft Entra ID: prefer location conditions for MFA with Conditional Access, and note the maximum of 50 trusted IP ranges Microsoft Learn.
  • GitHub: confirm the IP allow list covers owners and external collaborators, and note that user-installed apps using server-to-server installation tokens are not restricted by it GitHub Docs.
  • Box: check Trash search results against Viewer Uploader and edit access, because the search also returns items you own or deleted Box.

Client data access controls: the answer by tool and resource

The four tools manage distinct boundaries rather than interchangeable security layers. GitHub documentation states that you can restrict access to your organization's private resources by configuring a list that allows or denies access from specific IP addresses GitHub Docs. This control applies specifically to private organizational resources, not to every asset within a firm's digital estate. The scope is defined by the network address list you configure, which acts as a gate for those specific private items.

For firm administrators, this means the control is resource-specific. You are not applying a blanket lock to all firm data; you are managing access to the private resources of a specific organization. This distinction matters when you review which client information sits in private organizational repositories or other storage locations.

The other three tools address different control types. Google Account focuses on verification steps for app passwords, Microsoft Entra ID handles identity policies tied to licenses, and Box manages visibility of trashed items based on user permissions. Each tool's documented boundary serves a different function in protecting client information.

Comparison method and reference table from vendor help pages

The four tools address different access boundaries, so a firm review must record each vendor's documented rule separately rather than treating the controls as interchangeable. The table below lists the publisher, the specific access boundary documented in their help pages, and the stated exception or constraint for each of the four tools.

PublisherDocumented access boundary Documented exception or constraint
Google Account HelpApp password creation requires 2-Step Verification on the account The prerequisite is tied to the account's verification status
Microsoft Learn Risk-based Conditional Access policies are available with a Microsoft Entra ID P2 licenseAvailability depends on the specific tenant license tier
GitHub Docs IP allow lists restrict access to organizational resourcesRanges covering the entire address space are prohibited
Box Trash search covers items the user has Viewer Uploader access toVisibility is limited to the user's specific access permissions

The Google Account Help source defines the prerequisite for generating app passwords, noting that 2-Step Verification is required on the account. This boundary applies specifically to the creation of these credentials within the account settings.

Microsoft Learn documents that tenants with a Microsoft Entra ID P2 license can use risk-based Conditional Access policies to automatically remediate user risk. The documentation ties this specific policy capability to the presence of that license tier within the tenant.

GitHub Docs explains that you cannot add a range that covers the entire address space, such as 0.0.0.0/0 or ::/0, because it would allow access from any IP address. This constraint prevents the allow list from becoming ineffective by accepting all possible addresses.

Box states that trash search covers items in the trash that the user has Viewer Uploader access to. This rule distinguishes trash visibility from general network or authentication controls, limiting results to items within the user's documented permission scope.

Record the specific license tier and IP range constraints in your WISP review notes to ensure each tool's documented boundary is tracked accurately.

Google app access and Microsoft identity policy differ in scope

The Google Account Help documentation defines a specific prerequisite for creating app passwords. You need 2-Step Verification on your Google Account to create an app password Google Account Help. This requirement establishes a baseline security state before any app password can be generated. The documentation also notes an account state where 2-Step Verification is set up only for security keys. In that specific configuration, the account relies solely on security keys for the second factor.

When 2-Step Verification is active, some less secure apps or devices may be blocked from accessing your Google Account Google Account Help. This blocking mechanism applies to applications or devices that do not meet the security standards required by the verification method. For firm administrators, this means that legacy or less secure tools connecting to client data may lose access if the account enforces this verification. The documentation recommends that you revoke an App Password if you lose a device or no longer use an app that was authorized with it. This revocation step is a direct response to lost hardware or discontinued applications.

Microsoft Learn provides distinct guidance for identity policies. Tenants with a Microsoft Entra ID P2 license can use risk-based Conditional Access policies to automatically remediate user risk Microsoft Learn. This capability is tied specifically to the P2 license level. The documentation notes that these policies operate in addition to other options available with that license. This creates a layer of automated response to user risk that is not available to all license tiers.

Microsoft Learn also recommends location conditions as the way to configure MFA with Conditional Access. This recommendation is based on IPv6 support and other improvements Microsoft Learn. For a firm reviewing its access controls, this indicates that IP-based restrictions may need to account for IPv6 capabilities.

The scope of these controls differs significantly between the two platforms. Google Account Help focuses on the creation and revocation of app passwords within the context of 2-Step Verification. It addresses the specific state of the account's verification methods. Microsoft Learn focuses on tenant-level policies that depend on licensing and network conditions. It addresses how risk is remediated and how MFA is configured across the organization. These are distinct operational areas. One manages credential issuance for specific apps, while the other manages policy enforcement for user sessions.

GitHub network restrictions include owners but have an app exception

You can restrict access to your organization's private resources by configuring a list that allows or denies access from specific IP addresses. This IP allow list applies to users with any role or access, including enterprise and organization owners, repository administrators, and external collaborators. When setting up this list, you cannot add a range that covers the entire address space, such as 0.0.0.0/0 or ::/0, because it would allow access from any IP address. To prevent possible access interruptions, the documentation advises ensuring you have added any necessary IPv6 addresses to your IP allow list.

A specific exception exists for certain application access paths. IP allow lists don't currently restrict access when a GitHub App is installed on a user account and uses server-to-server installation tokens to access an organization or enterprise. This means that even if an organization owner or external collaborator is subject to the IP restrictions, a user-installed app utilizing these specific tokens may bypass the network boundary. For firm administrators, this distinction is critical when mapping out where client data might be accessed. You should note that the IP allow list covers human user roles comprehensively, but it does not cover every potential access vector for installed applications.

When reviewing your firm's GitHub security posture, identify which repositories contain client information and confirm that the IP allow list is configured to cover all staff roles. Verify that your list includes the necessary IPv6 addresses to avoid unexpected access issues for your team. Record the specific exception for user-installed apps using installation tokens in your WISP review notes, as this represents a documented gap in the network restriction scope. This documentation helps you understand that while the IP list is a strong control for human access, it does not block every app access path. Your review should reflect this nuance to accurately represent the security boundaries around your client data.

Box Trash visibility follows documented access permissions

When a user searches the trash, the system returns items in the trash that the user has Viewer Uploader access to, according to Box. This visibility rule is distinct from network or authentication controls discussed for other tools in this guide. The search results include 'Items I own,' 'Items I deleted,' and also other trashed items that the user has edit access to. These categories define the scope of what appears in the search results based on the user's specific permissions. The documentation does not state that these permissions apply to active files outside the trash. Firm administrators should note that access to deleted content is governed by these specific permission levels. This distinction helps operations leads understand how client data visibility is limited within the trash environment. The rules apply specifically to the trash search function as documented. No other access paths are described in this section.

Which controls fit the resources your firm actually uses

Match each documented control to the specific resource it governs before recording it in your WISP review notes. The four tools address different access boundaries, so a control that fits one resource may not apply to another. For Microsoft Entra ID, the trusted IPs feature requires Microsoft Entra ID P1 license according to Microsoft Learn. If your firm does not hold that specific license, this particular trusted IP functionality is not available under the documented licensing terms. Record the license requirement alongside the feature name so your notes reflect the actual licensing constraint rather than assuming the feature is universally accessible.

For the other three tools, the documented boundaries relate to app password verification, license-based Conditional Access policies, and trash visibility permissions. Each of these operates within its own product scope. When you review your firm's existing tools, identify which of these specific resources you actually use. If you use GitHub organizations, note the IP allow list coverage for owners and external collaborators, along with the documented exception for certain user-installed apps. If you use Box, note how Trash search visibility follows Viewer Uploader and edit access permissions. If you use Google Account, note the two-step verification requirement for app passwords and the recommendation to revoke them when devices are lost. For staff access mistakes, see Firm authentication mistakes: 6 staff access errors.

Illustrative example: recording 4 tools

Suppose a firm uses 4 tools and records 2 lines for each: the documented access boundary and any applicable exception. That gives 8 lines in the WISP review notes. Keep each line tied to the vendor help page it came from, so the record can be checked later. For a related handoff step, see Accounting Client Intake Checklist for a Clear Handoff.

Next step: For each of these tools your firm already uses, record the relevant resource, documented access boundary and applicable exception in your existing WISP review notes.

Related guides: Bank feed checks: 8 items for client reconciliation · Bank reconciliation: 8 checks before client sign-off.

FAQ: client data access across existing firm tools

How do client data access controls differ between these tools?

Google Account manages app password creation and revocation, while Microsoft Entra ID uses license-based Conditional Access policies. GitHub organizations apply IP allow lists to network access, and Box uses permission-based rules for Trash visibility. Each tool addresses a distinct access boundary rather than serving as a substitute for the others.

Which Microsoft Entra controls depend on our firm's license?

Risk-based Conditional Access policies that automatically remediate user risk are available to tenants with a Microsoft Entra ID P2 license, according to Microsoft Learn. The trusted IPs feature requires a P1 license. These licensing tiers determine which specific identity controls your firm can configure.

Does a GitHub IP allow list apply to organization owners?

Yes, the IP allow list applies to users with any role or access, including enterprise and organization owners, repository administrators, and external collaborators, as stated in GitHub Docs. This coverage ensures that high-privilege accounts remain subject to the same network restrictions as other members.

Can a user-installed GitHub App fall outside an IP allow list?

IP allow lists do not currently restrict access when a GitHub App is installed on a user account and uses server-to-server installation tokens to access an organization or enterprise, according to GitHub Docs. This exception means certain app-based workflows bypass the standard IP restrictions.

According to Box, trash search covers items the user has Viewer Uploader access to, and its results also include items the user owns or deleted. These visibility rules are distinct from network or authentication controls.

Sources