Files
sure/pipelock.example.yaml
LPW b457514c31 chore(pipelock): bump chart default to v2.2.0, add CI scan badge (#1494)
- Helm chart default pipelock.image.tag bumped from 2.0.0 to 2.2.0
  (three minor releases behind latest)
- README: pipelock CI scan status badge added to the existing badge row
- charts/sure/README.md, docs/hosting/pipelock.md, pipelock.example.yaml:
  refreshed feature notes to reference the upstream changelog rather than
  pinning to a single version
- compose.example.ai.yml: pin example comment bumped to :2.2.0
- Workflow pin (@v2) unchanged — floating major tag picks up 2.2.x
2026-04-18 09:32:23 +02:00

75 lines
1.9 KiB
YAML

# Pipelock configuration for Docker Compose
# See https://github.com/luckyPipewrench/pipelock for full options.
#
# Recent additions: trusted_domains, redirect profiles, attack simulation,
# security scoring, process sandbox, enhanced tool poisoning detection, signed
# action receipts, per-pattern DLP warn mode, and the `pipelock posture verify`
# / `pipelock session` CLIs.
# Run `pipelock simulate --config <file>` to test your config against 24 attack scenarios.
# Run `pipelock audit score --config <file>` for a security posture score (0-100).
version: 1
mode: balanced
# Trusted domains: allow services whose public DNS resolves to private IPs.
# Prevents SSRF scanner from blocking legitimate internal traffic.
# trusted_domains:
# - "api.internal.example.com"
# - "*.corp.example.com"
forward_proxy:
enabled: true
max_tunnel_seconds: 300
idle_timeout_seconds: 60
websocket_proxy:
enabled: false
max_message_bytes: 1048576
max_concurrent_connections: 128
scan_text_frames: true
allow_binary_frames: false
forward_cookies: false
strip_compression: true
max_connection_seconds: 3600
idle_timeout_seconds: 300
origin_policy: rewrite
dlp:
scan_env: true
include_defaults: true
response_scanning:
enabled: true
action: warn
include_defaults: true
mcp_input_scanning:
enabled: true
action: block
on_parse_error: block
mcp_tool_scanning:
enabled: true
action: warn
detect_drift: true
mcp_tool_policy:
enabled: false
action: warn
# Redirect profiles: route matched tool calls to audited handler programs
# instead of blocking. The handler returns a synthetic MCP response.
# redirect_profiles:
# safe-fetch:
# exec: ["/pipelock", "internal-redirect", "fetch-proxy"]
# reason: "Route fetch calls through audited proxy"
mcp_session_binding:
enabled: true
unknown_tool_action: warn
tool_chain_detection:
enabled: true
action: warn
window_size: 20
max_gap: 3