CYF-04 · Supply-chain claim reweaver
7 claims rest on 5 artifacts, and some claims rest on each other. Change a digest, a pinned version or a signer and the reweaver follows the basis chains: exactly the arguments that depend on the changed node reopen, everything else holds, and the disposition follows from what reopened.
One CVE in this release has unknown applicability. No change upgrades it, and no disposition ships past it silently — the count is named in every hold.
Backend register read
The read client is implemented and contract-tested. No transport and no workspace coordinate are configured, so no register is read from the backend on this page. The register below is a frozen fixture.
Register preview — fixture ingest, no collector
Preview12 records · 5 states
evidenced 1 · partial 3 · unverified 2 · unknown 3 · refused 3
fixture 4 · rehearsal 2 · observed 0 · imported 0 · unclassified 6
Findings register
A class says what a claim rests on: the authored synthetic corpus, a rehearsal run over synthetic inputs, an observation of a live system, or an artefact imported from its producer. Unclassified means no class is stated, so nothing behind the claim states one.
The export-after-invoke rule scores 4 true positives and 2 false positives on the 13 placeable labelled detection traces under the actor-key correlation; trace T11 carries no object field and could not be placed.
detection-corpus · detection:rule-export-after-invoke · detection:corpus/DETECTION_TRACES · 2026-10-30T00:00Z/2026-11-03T00:00Z · digest a91f3c2e
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by detection-evaluate@2 on 2026-11-03 · fixture provenance
Run: run:demo:detection:d7fe14e9
Denominator
Owner
Review
Stopping point
It stops at the authored corpus and at the T11 source gap: no trace outside these 14 labelled events was evaluated, and the unplaceable trace is drawn as a gap rather than counted clean.
Changing the provenance signer reopens exactly 2 of the 7 supply-chain claims while the 5 artifacts stay pinned by digest.
supply-chain-argument · claims:ch-signer · claims:CLAIMS · artifacts:ARTIFACTS · 2026-11-02T00:00Z/2026-11-03T00:00Z · digest b7d24e10
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by claims-requalify@1 on 2026-11-03 · fixture provenance
Run: run:demo:claims:36d6d25d
Denominator
Owner
Review
Stopping point
The result stops at the fixture's 7 claims; a supplier-published VEX analysis, which does not exist here, was not read.
The object-key correlation evaluated 13 of the 14 labelled traces; trace T11 carries no object field and could not be placed in a correlation group.
detection-corpus · detection:rule-export-after-invoke · detection:trace/T11 · 2026-10-30T00:00Z/2026-11-03T00:00Z · digest c3ea5b07
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by detection-evaluate@2 on 2026-11-03 · fixture provenance
Run: run:demo:detection:3651b719
Denominator
Owner
Review
Stopping point
It stops at the source gap in T11: the field is absent, so the unexamined trace is drawn as a gap rather than counted clean.
The VEX argument for CVE-2026-1111 was re-evaluated against 4 of the 5 supply-chain artifacts; the provenance artifact sits outside its basis and was not read.
supply-chain-argument · claims:c4 · claims:c3 · artifacts:a-prov · 2026-11-02T00:00Z/2026-11-03T00:00Z · digest d4f81a63
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by Supply-chain requalification bench on 2026-11-03 · fixture provenance
Denominator
Owner
Review
Stopping point
It stops at the provenance artifact: a-prov is not in the VEX argument's basis, so its signer state was left outside this evaluation.
The 5 required authority steps complete with the 4 participants holding the narrowed grant set.
authority-rehearsal · authority:AUTHORITY_SCENARIO · authority:proposeNarrowerArrangement/WIDE_ARRANGEMENT · 2026-11-03T00:00Z/2026-11-04T00:00Z · digest e5c19b2f
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by authority-rehearse@1 on 2026-11-03 · fixture provenance
Run: run:demo:authority:5d15aa79
Denominator
Owner
Review
Stopping point
The completion is fixture-evaluated in the rehearsal only; a live run against the deployment's own grant table would confirm it.
All 5 supply-chain artifacts are pinned by digest in the requalification fixture.
supply-chain-argument · artifacts:ARTIFACTS · claims:CHANGES · 2026-11-02T00:00Z/2026-11-03T00:00Z · digest f60d7c48
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by Supply-chain requalification bench on 2026-11-03 · fixture provenance
Denominator
Owner
Review
Stopping point
The pins are fixture-evaluated against the authored artifact list; a signed SBOM export from the release pipeline would confirm them.
MFA state for the 4 authority participants is unknown because there is no identity inventory to read.
identity-inventory · inventory:identity · authority:PARTICIPANTS · 2026-11-03T00:00Z/2026-11-04T00:00Z · digest 0a7e2d91
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by Evidence register on 2026-11-03 · fixture provenance
Denominator
Owner
Review
Stopping point
It stops at the missing instrument: no identity inventory exists, so no participant identity was assessed.
Missing instrument
Missing instrument — no identity inventory exists, so no participant identity was assessed.
The 14 labelled traces were authored, not collected; no collector exists to assess live equivalents.
collector-inventory · collector:app-audit · collector:mcp-proxy · 2026-11-03T00:00Z/2026-11-04T00:00Z · digest 1b8f4a05
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by Evidence register on 2026-11-03 · fixture provenance
Denominator
Owner
Review
Stopping point
It stops at the missing instrument: no collector exists, so neither source was read and no live event was observed.
Missing instrument
Missing instrument — no collector exists, so neither source was read and no live event was observed.
Whether the 5 authority steps are enforceable at run time is unknown: the grant table is design-only and not assessed.
grant-table · authority:grant-table · authority:AUTHORITY_SCENARIO · 2026-11-03T00:00Z/2026-11-04T00:00Z · digest 2c90e6b3
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by Authority rehearsal bench on 2026-11-03 · fixture provenance
Denominator
Owner
Review
Stopping point
It stops at the design-only grant table: the 5 steps are not assessed against a deployed table, and nothing upgrades on its own.
Missing instrument
Missing instrument — the 5 steps are not assessed against a deployed table, and nothing upgrades on its own.
Exposure assessment for natural-person subjects is refused — reason: the lab does not enrich natural persons; authority: Security Laboratory council; date: 2026-11-03.
exposure-query · exposure:natural-person · 2026-11-03T00:00Z/2026-11-04T00:00Z · digest 3da1f7c4
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by Exposure map on 2026-11-03 · fixture provenance
Denominator
Owner
Review
Stopping point
The refusal stops before any lookup: the reason and the authority are named, and no person data was collected.
Refusal
Reason
Authority
Date
The release-gate signature check is refused — reason: no signing service exists in this build; authority: Evidence register (D-15 hold); date: 2026-11-03.
signing-service · evidence:signing-service · 2026-11-03T00:00Z/2026-11-04T00:00Z · digest 4eb2a8d5
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by Evidence register on 2026-11-03 · fixture provenance
Denominator
Owner
Review
Stopping point
The refusal stops at the absent service: no signature can be produced or replayed in this build.
Refusal
Reason
Authority
Date
Autonomy level L4 is refused — reason: no person owns the decision, and the design ceiling is L2; authority: Fleet design (ceiling L2); date: 2026-11-03.
autonomy-level · authority:autonomy-L4 · 2026-11-03T00:00Z/2026-11-04T00:00Z · digest 5fc3b9e6
Digest rule: fixture-placeholder@1 — an authored eight-hex literal naming this scope; it is not a hash of the scope and no function computes it
Asserted by Authority rehearsal bench on 2026-11-03 · fixture provenance
Denominator
Owner
Review
Stopping point
The refusal is a positive result: the level is named, the ceiling that refuses it is named, and no write is rehearsed above L2.
Refusal
Reason
Authority
Date
Below the register
Vendor-claim register · SF-11.1
These are the producers' claims, recorded with their words and the scope each one names. The section has not tested these products and does not rank them. No row is an endorsement or a recommendation of a product, and no row is a finding against one: each row carries the verdict the record behind the claim supports, and the boundary that verdict was taken inside.
There is no total, no percentage and no ordering of one producer above another here. One claim is one row, the register draws no conclusion across rows, and a row's verdict is about the record behind that sentence rather than about the product.
Imported from docs/research/security-capability-frontier-2026-11-14/findings/01-ai-security-product-market.md §Claim ledger (as-of 2026-11-14). A date is the citation's own — the publication date where the source states one, otherwise the day the finding read the page — so a stored sentence is not a live page, and a page rewritten under a row does not move the row.
“Effective July 1, 2026, AI agent discovery and security posture for Microsoft Foundry agents and third-party cloud agents require a Microsoft Agent 365 license.”
Coverage boundary
What the record supports
Source
“Outcome: full visibility into AI agents and its connections, across cloud providers, SaaS platforms, and self hosted architectures — without deploying new agents.”
Coverage boundary
What the record supports
Source
“25% still lack visibility into which AI services are running in their environment”
Coverage boundary
What the record supports
Source
“Prisma AIRS AI Gateway sits inline between every AI interaction, model provider, and agentic interaction (Agent/AI App to LLMs, MCP Tool Calls, and A2A).”
Coverage boundary
What the record supports
Source
“added approximately 700 ms of average latency compared with an App-ID and decryption-only baseline.”
Coverage boundary
What the record supports
Source
“Reporting a verdict doesn't change existing scan results.”
Coverage boundary
What the record supports
Source
“runtime protection does not rely on a gateway that intercepts traffic. Instead, your application evaluates prompts and responses by sending them to the Inspection API endpoint.”
Coverage boundary
What the record supports
Source
“Gartner projected that AI cybersecurity spend will grow at an impressive 73.9% CAGR from 2024-2029”
Coverage boundary
What the record supports
Source
“AI Agent Security Guardrails 10M Requests per Year - $74,000”
Coverage boundary
What the record supports
Source
“The platform delivers adaptive protection in under 50 milliseconds across more than 100 languages”
Coverage boundary
What the record supports
Source
“Validates which of an agent's attack paths are actually exploitable, scores each one, and ships a fix ready to apply in Runtime Boundaries.”
Coverage boundary
What the record supports
Source
“See why over 10% of the Fortune 100 already trusts Noma to secure agent adoption.”
Coverage boundary
What the record supports
Source
Where this bench sits in a regime
Full registerSupply chain security, including supplier relationships.
Claim Reweaver reopens exactly the SBOM/VEX/provenance arguments a changed artifact invalidates and generates the supplier question.
The directive binds through national implementing law; transposition varies by Member State and is not tracked here.
Manufacturers must ensure vulnerabilities in products with digital elements are handled.
The claim graph makes a vulnerability statement's dependencies explicit and its re-opening after a change visible.
Main CRA duties; Art. 14 reporting has applied since 11 September 2026 and Chapter IV since 11 June 2026.
Products must be placed on the market without known exploitable vulnerabilities.
The SBOM/component/VEX claim chain is the concrete record that an absence argument rests on, with its unknown applicability preserved.
Main CRA duties; Art. 14 reporting has applied since 11 September 2026 and Chapter IV since 11 June 2026.
A regime row on a bench is a mapping, not a compliance result: the chip says how far the connection goes, and the register says where it stops.
Requalify
Release train
poly/chat:2026.11.03
sha256:9f2c1e7b4a6d…
ubuntu:24.04.1
sha256:3b7d9f1a5c3e…
poly/chat@2026.11.03.cdx.json
sha256:7e5c3a1f9d7b…
poly-chat-2026.11.03.openvex.json
sha256:1a9f7e5c3b1d…
poly-chat-2026.11.03.slsa-provenance.json
sha256:5d3f1a8c6e4b…
Disposition
Question to the supplier
For poly/chat:2026.11.03 (CVE-2026-1111): confirm whether the component is still absent from the new build, and provide the upstream OpenVEX statement or a CycloneDX component diff for the changed digest.
Computed as run:demo:claims:6c81a5fc — nothing is kept until you pin it.
Change · ch-digest
Reopened · 6
basis includes a-core
basis path · a-core
basis includes a-core
basis path · a-core
basis includes a-core
basis path · a-core
basis includes a-core
basis path · a-core
basis claim c5 reopened
basis path · a-core → c5
basis includes a-core
basis path · a-core
7 assertions
poly/chat@2026.11.03.cdx.json · basis a-sbom + a-core
poly/chat:2026.11.03 · basis a-core + a-base
poly/chat@2026.11.03.cdx.json · basis a-sbom + a-base
poly-chat-2026.11.03.openvex.json · basis a-vex + a-core + c3
poly-chat-2026.11.03.slsa-provenance.json · basis a-prov + a-core
poly-chat-2026.11.03.slsa-provenance.json · basis a-prov + c5
poly-chat-2026.11.03.openvex.json · basis a-vex + a-core
Requalification is deterministic: the same change reopens the same claims every run.