From 679362968ebcaec1cbf06ee9d5758a5453a191b5 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sat, 3 Oct 2026 19:14:07 +0200 Subject: [PATCH] Name the risk-nexus ids that now hold the Emergent knowledge findings. RISK-F-0013, RISK-F-0014 and RISK-F-0015 are filed and graded in risk-nexus. WHITEHAT-WP-0009-T03 stays waiting on emergent-security acceptance, and the workplan stays blocked. Assistant: grok Assistant-Session: 01a102a0-0003-7391-bebd-c979e4f430be --- SCOPE.md | 5 +- ...-0009-emergent-knowledge-offline-review.md | 47 ++++++++----------- 2 files changed, 22 insertions(+), 30 deletions(-) diff --git a/SCOPE.md b/SCOPE.md index e963a0d..47bc20f 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -84,8 +84,9 @@ boundary always holds. engagement. `WHITEHAT-WP-0006` owns that work and authorizes no packet. - `WHITEHAT-WP-0009` holds the offline Emergent knowledge review. The 0.2.1 record still shows WH-KNOW-001 and WH-KNOW-002. A local 0.2.3 retest did - not reproduce them. T03 stays waiting on `risk-nexus` registration and - `emergent-security` acceptance. The plan is blocked and authorizes no packet. + not reproduce them. `risk-nexus` registered RISK-F-0013, RISK-F-0014 and + RISK-F-0015. T03 stays waiting on `emergent-security` acceptance. The plan + is blocked and authorizes no packet. ## Relationships diff --git a/workplans/WHITEHAT-WP-0009-emergent-knowledge-offline-review.md b/workplans/WHITEHAT-WP-0009-emergent-knowledge-offline-review.md index 71fe3cf..32fdc69 100644 --- a/workplans/WHITEHAT-WP-0009-emergent-knowledge-offline-review.md +++ b/workplans/WHITEHAT-WP-0009-emergent-knowledge-offline-review.md @@ -62,10 +62,11 @@ state_hub_task_id: "2aeda1b6-6937-502e-a422-8792bdeb5031" Evidence: evidence/2026-10-03-emergent-021-offline-review.md and .json; retest: evidence/2026-10-03-emergent-023-offline-retest.md and .json; reproducer: tools/offline_emergent_knowledge_review.py. Task status stays -`wait`, the blocked-task state in this repo. The workplan stays `blocked`. -Delivery was sent. Registration and acceptance are dependencies below. -No new target remediation plan, institutional assent, severity or live -assurance is created. +`wait`. The workplan stays `blocked` on emergent-security acceptance. +Risk-nexus registered the delivery as RISK-F-0013, RISK-F-0014 and +RISK-F-0015 in commit 55af2d0. Those grades belong to risk-nexus. +No new target remediation plan, institutional assent or live assurance +is created. ## Artifact preservation and repository sync — 2026-10-03 @@ -105,35 +106,22 @@ check left `informed-decision` `changed`: the seal pins Whitehat recorded that and stopped. No packet was sent and the target tree was not edited. -Hub delivery already sent, with no reply in this inbox and no `RISK-F-` -record in the `risk-nexus` checkout: +Hub delivery already sent: - `risk-nexus` `9cfdad0d-d531-4387-bf58-78b025dc77a4` - `emergent-security` `ecd093c9-4e57-458e-a238-ca98659a061c` -### Required from risk-nexus +### Recorded by risk-nexus -File the reporter facts under `findings/README.md`. Allocate the ids there. -Leave severity, disclosure, cadence and every other grading field unset. -Reply with the allocated ids so this workplan can name them. Until those -ids are on this file, T03 stays `wait`. +Satisfied by `risk-nexus` commit `55af2d0`. The register owns these grades. +Whitehat records the ids and does not regrade them. All three remain `open`. +Their closure conditions still require EMERGENT-WP-0002-T07. -Reporter fields for both findings: `reported_by: whitehat-security`, -`system: emergent-security`, `environment: build`, -`fix_owner: emergent-security`, `fix_tracking: EMERGENT-WP-0002-T04`, -`date_reported: 2026-10-03`, `status: open`. Whitehat does not mark either -finding fixed. The 0.2.3 retest is later evidence on the same facts. - -- WH-KNOW-001. On 0.2.1, a loaded bundle returned unsealed card bytes under - the original digest. On 0.2.3 the same attack returned no bytes. -- WH-KNOW-002. On 0.2.1, a loaded object still served a source after - withdrawal and reseal, while a fresh object withheld it. On 0.2.3 the - loaded object returned no content and a fresh object withheld it. -- Retained Claude routing observations from the 0.2.1 report: `model-switch` - sends the next step to the package publisher, and `zones` routes its - capability question to access-engine. No unsafe effect recommendation was - observed. `risk-nexus` decides whether each observation is a finding or a - note. +| Reporter fact | Register id | Grade recorded by risk-nexus | +| --- | --- | --- | +| WH-KNOW-001 | RISK-F-0013 | medium, public, no escalation | +| WH-KNOW-002 | RISK-F-0014 | low, public, no escalation | +| Claude `model-switch` and `zones` routing | RISK-F-0015 | finding, low, public, no escalation | ### Required from emergent-security @@ -144,10 +132,13 @@ until that plan records all of the following. 1. Whether the independence limit in both evidence files meets T07's request for a whitehat-security-owned adversarial review. Both runs say they are not a separately authenticated Whitehat principal. -2. Whether WH-KNOW-001 and WH-KNOW-002 are remediated for digest +2. Whether WH-KNOW-001 (RISK-F-0013) and WH-KNOW-002 (RISK-F-0014) are + remediated for digest `60f8811c6b94b30d357a0d9e5022f2a8ea52e69b47138d3a536755f3295310b5` at commit `681144e5d4f59ef00418e7ae776e180b671f5d4d`. Their tests and this retest stay separate evidence. This retest does not close T07. + RISK-F-0015 stays open until current-release provider evidence resolves + the `model-switch` and `zones` routes. 3. Renewed provider evidence for that 0.2.3 digest before it counts toward their T05 or T07, as their `docs/evidence/2026-10-03-023-source-repin.md` already requires. Whitehat does not run providers.