Comparison tables

Data location and residency requirements compared

Data location and residency requirements compared Each number links to the cell's source. Cells checked unless the cell shows another date.
RuleRequirementApplies toCitation
FedRAMP Rev5, SA-09(05) Processing, Storage, and Service Location1RequirementClass D: restrict information processing, information or data, and system services to U.S./U.S. territories or geographic locations where there is U.S. jurisdiction, for all federal customer data. The Class C parameters on the same page set no location value1Applies toCloud service providers holding FedRAMP Rev5 Class C or Class D certification1CitationFedRAMP Rev5 control guidance, System and Services Acquisition, SA-09(05)1
DoD Cloud Computing Security Requirements Guide, Cloud Service Provider SRG V1R7 (June 30, 2026)2RequirementData stored and processed for the department must be in a facility under exclusive U.S. legal jurisdiction. Government data not on department premises stays in the 50 states, the District of Columbia and U.S. outlying areas unless the responsible authorizing official allows otherwise. CSPs list every physical location where data could be stored. For IL4, IL5 and IL6, SA-9(5) is set to U.S./U.S. territories or locations under U.S. jurisdiction for all data, systems or services2Applies toCloud service providers and offerings serving the department (the 2026 SRG uses the name DoW)2CitationCSP SRG V1R7, section 5.2.1 and Table D-1 (FedRAMP+ parameter values for IL4 to IL6)2
CJIS Security Policy Version 6.1 (06/25/2026), SC-283RequirementCriminal justice information (CJI), encrypted or not, may be stored only in cloud environments within the physical boundaries of an APB-member country (United States, U.S. territories, Indian Tribes and Canada) and under the legal authority of an APB-member agency. Exchanges with foreign government agencies under international agreements are excepted3Applies toAgencies and other entities storing CJI in cloud environments3CitationCJIS Security Policy v6.1, SC-28 Protection of Information at Rest3
IRS Publication 1075 (Rev. 11-2021), section 2.C.7 Offshore Operations4RequirementFTI must not be received, processed, stored, accessed or transmitted to IT systems located offshore, or sent offshore for disposal. No access by employees, agents, contractors or sub-contractors outside the United States, its territories, embassies or military installations. Systems with FTI are located, operated and maintained by personnel in the United States, which rules out foreign remote maintenance, call centers and help desks4Applies toFederal, state and local agencies that receive federal tax information, and their agents, contractors and sub-contractors4CitationPublication 1075, section 2.C.74
28 CFR part 202, Access to U.S. Sensitive Personal Data and Government-Related Data by Countries of Concern or Covered Persons (effective April 8, 2025)5RequirementNot a storage-location rule: it governs covered data transactions that give a country of concern or covered person access to the data. U.S. persons may not knowingly engage in data brokerage with them, or in covered data transactions involving bulk human 'omic data or biospecimens. Vendor, employment and investment agreements with them are restricted transactions, allowed only with the CISA Security Requirements for Restricted Transactions. Storing data with a foreign cloud company that is not a covered person is not prohibited or restricted. Countries of concern: China, Cuba, Iran, North Korea, Russia and Venezuela5Applies toU.S. persons, for covered data transactions involving government-related data or bulk U.S. sensitive personal data5Citation28 CFR 202.210, 202.216, 202.301, 202.303, 202.305 (Example 9), 202.401, 202.6015

Get the data: CSV · JSON

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

Method

We read FedRAMP's Rev5 control guidance for SA-09(05) on fedramp.gov, the Cloud Service Provider SRG (V1R7, June 30, 2026) from DISA's Cloud Computing SRG package, the CJIS Security Policy Version 6.1 PDF (dated 06/25/2026) on the FBI's law enforcement site, the IRS's current Publication 1075, and 28 CFR part 202 in the eCFR. Each cell was first checked on 2026-11-13 and re-checked on 2026-11-14 against the same sources; the CJIS row was re-checked against version 6.1, whose SC-28 location rule reads the same as in version 6.0. The FBI's CJIS resource center page still blocked automated access on 2026-11-14, so we could not confirm whether a version later than 6.1 has been published. State rules are left out (see Omitted). This table explains the rules; it is not legal advice.

Omitted

What was left out, and why.

  • A row left out: No single state data-location rule was opened and confirmed in a primary source in this session.

Sources

  1. FedRAMP (U.S. General Services Administration). FedRAMP Rev5 control guidance: System and Services Acquisition, SA-09(05). Checked .
  2. Defense Information Systems Agency. Cloud Computing SRG package (June 2026): Cloud Service Provider Security Requirements Guide, Version 1, Release 7. Checked .
  3. Federal Bureau of Investigation. Criminal Justice Information Services (CJIS) Security Policy, Version 6.1 (06/25/2026). Checked .
  4. Internal Revenue Service. IRS Publication 1075 (Rev. 11-2021), Tax Information Security Guidelines for Federal, State and Local Agencies, section 2.C.7. Checked .
  5. U.S. Department of Justice. 28 CFR part 202, Access to U.S. Sensitive Personal Data and Government-Related Data by Countries of Concern or Covered Persons. Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the table where needed.