Each cloud's transfer service is FedRAMP authorized — only inside its own cloud.
AWS DataSync is authorized within AWS. GCP Storage Transfer Service is authorized within GCP. Neither covers the path between them. That uncovered span is exactly what a cross-cloud transfer requires — and exactly where the evidence gap lives.
Authorization scope · End-to-end
Two FedRAMP-authorized boundaries. One uncovered crossing.
AWS scopeGCP scopeUncoveredAuthorized
Server General · Transfer GeneralConfirmed · GCP FedRAMP implementation guide
FedRAMP authorization is scoped to a system boundary. AWS DataSync's boundary stops at AWS. GCP Storage Transfer Service's boundary stops at GCP. The cross-cloud span lies outside both.
— 02
No combined coverage
Stacking two single-cloud authorizations does not produce a cross-cloud authorization. Each tool's evidence ends at its own boundary edge.
— 03
Where the evidence gap lives
For a regulated workload moving between clouds, the uncovered middle is precisely the segment that needs cryptographic proof of delivery — and that neither CSP-native tool provides.