Difference between revisions of "Trusted-Location-Control"
(→Geo and Asset Tagging Solution) |
(→Geo and Asset Tagging Solution) |
||
| Line 20: | Line 20: | ||
== Geo and Asset Tagging Solution == | == Geo and Asset Tagging Solution == | ||
| − | # Provision geo tags to Compute Hosts using ‘Remote Attestation solution’ | + | # Provision geo tags to Compute Hosts using ‘Remote Attestation solution’ |
| − | # Create a tag or tags | + | # Create a tag or tags |
# Create a selection ID by selecting one or more tags | # Create a selection ID by selecting one or more tags | ||
# Provision a selection ID to the asset (ex: Compute Host). The Provisioning process will include generation of Asset Certificate and writing the SHA1 of the certificate to TPM’s NVRAM | # Provision a selection ID to the asset (ex: Compute Host). The Provisioning process will include generation of Asset Certificate and writing the SHA1 of the certificate to TPM’s NVRAM | ||
| − | # Reboot the host to complete the provisioning process, which will extend the hash to PCR 22 register of TPM. | + | # Reboot the host to complete the provisioning process, which will extend the hash to PCR 22 register of TPM. |
| − | # For more details follow the instructions in Remote Attestation Solution product guide. | + | # For more details follow the instructions in Remote Attestation Solution product guide. |
| − | # Create and Add Geo-Location/Asset-tag Policies to VM Image Properties in ‘Open Stack’ | + | # Create and Add Geo-Location/Asset-tag Policies to VM Image Properties in ‘Open Stack’ |
# The following changes have been made to Image…….screen> within open stack | # The following changes have been made to Image…….screen> within open stack | ||
| − | # NARESH to fill technical details on changes – what code was change, where is data stored and more… | + | # NARESH to fill technical details on changes – what code was change, where is data stored and more… |
| − | # Jerry to add screen shots | + | # Jerry to add screen shots |
# On Horizon dashboard Image creation/edit page(s), User to select a tag key from the pre-configured tag key list [Country, State/Province, City, Region, Classification] | # On Horizon dashboard Image creation/edit page(s), User to select a tag key from the pre-configured tag key list [Country, State/Province, City, Region, Classification] | ||
# Associate the keys with the appropriate values | # Associate the keys with the appropriate values | ||
# On image creation or editing, Horizon updates the glance database to store the list of tag key/value pairs as image properties. | # On image creation or editing, Horizon updates the glance database to store the list of tag key/value pairs as image properties. | ||
# Add Asset/Location Filter to Scheduler | # Add Asset/Location Filter to Scheduler | ||
| − | # Naresh to add technical details including API calls. | + | # Naresh to add technical details including API calls. |
# For the selected image, retrieves the list of tag key/value pairs from the glance database. | # For the selected image, retrieves the list of tag key/value pairs from the glance database. | ||
| − | # For each host, retrieves the trust and geo-tag details | + | # For each host, retrieves the trust and geo-tag details |
# Maps the image trust and geo-tag requirements with the server geo-tag and filters appropriately | # Maps the image trust and geo-tag requirements with the server geo-tag and filters appropriately | ||
# NOTE: This filter does not assign a weight to the hosts | # NOTE: This filter does not assign a weight to the hosts | ||
Revision as of 14:58, 27 August 2014
Contents
Hardware assisted Geo and Asset Tagging
While the cloud enables workloads and data to reside anywhere, users may be constrained to run their workloads and save their data in certain geographies due to regulatory requirements. This solution will extend to include trusting the location and boundary of the hardware resources, extending the current functionality of trusting the integrality of the compute platform to be free of malware and rootkits. Extensions from this solution enable associating geo and asset tags with hardware at provision time. Intel Trusted Execution Environment (TXT) and other measured launch environments (MLEs) facilitate measurement of provision time information into the Trusted Platform Module (TPM). Remote attestation services can then be used to ascertain that provision time meta-data have not been tampered. Geo and Asset tagging builds on the Trusted Compute Pools feature, covered in TrustedComputingPools
This blueprint details how geo and asset tagging can be incorporated and taken advantage of in OpenStack clouds to provide location and boundary control of workloads/OpenStack images. With Geo/Asset Tags, you can enforce policies to control placement, migration or bursting of workloads to trusted systems in specific geographical locations or boundaries, provide visibility and compliance of your workload policies to ensure tenants that of its compliance to Trust and location policies.
Principles of Operation
What is Geo/Asset Tag?
Proposed Changes
Geo and Asset Tagging Solution
- Provision geo tags to Compute Hosts using ‘Remote Attestation solution’
- Create a tag or tags
- Create a selection ID by selecting one or more tags
- Provision a selection ID to the asset (ex: Compute Host). The Provisioning process will include generation of Asset Certificate and writing the SHA1 of the certificate to TPM’s NVRAM
- Reboot the host to complete the provisioning process, which will extend the hash to PCR 22 register of TPM.
- For more details follow the instructions in Remote Attestation Solution product guide.
- Create and Add Geo-Location/Asset-tag Policies to VM Image Properties in ‘Open Stack’
- The following changes have been made to Image…….screen> within open stack
- NARESH to fill technical details on changes – what code was change, where is data stored and more…
- Jerry to add screen shots
- On Horizon dashboard Image creation/edit page(s), User to select a tag key from the pre-configured tag key list [Country, State/Province, City, Region, Classification]
- Associate the keys with the appropriate values
- On image creation or editing, Horizon updates the glance database to store the list of tag key/value pairs as image properties.
- Add Asset/Location Filter to Scheduler
- Naresh to add technical details including API calls.
- For the selected image, retrieves the list of tag key/value pairs from the glance database.
- For each host, retrieves the trust and geo-tag details
- Maps the image trust and geo-tag requirements with the server geo-tag and filters appropriately
- NOTE: This filter does not assign a weight to the hosts
- Screen shots before and after launching an instance with a image policy
Nova Aggregates and Availability Zones
The partitioning, resource reservation, and fault tolerance benefits that Nova aggregates and availability zones bring have a lot in common with geo tags. However, the main difference is that trusted tags are provision time values, and attached to the hardware resource. Re-purposing a machine is more easy via the command line with aggregates and availability zones, does not require machine reboot, but to modify trusted geo-tags more deliberate action is required, a machine reboot. The trusted geo-tag by virtue of being associated with a hardware root of trust is more valuable with respect to meeting regulatory requirements.
Further, the Attestation service could be independent of the cloud provider to increase credibility and better meet regulatory requirements. In addition, geo-tags can be verified with about 90% accuracy using software techniques using the Internet Protocol (IP) address of the device being attested.
This blueprint details how geo-tags can be incorporated and taken advantage of in OpenStack clouds.
Nova Compute Node Provisioning
During compute nodes provisioning for trust, geo-tags may also be assigned. These can be simple strings, such as, "3 rd Floor, Expo Center, Hong Kong", or complex, such as XML data providing sub-items such as GPS co-ordinates, postal address, and more, or json strings.
Dashboard
- Image properties field readily supports specifying geo and other asset tag constraints.
- Displaying VM and Image geo/asset tag affiliations. The Horizon UI for instance and Image lists could be extended to display in addition to current information, trusted and geo tags. For example, it would be logical to add a little trusted seal if a compute node is trusted, and by extension a VM running on the same compute node. A country flag would be a good geo indicator.
- Object listings Could also contain geo indicators.
Nova Scheduler Filter
Asset /Geo Tag filters should be specified. They will be very similar to todays Aggregate and Availability filters with the distinction that the data they retrieve from the Attestation service may need to be parsed. For instance, geo-tag data may be retrieved as a json string or as XML. In the case of XML,
Attestation Service
Existing Attestion services need to be upgraded to understand geo tags, support an API to retrieve them for registered hardware resources. The geo tags retrieved for hardware resource could be cached at the attestation service or even at the nova scheduler to speed scheduling decisions as long as the cached value is no older than some specifiable time window.
The simplest geo tag is a string, while more complex variants are XML and json strings. A match policy (country match, state and country match, or city, state, and country match) and a formatter to parse a given representation is required to facilitate match.
