P064 Robustness of on-chip governance mechanisms
Are on-chip governance mechanisms robust against physical attack and hard to circumvent?
Whether on-chip governance mechanisms are robust against physical attack, confidential enough, and hard to circumvent.
Status
Analyzed Designs only. Petrie (2025) designs an off-switch built from thousands of redundant security blocks per chip and evaluates attack vectors on paper; Petrie's firmware offline licensing (2024) is an earlier design. No on-chip governance mechanism has been fabricated and tested against physical attack. The flexHEG authors mention a power-measurement prototype in one sentence, with no results published; a tamper-responsive enclosure prototype tested against probes is cited in flexHEG Part 2, but its own report has not been located.
This massively redundant architecture is designed to prevent unauthorized chip use, even against sophisticated physical attacks.
Raised in: Reuel, Bucknall et al. (2025), Open Problems in Technical AI Governance, compute sections; Aarne & Petrie (2025), International Security Applications of Flexible Hardware-Enabled Guarantees (flexHEG Part 3); Aarne, Fist & Withers (2024), Secure, Governable Chips (CNAS); Ansari (2026), Hardware-Level Governance of AI Compute: A Feasibility Taxonomy for Regulatory Compliance and Treaty Verification; Kulp et al. (2024), Hardware-Enabled Governance Mechanisms (RAND WR-A3056-1); Wasil, Reed, Miller & Barnett (2024), Verification Methods for International AI Agreements; Proofworks, Living Verification Documents.
Sub-questions
| ID | Sub-question | What the sources report |
|---|---|---|
| P064.1 | What die-area, power and unit-cost overhead does each mechanism (metering, attestation, off-switch, DPA-hardened ECDSA block) add, against a stated attack-potential rating? | open |
Sub-questions not yet stated precisely enough to check
| ID | Sub-question |
|---|---|
| P064.2 | Are on-chip export-control mechanisms viable, confidential enough, and resistant to circumvention? |
| P064.3 | Is every alternative route to compute at least as costly to an attacker as defeating the HEM, and how can that be evaluated? |
| P064.4 | How does the required hardware security of HEMs vary with the degree of on-site oversight permitted where GPUs are used? |
| P064.5 | Are current commercial chip security features robust against well-resourced adversaries, given security is tightly integrated with proprietary CPU/GPU designs and restricted access to the security module trades off attestation? |
| P064.6 | Can hardware-enabled mechanisms stay secure in an adversary's physical possession, and has any (FlexHEG, embedded off-switch) been fabricated and tested against physical attack? |
| P064.7 | What attacks apply to embedded off-switches (logic flaws, licence reuse, workload modification, glitching, FIB, side channels, supply chain, quantum)? |
Possibly relevant work found by automated search
Found by AI agents searching for this problem's sub-questions, mostly by keyword and citation in the OpenAlex scholarly database and on the web; a second AI pass reviewed each one, and we spot-checked some by hand. They seemed reasonably related, as far as one can tell from outside each paper's field. Some come from neighbouring fields, such as arms control and financial audit, and bear on the problem by analogy. Not reviewed against the status above; a paper listed here does not change that status. 928 of 1052 quotes checked word for word against the paper's text.
For P064.1: What die-area, power and unit-cost overhead does each mechanism (metering, attestation, off-switch, DPA-hardened ECDSA block) add, against a stated attack-potential rating?
For P064.6: Can hardware-enabled mechanisms stay secure in an adversary's physical possession, and has any (FlexHEG, embedded off-switch) been fabricated and tested against physical attack?
For P064.7: What attacks apply to embedded off-switches (logic flaws, licence reuse, workload modification, glitching, FIB, side channels, supply chain, quantum)?
Data
- problems.csv — one row per problem
- problem_status.csv — status, scope and evidence per problem
- problem_sources.csv — the posed-by quote and other documents per problem
- leaves.csv — all sub-questions, including those without a checkable form
- leaf_sources.csv — every source row behind each sub-question