Home›Industry News›RISC-V update adds I/O coverage to attestation, but it's still a paper
← Back to Industry News
Research

RISC-V update adds I/O coverage to attestation, but it's still a paper

ResearchRISC-V update adds I/Ocoverage toattestation, but it's…fpga.love
Illustration

An arXiv paper extends RISC-V post-update attestation from the CPU core to the I/O path. The authors—Niccolò Lentini and two co-authors—propose a scheme called PULSAR-V. For engineers working on boards and high-speed interfaces, this touches a long-neglected segment of the secure boot chain on domestic RISC-V platforms, but it remains far from usable IP or a reference implementation.

Attestation scope extends to I/O

The paper, titled "PULSAR-V: An I/O-Aware Post-Update Attestation Scheme for RISC-V," was submitted to the arXiv Cryptography and Security category on November 18, 2026, by Niccolò Lentini and two other authors, with a full text of 471 KB. The scheme's core claim is to extend the object of post-update attestation checks from the processor core to the I/O path; the official description is an added I/O-aware attestation framework. This implies that attestation flows previously covering only CPU-side integrity have an uncovered interval when peripheral configuration and data paths are involved. The paper presents a methodological framework, not synthesizable RTL or tapeout-validated IP.

Engineering deployment still far off

The source material provides only paper metadata and abstract-level information, with no process node, interface standard, performance overhead, area figures, or test platform. For board designers to judge whether the scheme is usable, they would need at minimum to know attestation latency, the degree of intrusion into the DMA path, and whether an additional root of trust is required—none of which has been disclosed. The real issue is that RISC-V secure boot discussions have mostly focused on the core and firmware, while I/O-side attestation has long lacked public schemes. PULSAR-V puts the topic on the agenda, but it is still far from entering domestic substitution selection lists pending engineering validation.

QuestionMethodFinding
Illustration
Three takeaways
  • PULSAR-V extends post-update attestation from the CPU core to the I/O path
  • The paper offers only a framework—no RTL, no tapeout, no overhead data
  • The I/O blind spot in RISC-V secure boot is beginning to be publicly discussed

What it means for us

For domestic teams working on RISC-V boards and high-speed interfaces, this paper does not yet constitute a reason to switch solutions: there is no IP, no reference implementation, and no performance figures, making it impossible to assess the impact on DMA and configuration space. The indirect impact lies in how selection questions are framed—when evaluating domestic RISC-V secure boot solutions in the future, post-update attestation of the I/O path will become an item that needs to be confirmed with vendors, while most public solutions currently do not cover it. There are no direct changes at the toolchain or supply chain level.

RISC-Vsecurity attestationI/Ofirmware update
fpga.love

Subscribe to fpga.love

Daily Briefing · Weekly Digest · Monthly Deep Dive