Cloud Computing Patterns, Mechanisms > Cloud Service and Storage Security Patterns > Geotagging
Geotagging (Cope, Erl)
How can the geographic location of cloud-based data and workloads be automatically communicated?
Control of data, workload locality and data sovereignty are requirements for federal and industrial compliance and regulatory issues. Without knowledge of where a cloud consumer’s workload is executed, it may not be possible to meet industrial compliance and regulatory requirements for data sovereignty.
When trusted resource pools are generated, the geolocation is supplied as part of the compliance and regulatory assurance attributes.
Assets are geotagged using TPMs and are added to trusted resource pools that contain the same security assurance levels and geolocation regions.
Burst In, Burst Out to Private Cloud, Burst Out to Public Cloud, Cloud Authentication, Cloud Balancing, Elastic Environment, Infrastructure-as-a-Service (IaaS), Isolated Trust Boundary, Multitenant Environment, Platform-as-a-Service (PaaS), Private Cloud, Public Cloud, Resilient Environment, Resource Workload Management, Secure Burst Out to Private Cloud/Public Cloud, Software-as-a-Service (SaaS)
The geolocation is configured in the TPM.