Browser Sandbox & Pixel Auditor Audit
Project 3 Release Candidate Suite
Jump & context
Week 15: Project 3 Hardening Sprint (Agent & Workflow System) & Cross-Project Red Teaming Start
The five hours
- 01
Concepts & system design
60 min· read · map the mechanismR33 — Playwright
R25 — Docker security
R41 — Agentic security
R21 — MCP
R22 — OAuth
R27 — OpenTelemetry
Read the assigned sections; map the mechanism, threat model and trade-offs.
- 02
Project implementation
120 min· build · integrate · debugAudit
P3browser sandbox: disposable Playwright profile, confined download dir, egress allowlist, command denial,D9screenshot/OCR/DOM coordinate verification, parameter-bound approval, andC6human takeover/emergency stop. Run malicious webpage tests.Run the complete
P3RC suite: workflow invariants,D2MCP auth,D3message bus,D7OAuth delegation,D9browser isolation,C4code-diagnosis sandbox,D11trajectory ledger,D8PyRIT CI gate (C12), andM10misuse evaluation.Build, integrate, debug and improve the increment in the active project.
- 03
Security lab
60 min· attack your own systemNo separate task text for this block on day 88 — the sourced work sits in the block above. Keep the time box.
Test the abuse case, failure path, authorization bypass or resource limit.
- 04
Verification & evidence
30 min· test · record evidenceFreeze
P3RC package: architecture diagram, threat model, test/evaluation report, and residual-risk statement.Add or run regression tests; record the 9-point evidence record.
- 05
Deliberate practice & Socratic review
30 min· explain aloud · update gapsAnswer the 8 Socratic questions without notes: What? Why? How? What if? Why not? How can I prove it? Where can it break? What have I learned?
Re-explain the hardest concept aloud, inspect one edge case, update the gap log.
- total5 h
Read today · inside the concepts block
R21 R22 R25 R27 R33 R41Official specification: client/server lifecycle, JSON-RPC messages, tool discovery, authorization, and trust boundaries.
RFC 6749 core flows + RFC 9700 security best practices: narrow scopes, audience restriction, token leakage, and replay.
Daemon surface, Linux namespaces/capabilities, rootless/non-root containers, read-only FS, and secrets.
Traces, spans, context propagation, semantic conventions, and redacting sensitive attributes.
Isolated BrowserContext, downloads, permissions, screenshots, bounding boxes, locators, and tracing.
Agentic threat taxonomy: tool misuse, excessive agency, memory poisoning, inter-agent trust, and human oversight.
Read only the named sections needed for today's task. Reading sits inside the 60-minute concepts block; it is not extra time.
Free resources for this day
5 curated- docsPlaywrightIsolation
Shows that each BrowserContext is an incognito-like profile with its own cookies and storage, which is the disposable-profile primitive your D9 browser sandbox must create per task.
R33checked 2026-11-11 - videoDatadogContainer Security Fundamentals - Seccomp
Demonstrates filtering container syscalls with a seccomp profile, the concrete mechanism for command denial when a computer-use agent tries to shell out of its sandbox.
R25checked 2026-11-11 - videoNaveen AutomationLabs · 18:08#5 - BrowserContext in Playwright || Handle Two different user sessions with BrowserContext
Builds two fully separate browser sessions side by side, which is the practical test for whether your agent's profile isolation actually prevents cross-session cookie leakage.
R33checked 2026-11-11 - articleSafeguard.shContainer Isolation: Namespaces, Cgroups, Seccomp
Frames containers as three kernel primitives and catalogs the escape-prone misconfigurations (privileged flags, host mounts), the checklist for auditing the agent's container boundary.
R25checked 2026-11-11 - docsDocker DocsRootless mode
Explains running both daemon and container inside a user namespace with no root, the baseline control when the code-diagnosis and browser sandboxes share one host.
R25checked 2026-11-11
Evidence record · 9-point standard
A lab is complete only when it produces evidence. Installing PyRIT, Garak, Presidio or TransformerLens is not completion. Saved on this device only.
Day notes
emptyThe two source formulations
verbatim · nothing summarisedProject & Deliverable Target
Project 3 Release Candidate (C6, C12) | `D2`, `D3`, `D7`, `D8`, `D9`, `D11` | M9, M10
Focus 1 (Browser Sandbox & Pixel Auditor Audit — Orig. Day 113)
Audit P3 browser sandbox: disposable Playwright profile, confined download dir, egress allowlist, command denial, D9 screenshot/OCR/DOM coordinate verification, parameter-bound approval, and C6 human takeover/emergency stop. Run malicious webpage tests.
Focus 2 (Project 3 Release Candidate Suite — Orig. Day 114)
Run the complete P3 RC suite: workflow invariants, D2 MCP auth, D3 message bus, D7 OAuth delegation, D9 browser isolation, C4 code-diagnosis sandbox, D11 trajectory ledger, D8 PyRIT CI gate (C12), and M10 misuse evaluation.
Verification & Evidence
Freeze P3 RC package: architecture diagram, threat model, test/evaluation report, and residual-risk statement.
Read Today (60m Concepts Block)
R33 (Playwright), R25 (Docker security), R41 (Agentic security), R21 (MCP), R22 (OAuth), R27 (OpenTelemetry).
---