Learning path
Runtimeazure-confidential-vm
Regionspaincentral
ResultTRUSTED

Environment claims

Job
proteonext-federated-analytics-round-001
Hash
8a9cba968eb0f6e7c564c947...
Raw rows
False

Decision

The policy matches the claims. The node could release resources according to its local policy.

Module README

05 Confidential Computing

Confidential computing protects data and code during execution, not only at rest or in transit.

In PROTEONEXT it applies when a hospital or scientific node needs to run scoring, training, or inference with stronger isolation guarantees.

Conceptual pattern

  1. Syntax or the coordinator prepares a signed job.
  2. The node validates who is requesting it and what permissions they have.
  3. The confidential runtime starts on a Confidential VM or confidential container.
  4. The node verifies attestation: image, code hash, environment, and policy.
  5. Only if the evidence matches the policy are secrets or local data released.
  6. The job produces aggregates, weights, or authorized artifacts.

Azure fit

Need Azure component
Workload identity Entra ID Workload Identity / Managed Identity
Secrets and keys Key Vault / Managed HSM
Protected execution Azure Confidential VMs / confidential containers
Verification Microsoft Azure Attestation
Private network Private Link, NSG, Firewall
Audit Azure Monitor, Log Analytics, Sentinel
Governance Microsoft Purview

Run simulation

From Desarrollo:

python .\05_confidential_computing\simular_attestation.py

The simulation does not use Azure. It only explains the logic of an attestation decision.