dorfteich/docs/vs-nfd
Claude Fable 5 9b7acab294
All checks were successful
CI / Lint, typecheck, test (pull_request) Successful in 6m21s
CI / Build container images (pull_request) Successful in 3m59s
CI / Auth e2e pack (pull_request) Successful in 8m35s
CI / Import/export fidelity gate (pull_request) Successful in 1m1s
CD / Build and push images (push) Successful in 17s
CD / Deploy to Test (push) Successful in 14s
CD / Smoke tests against Test (push) Successful in 1m17s
CD / Promote to Int (push) Successful in 12s
CI / Build container images (push) Has been skipped
CI / Auth e2e pack (push) Successful in 8m27s
CI / Import/export fidelity gate (push) Successful in 58s
CI / Lint, typecheck, test (push) Successful in 6m30s
#232: plugin allowlist with SHA-256 hash pinning
The install path records the SHA-256 of the delivered bundle ZIP
(plugins.bundle_hash; pre-#232 installs show it as unknown until
reinstalled). plugins.allowlist in instance_settings names permitted
ids with their pinned hashes: empty (default) = not enforced, existing
instances unchanged; non-empty = installs of unlisted or deviating
bundles are rejected (plugin_not_pinned / plugin_hash_mismatch, 403),
and an installed plugin outside the list or with a deviating hash does
not load — absent from pond mount lists, frame/assets 404. Every
rejection is audited (plugin.rejected, catalogue v1.5). A version bump
changes the hash and therefore requires an explicit re-pin — the
intended friction (ADR 0025). Admin UI shows observed vs pinned hash
per plugin with pin/re-pin/unpin. Scope stated honestly in
plugin-architecture.md: the pin answers "is this the reviewed bundle";
post-install disk tampering is platform integrity (ADR 0019), sandbox
containment stays the sandbox's job. Hardening guide row + catalog
advisory triage; residual risk R-03 resolved. e2e: empty-allowlist
compatibility, pinned load, unpinned and tampered installs rejected and
audited, pin drift blocks loading while the admin still sees the
mismatch, version bump needs re-pin. Full api suite 101 files / 561
green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AUtYMxwTCMHG9mVHnwbFg8
2026-07-31 21:26:36 +02:00
..
00-analyse-auftrag.md docs: VS-NfD readiness planning (ist-aufnahme, plan, ADRs 0019-0026, issue drafts) 2026-07-30 01:48:05 +02:00
10-ist-aufnahme.md docs: VS-NfD readiness planning (ist-aufnahme, plan, ADRs 0019-0026, issue drafts) 2026-07-30 01:48:05 +02:00
20-massnahmenplan.md #232: plugin allowlist with SHA-256 hash pinning 2026-07-31 21:26:36 +02:00
30-issue-adr-auftrag.md docs: VS-NfD readiness planning (ist-aufnahme, plan, ADRs 0019-0026, issue drafts) 2026-07-30 01:48:05 +02:00
31-issue-entwurf.md docs: VS-NfD readiness planning (ist-aufnahme, plan, ADRs 0019-0026, issue drafts) 2026-07-30 01:48:05 +02:00
40-abgrenzungserklaerung.md #227: hardening guide with the VS-NfD reference configuration 2026-07-31 10:35:26 +02:00
50-haertungsleitfaden.md #232: plugin allowlist with SHA-256 hash pinning 2026-07-31 21:26:36 +02:00
60-sicherheitsdokumentation.md #215: trusted reverse-proxy header / mTLS client-certificate path 2026-07-31 12:50:09 +02:00
70-betriebshandbuch.md #221: offline update path incl. migrations, rehearsed with rollback 2026-07-31 17:26:50 +02:00
80-grundschutz-mapping.md #230: IT-Grundschutz mapping for APP.3.1 and CON.11.1 2026-07-31 10:35:26 +02:00
90-restrisiken.md #232: plugin allowlist with SHA-256 hash pinning 2026-07-31 21:26:36 +02:00
95-mirror-protokoll.md #218: mirror procedure into an internal registry 2026-07-31 14:33:04 +02:00
96-offline-build-protokoll.md #219: verified reproducible build without network access 2026-07-31 14:39:35 +02:00
97-isolationslauf-protokoll.md #220: protocol of the isolated deployment run 2026-07-31 17:05:08 +02:00
98-update-rollback-protokoll.md #221: offline update path incl. migrations, rehearsed with rollback 2026-07-31 17:26:50 +02:00