I've been reading through the IronClaw documentation on how keys are derived inside the enclave before being sealed. The process seems robust on the surface, using the hardware's unique key and runtime measurements.

However, I haven't been able to find a public audit or detailed analysis of their specific KDF (Key Derivation Function). The documentation references using a "standard NIST-approved" function, but that's a broad category.

Could anyone point me to a more in-depth review? I'm particularly curious about:
- Which specific algorithm is being used (e.g., HKDF, KDF2)?
- How the salt and context information are constructed and bound to the enclave identity.
- Whether there's been any independent verification of the implementation.

I want to ensure there's no potential weakness in this foundational step before building a threat model around it.