Skip to content

REQ 044

sergio velderrain edited this page Nov 9, 2026 · 1 revision

REQ-044: Bind evidence to current VM, attempt, and boot

Requirement

A Windows bootstrap success decision shall use only evidence bound to the current verified VM, attempt, and guest boot.

Rationale

Old VBox logs, old guest status, or a different VM must not satisfy the current run.

Fit Criterion

Reject mismatched UUIDs, attempt IDs, boot IDs, policy hashes, pre-boundary records, malformed records, and interrupted evidence. A boot witness reuses one volatile boot ID across service restarts and generates a new ID after a full guest restart. A pre-existing key of unverified volatility is unknown, not trusted as boot identity.

Verification

Planned, TEST-044; boot-ID lifetime and serial freshness require live proof.

Source

Software-Requirements-Specification

Priority

High

TestID

TEST-044

TestArtifact

Planned replay, identity, and boot-ID fixtures

CodeRef

vm/windows-labview/vnc-bootstrap.py, planned witness

Status

Planned

Clone this wiki locally