Urgent.News

What's breaking now, across thousands of outlets.

Tech

Seven checks: verifying an AWS Nitro attestation in the browser

My server says an enclave scored this borrower. The verify page checks that claim itself, against AWS's signature and Solana, without trusting my server. Seven checks, and where the obvious code would have been wrong. I'm building TEE Income Oracle . It reads a borrower's bank statement inside a sealed-off part of an AWS server, works out a credit tier (A, B or C), signs it, and writes it to…

An AWS Nitro enclave is a secure, isolated environment within an AWS server that cannot be accessed or inspected, including by the operator. The enclave can execute code and produce a signed attestation document, which contains information about the code that booted and the key used for signing. This document is verified through seven checks performed by a TypeScript library running in a user's browser.

The seven checks are:

1. Signed by AWS Nitro hardware: Confirm that the signature is valid and the certificate chain ends with AWS's root certificate.

2. Marlin's published base image, not debug mode: Verify that the Platform Configuration Registers (PCRs) 0-2 match the published values from Marlin, a service that provides Nitro enclaves. Debug mode zeroes out these PCRs, so this check ensures the enclave is in production mode.

3. Runs our published code: Check that PCR16 matches the Compose file from the published release tag, ensuring the enclave is running the intended code.

4. Image ID matches the registry: Confirm that the four PCRs give the exact image ID recorded in the registry.

5. Enclave key = on-chain attester: Verify that the enclave's key matches the key listed in the registry as the signer for tiers.

6. Same document the registry recorded: Confirm that the document's hash matches the hash stored on the Solana blockchain.

7. Entry is active: Ensure the registry entry is still active and for the same type of proof as the tier.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The Better You Get at React Native, the More You Need to Understand Native

When I started working with React Native, one of the biggest attractions was simple: Write once, run on both iOS and Android. And yes, React Native gives us a great way to share code across platforms.

  • Proficient React Native developers need deeper native knowledge
  • Real-world apps hit OS limits beyond React Native capabilities
  • Transition from "write once, run everywhere" to platform-specific adaptation

More from Wednesday 4 November →