P057 Governance of mechanism firmware and rule updates
Can updates to governance firmware/rulesets be signed, rollback-protected, multi-party-controlled, and constrained so no single party can change the rules?
How updates to governance firmware/rulesets are signed, forced, rolled back or constrained, and who may change the rules.
Status
Analyzed Design discussion only (flexHEG Part III Appendix A; Part II 'Guarantee Update Process'): forced updates through limited lifetimes or licences that carry a minimum version number; approver-based or k-of-n signing of updates; approver signing keys held in a guarantee processor that serial-numbers what it signs, to prevent secret double-signing of lifetime extensions ('a topic for further research'). Nothing built or independently reviewed. Rollback protection is assumed, not shown. The clause 'constrained so no single party can change the rules' is at a lower stage: the same authors say rules about future rules are 'difficult to articulate', a baseline ruleset would be 'technically very challenging', and there is 'no clear mechanism' to ensure neutral rules.
Required updates would be implemented by having each update have a limited lifetime, tracked by an onboard clock. … If no new update has been installed before the lifetime runs out, the device locks down.
Posed by
- Petrie, Aarne, Ammann & Dalrymple (2025), Overview of Flexible Hardware-Enabled Guarantees (flexHEG Part 1):
any bugs or loopholes in the baseline ruleset could not reliably be fixed later.
(App B, Baseline Rulesets, p35, L1588)
Also raised in: Reuel, Bucknall et al. (2025), Open Problems in Technical AI Governance, compute sections; Petrie & Aarne (2025), Technical Options for Flexible Hardware-Enabled Guarantees (flexHEG Part 2); Aarne & Petrie (2025), International Security Applications of Flexible Hardware-Enabled Guarantees (flexHEG Part 3); Aarne, Fist & Withers (2024), Secure, Governable Chips (CNAS); AI Security Forum, Requests for Discussion.
Sub-questions
| ID | Sub-question | What the sources report |
|---|---|---|
| P057.1 | Is there a field-update scheme for governance firmware / guarantee logic with rollback protection and multi-party signing that passed independent review? | open |
| P057.2 | Can a non-updatable baseline layer (formal rule language) restrict the content of future updates (e.g. forbid 'phoning home')? | open |
| P057.3 | Has a hardware-held signing key with monotonic serials been shown to prevent two conflicting signed updates (secret double-signing of lifetime extensions)? | open |
| P057.4 | Can firmware update rules prevent both secret rollback and strategic delayed installation? | open |
Sub-questions not yet stated precisely enough to check
| ID | Sub-question |
|---|---|
| P057.5 | Can security patches be forced or required (expiring licences, attestation of version) when updates are voluntary or ratcheted? |
| P057.6 | Can a voting rule for ruleset changes avoid supermajority collusion and guarantee neutrality? |
| P057.7 | Can firmware for mechanisms be changed without substantial chip-designer assistance? |
| P057.8 | Can mechanism-enabled NICs/components be deployed to major data centres without the cooperation of operators or accelerator designers? |
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 P057.1: Is there a field-update scheme for governance firmware / guarantee logic with rollback protection and multi-party signing that passed independent review?
For P057.3: Has a hardware-held signing key with monotonic serials been shown to prevent two conflicting signed updates (secret double-signing of lifetime extensions)?
* Full text not reviewed; more likely to contain errors.
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