docs(H-389): tighten CDP security guidance

Co-authored-by: multica-agent <github@multica.ai>
This commit is contained in:
2026-08-20 22:37:28 +08:00
co-authored by multica-agent
parent 9c19721991
commit ab04c21254
+2 -1
View File
@@ -59,7 +59,8 @@ CDP observes browser-internal decrypted events. It is not a client/server proxy,
## Security and reliability
- Never commit or log CDP tokens, cookies, `Authorization`, `Set-Cookie`, credentials, full sensitive bodies, or production data.
- Use short-lived CDP credentials over a protected internal or TLS connection, with session isolation and auditable access.
- Never put CDP tokens, `Cookie`, `Authorization`, credentials, or unredacted sensitive values in any URL.
- Treat CDP access as browser-high-privilege: use short-lived credentials, protected internal or TLS transport, least privilege, session isolation, and auditable access.
- Redact sensitive headers and bodies before persistence or export; enforce body, event, frame, and retention limits.
- Treat response bodies as optional: cache, target closure, protocol behavior, or lifecycle timing may make them unavailable.
- Report disconnects, target closure, dropped events, and body-read failures without stopping the browser workload.