Browser-based graphical shell and control plane for a Linux server you own — real terminal, file manager, live metrics and BYOK AI in one mobile-first workspace. Next.js 16 · React 19 · node-pty · Tailwind v4 · shadcn/ui. Public alpha, self-hosted.
TypeScript browser-shellcontrol-planefile-managerhomelabmobile-firstnextjsptyreactself-hostedserver-managementshadcn-uisysadmintailwindcssterminaltypescriptvpsweb-desktopweb-terminal
fix(security): review cache-only passive signal
Rahmandd52cd81d214
diff --git a/docs/PROGRESS.md b/docs/PROGRESS.mdindex 9cc67c35..ab6076d1 100644--- a/docs/PROGRESS.md+++ b/docs/PROGRESS.md@@ -1,3 +1,12 @@+## 2026-09-18 — Classify cache retrieval only for immutable public assets++The first post-merge passive ZAP run against main produced one new default warning:+rule 10050 (Retrieved from Cache) on five content-hashed _next/static JavaScript/font+assets carrying an Age header. The report contained no authenticated, personal, or+user-specific URL for that rule. Keep the signal visible as INFO for those intentionally+cacheable public assets; do not use IGNORE, do not alter authenticated response caching,+and leave every other unreviewed ZAP rule at its default warning/failure behavior.+## 2026-09-18 — Require executed passive security scan evidenceThe security closeout found that the scheduled hosted ZAP workflow could reportdiff --git a/docs/SECURITY-ASSURANCE.md b/docs/SECURITY-ASSURANCE.mdindex 8512bbec..41d7a6a1 100644--- a/docs/SECURITY-ASSURANCE.md+++ b/docs/SECURITY-ASSURANCE.md@@ -89,7 +89,7 @@ The exception is intentionally finding-specific. The file and rules are **not**## Reviewed ZAP informational alerts-The production baseline keeps five known passive signals visible as `INFO`: cache policy on the public manifest, intentionally non-storable private/auth-shell responses, broad HTTPS sources in `img-src`/`frame-src`, a Unix timestamp in a static bundle, and the deliberate absence of COEP. The CSP exception is a product trade-off: MSO permits user-selected remote images and sandboxed HTTPS embeds, while `connect-src` remains restricted and inbound framing is blocked by CSP `frame-ancestors 'none'` plus `X-Frame-Options: DENY`. COEP would break those supported cross-origin resources.+The production baseline keeps six known passive signals visible as `INFO`: cache policy on the public manifest, intentionally non-storable private/auth-shell responses, retrieval of content-hashed Next.js static chunks/fonts from the shared cache, broad HTTPS sources in `img-src`/`frame-src`, a Unix timestamp in a static bundle, and the deliberate absence of COEP. The cache-retrieval classification is limited to immutable public framework assets observed in the September 18 production scan; authenticated and user-specific responses remain `private, no-cache, no-store`. The CSP exception is a product trade-off: MSO permits user-selected remote images and sandboxed HTTPS embeds, while `connect-src` remains restricted and inbound framing is blocked by CSP `frame-ancestors 'none'` plus `X-Frame-Options: DENY`. COEP would break those supported cross-origin resources.These are rule-specific classifications in `security/zap-baseline.conf`, not a global warning bypass. Any other ZAP baseline alert remains a warning/failure and makes the gate non-zero.diff --git a/lib/security/security-scanner-supply-chain.test.ts b/lib/security/security-scanner-supply-chain.test.tsindex a2f484a2..5b6a0098 100644--- a/lib/security/security-scanner-supply-chain.test.ts+++ b/lib/security/security-scanner-supply-chain.test.ts@@ -30,4 +30,10 @@ describe("security scanner supply chain", () => {expect(script).toContain("zaproxy/zap-stable@sha256:781a2bdaea47324e7bab583e2263f21d257b0aee61ed51521a5be45f5f5081ef");expect(script).not.toContain("ghcr.io/zaproxy/zaproxy@sha256:");});++ it("keeps cache retrieval informational only for the reviewed static-asset policy", () => {+ const policy = fs.readFileSync(path.join(ROOT, "security/zap-baseline.conf"), "utf8");+ expect(policy).toContain("10050\tINFO\t(Content-hashed Next.js static chunks/fonts are intentionally cacheable; authenticated and user-specific responses remain no-store)");+ expect(policy).not.toContain("10050\tIGNORE");+ });});diff --git a/security/zap-baseline.conf b/security/zap-baseline.confindex 8013193d..0fc8f1a0 100644--- a/security/zap-baseline.conf+++ b/security/zap-baseline.conf@@ -3,6 +3,7 @@# Any other ZAP baseline rule remains WARN by default and therefore fails the gate (exit 2).10015 INFO (Public web manifest intentionally revalidates; no sensitive content)10049 INFO (Private/authenticated responses intentionally use no-store; static auth-shell responses inherit it)+10050 INFO (Content-hashed Next.js static chunks/fonts are intentionally cacheable; authenticated and user-specific responses remain no-store)10055 INFO (CSP permits arbitrary HTTPS image/embed sources by product design; connect-src remains tightly restricted)10096 INFO (Build/static bundle contains ordinary Unix timestamps; no credential or host-secret exposure)90004 INFO (COEP intentionally omitted because cross-origin media/embeds are supported; inbound framing is denied separately)