Add in-process known-bad fixtures for remaining ASM T-01–T-10
Each Canon test now has a fixture-asm registration that fails known-bad and passes known-good in-process. Live asm-tNN targets stay pending. No network, OpenBao, or packet. Assistant: grok Assistant-Session: 01a05e32-c776-72a3-86ec-c490e027aca9
This commit is contained in:
parent
75deaf073f
commit
6f1ca0bfef
38 changed files with 1132 additions and 37 deletions
|
|
@ -4,7 +4,7 @@
|
|||
"posture_claim": "ASM T-02",
|
||||
"attacker_model": "prompt-injected agent enumerating or requesting reusable credentials",
|
||||
"applicability": "pending",
|
||||
"applicability_reason": "No synthetic canary credential lane and no agent-context oracle. Value-safe whitehat receipts are not T-02. Known-bad design: place a canary in model-visible context; the probe must detect it without retaining the value. This registration does not authorize a probe.",
|
||||
"applicability_reason": "In-process known-bad calibration exists as fixture-asm-t02. Live run still needs a named surface, identities, and dated engagement. This live registration does not authorize a probe.",
|
||||
"approval_classes": [
|
||||
"asm"
|
||||
],
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue