OPEN CIT 3.2 RELEASE
- Open CIT 3.2 has been released, see the Product Guide and Deployment Guide for more information or pickup the code from here.
- Open CIT 3.2 adds support VM/Container Integrity functionality, Extended Tboot support, OpenStack support for Mitaka.
Click here to learn what Open CIT is.
- Added VM/Container Integrity functionality (see Product Guide for full details)
- CIT 3.2 is now able to attest any file within the guest OS image of a virtual machine or Docker container during the VM/container power-on process.
- Added VM Privacy functionality (see Product Guide for full details)
- CIT 3.2 now supports encrypting a virtual machine image, and gating decryption keys to positively-attested hosts that meet policy requirements. This restricts sensitive information access to only those hosts that pass policy requirements using a trust attestation
- Added Extended Tboot support (see Product Guide for full details)
- CIT 3.2 uses the "tbootxm" application to extend the standard trusted boot measurements to any file on the physical server. This allows attestation of non-hypervisor servers, and carries the "chain of trust" from the TXT hardware root of trust to the application level.
- Added the Key Broker service (KMS)
- Added the Key Broker Proxy (KMS Proxy)
- Added the Trust Director
- Added the Attestation Reporting Hub
- The CIT Attestation Service now includes an automated recurring check that runs every two minutes to search for host attestations that are within 5 minutes of expiring. This process will then automatically trigger a new host attestation for all such hosts, automatically refreshing their trust status. The frequency of this check and the validity period of the attestations can be configured in the Attestation Service .properties files. By default the check will run every two minutes, and host attestations are valid for one hour.
- Using the new automatic attestation refresher service, many background attestation requests (including those performed by the OpenStack trust filter) have been changed to use existing valid host attestations rather than getting a new TPM quote. This substantially improves the performance of all such requests.
- Cryptographic hash operations have been converted from SHA1 to SHA256, except where needed to support TPM 1.2 (which only supports SHA1)
- OpenStack integration has been updated for the Mitaka release and rewritten to use the Attestation Reporting Hub. This adds a new interface for Nova and a table in the Nova database for storing attestation details. The scheduler filter now looks to the Nova database for attestation information pushed to this new table by the Attestation Reporting Hub, instead of directly requesting attestation details from the Attestation Service. See the Product Guide for additional details.
Known Issues in Release 3.2:
- Shared storage is not supported for the VM Integrity or VM Privacy functions
- VM Migration is not supported for the VM Integrity or VM Privacy functions
- Trust Policies containing files that begin with special characters cause the Trust Director to throw and error and failto save the Policy draft. This causes any files/folders selected since the most recent draft of that policy to fail to be added. THe Policy will generate and be attested by a host as normal, bt will be missing any of those files. Special characters that are normally useable in Windows filesystems still work if they are in the middle of the file/folder name. Only files/folders that begin with a special character are affected.
Downloading Open CIT
Extending Open Stack