When Clients Restrict Offshore Access: How MSPs Find, Document, and Enforce the Limits

The Department of Health and Human Services says the HIPAA rules allow a covered entity or business associate to use a cloud provider that stores health data on servers outside the United States, as long as a business associate agreement is in place, while noting that overseas outsourcing may increase risks and raise questions about enforcing privacy protections. Florida, by contrast, requires health care providers that use certified electronic health record technology to make sure patient information stored offsite is physically maintained in the continental United States, its territories, or Canada. And a Defense Department contract clause requires contractors that use cloud computing to provide IT services to keep government data in the United States unless the contracting officer authorizes another location.

Those three rules do not conflict. They apply to different clients, and an MSP serving all of them gets three different answers to the question of whether offshore staff may work on an account. This post covers where those restrictions come from, how to record them client by client, how to enforce them with access controls so the answer does not depend on memory, and how to answer security questionnaires accurately. It is general information and not legal advice, and any specific restriction should be confirmed with counsel and with the client.

Where Restrictions Come From

Most restrictions arrive through a client agreement, a security addendum, a business associate agreement, or a questionnaire the client's own customers or insurers require them to complete. Behind those documents sit the sources of the requirement: sector regulations, state laws, federal contract clauses, and insurance terms. The table below lists the common sources and what to check in each.

Source What it can restrict What to check
Client master agreement and security addendum Location of staff, subcontracting, data storage, and notice before any change Clauses on subcontractors, personnel, data location, and approval rights
HIPAA business associate agreement Subcontractors and offshore handling of protected health information Whether the BAA limits offshore subcontractors and what risk analysis it expects
State law Where certain records may be stored, such as Florida's rule for health care providers Which states your clients operate in and whether any has a storage or access rule
Federal contract clauses Location of government data and who may access it, for example the DFARS cloud computing clause Whether a client holds government contracts and which clauses flow down to you
Cyber and professional liability insurance Conditions on who may access systems and what controls must be in place Application answers and policy terms about third parties and personnel location
Customer security questionnaires Representations you make about staff location and access That what you wrote still matches how your team works

The HIPAA position is more permissive than many owners expect, with caveats. In its FAQ on cloud providers storing health data outside the United States, HHS answers yes, provided the covered entity or business associate enters into a business associate agreement and otherwise complies with the HIPAA Rules. It adds that the rules include no requirements specific to health information processed or stored by a cloud provider or any other business associate outside the United States, that the risks may vary greatly with geographic location, and that outsourcing storage or other services overseas may increase risks or raise questions about enforcing privacy and security protections. Entities should account for those risks in the risk analysis and risk management the Security Rule requires, and HHS gives the example that where information sits in a country with documented increased hacking attempts, those risks should be considered and appropriate technical safeguards implemented. The FAQ concerns cloud storage and says nothing specific about remote staff access, so applying it to offshore technicians is an inference you should confirm with counsel. Many healthcare clients also add their own, stricter terms in the contract, and those terms govern your work for them.

Florida shows how a state can go further. The text of Florida Statutes section 408.051 provides in subsection (3) that, in addition to the HIPAA requirements, a health care provider that uses certified electronic health record technology must ensure that all patient information stored in an offsite physical or virtual environment, including through a third-party or subcontracted computing facility or an entity providing cloud computing services, is physically maintained in the continental United States or its territories or Canada. It adds that this applies to qualified electronic health records stored using any technology that allows information to be electronically retrieved, accessed, or transmitted. The wording is about where information is physically maintained and does not expressly address remote access by overseas staff to data that remains in the United States, and readings differ, so a Florida client's counsel should confirm what they require of you.

The federal example comes from defense contracting. The Defense Federal Acquisition Regulation Supplement clause at 252.239-7010 applies when cloud computing is used to provide information technology services in performance of a contract. Under it, the contractor must maintain within the United States or outlying areas all government data not located on DoD premises unless the contracting officer gives written notice to use another location. The contractor must not access, use, or disclose government data unless the contract specifically authorizes it, must ensure its employees are subject to the same prohibitions, and must include the clause in subcontracts that involve cloud services. If a client holds defense contracts, check which clauses flow down to you before you assign anyone, and be aware that other rules on controlled information and export controls, which this post does not cover, can also affect who may touch the data.

Build an Access Register for Every Client

The most useful control is a single record of what each client allows. For every client, write down the data types they handle that carry special rules, such as health, financial, or government data. Record the contract clauses that address staff location, subcontractors, and approvals, whether a business associate agreement exists and what it says, and any insurance terms that depend on the client. Note who at the client approved offshore involvement, where there is any, and when the entry was last reviewed.

From that record, place each client in one of three tiers. The first tier is open: offshore staff may work on the account under your standard controls. The second is conditional: offshore staff may work on specific roles or systems, or only with approval, for example on ticket handling but not on systems that hold regulated data. The third is restricted: only staff in approved locations may access the account, and this tier needs technical enforcement so that it holds on a busy night shift as well as in a policy document.

