Concern 445 · Working draft · editorial review in progress
Secure enclaves as trust anchors
Secure-enclave risk is dependence on a protected hardware area whose failure could expose data thought to be shielded during processing.
Understanding the concern
A trusted execution environment, often called an enclave, aims to isolate code and data from other software on the machine. It can protect data while computations run, when ordinary storage encryption alone is not enough. But its security depends on hardware, firmware, configuration and what code is trusted inside.
An enclave is like a secure room with controlled entry. The room helps, but protection also depends on its walls, inspection and the people admitted. Vulnerabilities or incorrect assumptions can weaken the promise. Verification of the environment and timely updates matter, and the system should state which attackers or failures remain outside its protection.
An example
A service advertises protected processing without explaining which software and hardware components its guarantee depends on.
Illustrative unless identified as a documented case.
Words in plain English
- Firmware
- Software built into a device that helps control its basic operations.
Evidence and its limits
These sources describe isolation, attestation and attack limits. They do not imply every enclave is compromised or provides identical protection.
NVIDIA reference architecture · Official technical documentation
Trust and Threat Model: Deploying Proprietary Models Securely with NVIDIA Confidential Computing ↗ (opens in a new tab)Lists trust assumptions and exclusions for a specific architecture, including application logging, compromised trusted roles and side channels.
Internet Engineering Task Force · 2023 · Technical architecture standard
RFC 9334: Remote ATtestation procedureS Architecture ↗ (opens in a new tab)Defines evidence, verifier and appraisal roles; an authentic attestation does not establish that an AI evaluation is adequate.
Horváth and colleagues · USENIX Security 2024 · Research systematization
SoK: Neural Network Extraction Through Physical Side Channels ↗ (opens in a new tab)Examines platform-dependent attacks, assumptions and practical limits, with experimental validation on an accelerator.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
- OECD AI Principles (opens in a new tab)
framework
- NIST AI RMF (opens in a new tab)
framework
A question to discuss
What exactly is trusted, how is it verified, and what happens when a vulnerability is discovered?
Keep track of different views, what needs checking, and any next step in your own discussion notes.
Open discussion notes →Principles for the conversation
Before you finish · reflect together
Virtues and principles to consider
Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.
Dignity
Dignity means recognizing each person's worth regardless of usefulness, status, or a system's score. People deserve respect and a voice in matters that affect them.
Explain important decisions, avoid humiliating treatment, and keep room for a person's story. Do not treat a prediction as a complete account of who someone is.
Ask together: Does this use treat each person as someone whose experience matters?
Trustworthiness
Trustworthiness means giving people good reasons to rely on you. It grows when promises, actions, and evidence line up. With AI, a friendly voice or a famous brand is not enough: people need to know what was checked and what could still go wrong.
In practice, keep promises small enough to test, record mistakes, and tell people when the tool's limits affect them. If a service promises human review, make sure a person really has time and authority to review it.
Ask together: What would give the people affected a sound reason to trust this use?
Stewardship
Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.
Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.
Ask together: What are we responsible for caring for over time?
Editorial ratings
These are editorial judgments from the register, not measured probabilities or predictions about your situation.
About the register and scoring →More ways to explore
Search for more writing
For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.