Finish WHITEHAT-WP-0009 after the acceptance dispositions were recorded.
Emergent-security commit 19e7feb accepts the scoped offline review and the two library remediations, and leaves provider evidence and the informed-decision pin with EMERGENT-WP-0002. The three Whitehat tasks are done. The open RISK-F records stay with risk-nexus. Assistant: grok Assistant-Session: 01a102a0-0003-7391-bebd-c979e4f430be
This commit is contained in:
parent
679362968e
commit
3e7f3b75f7
2 changed files with 43 additions and 37 deletions
12
SCOPE.md
12
SCOPE.md
|
|
@ -82,11 +82,13 @@ boundary always holds.
|
|||
- `-01`, `-02` and `-03` are terminal. A later live run needs a new
|
||||
engagement ID, plane admission, and the approvals required by the rules of
|
||||
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. `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.
|
||||
- `WHITEHAT-WP-0009` is finished. The 0.2.1 record shows WH-KNOW-001 and
|
||||
WH-KNOW-002. A local 0.2.3 retest did not reproduce them. `risk-nexus`
|
||||
holds open RISK-F-0013, RISK-F-0014 and RISK-F-0015. `emergent-security`
|
||||
commit `19e7feb` accepts the scoped review and the two library
|
||||
remediations, and leaves provider evidence and the `informed-decision`
|
||||
pin reconciliation in blocked EMERGENT-WP-0002. This plan authorizes no
|
||||
packet.
|
||||
|
||||
## Relationships
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ type: workplan
|
|||
title: "Offline adversarial review of Emergent knowledge release 0.2.1"
|
||||
domain: infotech
|
||||
repo: whitehat-security
|
||||
status: blocked
|
||||
status: finished
|
||||
owner: whitehat-security
|
||||
topic_slug: whitehat-security
|
||||
created: "2026-10-03"
|
||||
|
|
@ -54,19 +54,22 @@ prerequisites and mitigation limits are preserved. No target edits.
|
|||
|
||||
```task
|
||||
id: WHITEHAT-WP-0009-T03
|
||||
status: wait
|
||||
status: done
|
||||
priority: high
|
||||
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 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.
|
||||
reproducer: tools/offline_emergent_knowledge_review.py.
|
||||
Risk-nexus registered RISK-F-0013, RISK-F-0014 and RISK-F-0015 in commit
|
||||
55af2d0. Emergent-security recorded the four acceptance dispositions in
|
||||
commit 19e7feb, `docs/evidence/2026-10-03-whitehat-t03-dispositions.md`.
|
||||
That record accepts the scoped offline review and the two library
|
||||
remediations on digest `60f8811c` at `681144e5`. It leaves RISK-F-0015,
|
||||
current-release provider evidence, and the `informed-decision` pin
|
||||
reconciliation waiting inside EMERGENT-WP-0002. Whitehat creates no
|
||||
institutional assent, severity, or live assurance.
|
||||
|
||||
|
||||
## Artifact preservation and repository sync — 2026-10-03
|
||||
|
|
@ -114,8 +117,10 @@ Hub delivery already sent:
|
|||
### Recorded by risk-nexus
|
||||
|
||||
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.
|
||||
Whitehat records the ids and does not regrade them. All three remain `open`
|
||||
there. EMERGENT-WP-0002-T07 has since accepted the scoped review and the
|
||||
library remediations, and has left provider routing and supported
|
||||
current-source use waiting. Register closure stays with risk-nexus.
|
||||
|
||||
| Reporter fact | Register id | Grade recorded by risk-nexus |
|
||||
| --- | --- | --- |
|
||||
|
|
@ -123,29 +128,28 @@ Their closure conditions still require EMERGENT-WP-0002-T07.
|
|||
| 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
|
||||
### Recorded by emergent-security
|
||||
|
||||
EMERGENT-WP-0002-T07 is the acceptance owner. EMERGENT-WP-0002-T04 is already
|
||||
`done` in that plan and is their implementation record. T03 stays `wait`
|
||||
until that plan records all of the following.
|
||||
Satisfied by commit `19e7feb` and
|
||||
`docs/evidence/2026-10-03-whitehat-t03-dispositions.md`. T07 remains `wait`
|
||||
and EMERGENT-WP-0002 remains blocked. Those residuals have that live owner.
|
||||
|
||||
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 (RISK-F-0013) and WH-KNOW-002 (RISK-F-0014) are
|
||||
remediated for digest
|
||||
1. Independence: accepted for the scoped offline repository review, including
|
||||
the disclosed shared-session limits. It is not an authenticated external
|
||||
principal or institutional assent.
|
||||
2. Library remediation: accepted for WH-KNOW-001 / RISK-F-0013 and
|
||||
WH-KNOW-002 / RISK-F-0014 on 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.
|
||||
4. Their disposition of the `informed-decision` pin drift named above.
|
||||
Whitehat does not re-pin the bundle.
|
||||
commit `681144e5d4f59ef00418e7ae776e180b671f5d4d`.
|
||||
3. Provider renewal: waiting. RISK-F-0015 stays open. Source-validated
|
||||
startup is withheld while `informed-decision` is `changed`. Whitehat does
|
||||
not run providers.
|
||||
4. Pin drift: retain `f0c60637e3fe592a23cc31ace8e4d386ff04b710`. Do not
|
||||
re-pin from the dirty sibling checkout. Reconciliation waits on
|
||||
owner-published source provenance.
|
||||
|
||||
Whitehat will not edit `emergent-security` or `risk-nexus`, mark their tasks
|
||||
done, grade severity, or send a packet. T05, T08, T09, T10 and human
|
||||
adoption remain in EMERGENT-WP-0002. A pass means only that the attacks
|
||||
attempted in this run did not work.
|
||||
Whitehat does not edit `emergent-security` or `risk-nexus`, mark their tasks
|
||||
done, or grade severity. T05, T08, T09, T10 and human adoption remain in
|
||||
EMERGENT-WP-0002. A pass means only that the attacks attempted in this run
|
||||
did not work. This plan is finished because its three tasks are done and
|
||||
the remaining acceptance work has those live owners.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue