You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Downgrade cef.js-bridge-registered and firmware.image-shipped Confirmed -> Inferred
Attribution debt from this session. Both rules emitted Confirmed on evidence
that was pattern-based, not proof-based, which is exactly what the ladder
exists to prevent.
cef.js-bridge-registered: fires on the literal string RegisterJsObject or
JavascriptObjectRepository in a PE. That proves the assembly references the
type. It does not prove the call is reached at runtime. Confidence now
Inferred. Promotion to Confirmed requires an IL call-graph trace (that IL
check is not run here).
firmware.image-shipped: fires when a file with a firmware extension has the
right magic bytes. That proves the file exists in that shape. It does not
prove the vendor updater LOADS it or that it is flashed without a signature
check. Confidence now Inferred. Invoke-TcpkFirmwarePlantProbe (K25) promotes
to Confirmed (dynamic) when the read is observed.
firmware.image-writable STAYS Confirmed. Both facts it rests on (file exists,
DACL grants non-admin write) are directly observed here. The description now
draws the line between what is proven (writable primitive) and what is
inference (unsigned flash outcome) explicitly.
Two Pester assertions updated to pin the new Confidence labels. One new
assertion in IoTCompanion.Tests pins firmware.image-shipped == Inferred for
every future run.
0 commit comments