Cyber Risks · Trail of Bits Blog

A few notes on AWS Nitro Enclaves: Images and attestation

Summary: Trail of Bits researchers examined AWS Nitro Enclaves and found that the hashes of the pre-compiled init executable and NSM driver shipped with nitro-cli 1.2.2 differ from those built from the aws-nitro-enclaves-sdk-bootstrap source, while the kernel hashes were consistent. They also found that PCR-0 is a SHA-384 hash over concatenated section data with no domain separation and no section headers, so bytes can be moved between adjacent sections without changing the measurement.

What you should know: The attestation model places both the signing key and the infrastructure with AWS, so a compromise or malicious act by AWS is game over, unlike SGX where trust is split between Intel and the cloud provider. And because the private EIF parser is not open sourced and behaves differently from the nitro-cli parser, the measurements you read from describe-eif may not be the ones the Hypervisor actually enforces.

Read the original at Trail of Bits Blog ↗