Tier Who can access How to enforce it How to answer a questionnaire
Open Any technician with the right role, in any approved location Standard least-privilege roles, managed devices, MFA, and logging State where staff are based and describe the controls in place
Conditional Named roles or systems only, sometimes with client approval Separate access groups for the permitted scope, with approvals recorded Describe the permitted scope and what is excluded
Restricted Staff in approved locations only A dedicated access group, location-based sign-in rules, and separate vault and tool permissions State plainly that access is limited to approved locations and how that is enforced

Enforce the Limits With Access Controls

A restriction that depends on technicians remembering a list will fail eventually, so enforce it in the systems. The first layer is group-based access. Give restricted clients their own access group in your PSA, RMM, password manager, and, where you use it, per-client delegated administration such as Microsoft's GDAP relationships, and only add people who are permitted to work on those accounts. An offshore technician then does not see the client's tickets, devices, or credentials at all.

The second layer is location-based sign-in control. Microsoft's guidance on blocking access by location explains that the location condition in Conditional Access lets you control access to cloud apps based on a user's network location, and that it is commonly used to block access from countries or regions where traffic should not come from. You create a named location from countries or IP ranges, then a policy that includes it, with emergency access accounts excluded, and you can evaluate the policy in report-only mode before turning it on. Apply a rule like this to the group that holds access to restricted clients, so those sign-ins work only from approved countries. Location is judged from network information, so treat it as one layer alongside group membership, device compliance, and logging, and not as proof of where a person is.

Test the controls the way an auditor would. Try to sign in as an offshore technician from an unapproved location and confirm you are blocked, try to find a restricted client's records through every tool your team uses, and review the logs for access attempts. Where a gap exists, such as a shared mailbox that spans clients or a remote access tool with broad rights, fix it before the next onboarding.

Answer Questionnaires and RFPs Accurately

Security questionnaires often ask where staff are located, whether subcontractors or offshore personnel have access to client data, and how access is controlled. Answer from the access register, not from memory or from a template written two years ago. If your team includes offshore staff, say so, describe their roles and the controls that apply, and state clearly which clients or data types they cannot access. Do not write that all staff are US-based unless that is true for the specific account, and do not promise restrictions you have not enforced.

Keep answers consistent across documents. A questionnaire response, a contract schedule, and an insurance application that describe your staffing three different ways create a problem the first time someone compares them. Keep a dated copy of each answer you submit, update it when your staffing or controls change, and tell the client when something material changes if the contract requires notice. Konnect's guides on whether to tell clients about your offshore team and what happens when clients find out cover the positioning side of this conversation.

Talking to a Client About a Restriction

When a client says no offshore, find out what the restriction actually covers before you accept or push back. Ask whether it concerns where data is stored, where staff are physically located, who may have administrative access, citizenship or residency of personnel, or a specific system. Each of these has different consequences, and many restrictions are narrower than the first reaction suggests. Ask where it comes from, because a regulatory requirement and a client preference are handled differently, and ask for the wording in writing.

Then offer a clear alternative where you can. That might mean assigning US-based staff to that account, keeping offshore staff on other clients, restricting offshore work to ticket triage without access to the restricted systems, or agreeing a different coverage model for after-hours support. Be direct about the cost and coverage difference, since a restriction that removes overnight coverage for one client has a real price. Some clients will also change their position when they see your controls, but you should not count on it, and you should never route around a restriction quietly.

Where This Does Not Fit

Some accounts are simply not suited to offshore staffing. Where a regulation, a contract clause, or a client's policy requires onshore handling, the answer is to keep the account onshore, and your register should say so. A mixed approach, with offshore staff on the accounts that allow it and onshore staff on the ones that do not, works for many MSPs but needs enough onshore capacity to cover restricted clients at all hours. If most of your client base is restricted, the case for an offshore team weakens, and you should check the numbers before hiring. Finally, no technical control replaces reading the contract: location rules, subcontractor approval rights, and notice requirements all live in documents, and they change when contracts are renewed.

A Thirty-Day Review

In the first week, list your clients and mark which handle health, financial, government, or other regulated data. In the second week, read the agreement, addenda, and any business associate agreement for each marked client, and fill in the register. In the third week, assign each client a tier, create the access groups, and set up location-based sign-in rules for the restricted tier in report-only mode. In the fourth week, test them from an unapproved location, correct what fails, switch the policies on, and update your questionnaire answers so they match the register. At the end of the month, you should be able to say for any client whether offshore staff may work on the account and how you know.

📅 Book a 20-minute call: https://meet.brevo.com/konnectph

✉️ Email us: hello@konnect.ph

If you have clients in healthcare, defense, or other regulated sectors and you are not sure which accounts offshore staff can safely touch, bring your client list and the access or subcontractor clauses from your largest agreements to the call, and we will go through how to tier the accounts and set up the access controls.

About the Author

Vilbert Fermin is the founder of Konnect, a remote staffing company connecting North American and Australian businesses with top Filipino talent. With deep expertise in IT support and remote team management, Vilbert helps MSPs access skilled technical professionals without the overhead of full-time domestic IT staff. His mission is to showcase Filipino excellence while helping businesses stay protected, productive, and competitive through strategic remote staffing.

Related Resources

Next
Next

Outsourced Cold Calling for MSPs: What to Delegate and the Rules in the US, Canada, and Australia