Skip to content

Integrations Guide

Heisenbug edited this page Mar 5, 2026 · 1 revision

Home · Security Features Guide

At a glance

  • Integrations extend CSF beyond local host-only controls.
  • Pick integrations based on topology: panel-managed, reverse-proxy, or multi-node estate.
  • Validate client-IP visibility and trust boundaries before enabling automation.

Integration patterns

Control panel and built-in UI workflows

Use when admins need browser-based operations and policy visibility.

Blocked-user UX and self-service unblock flows

Use when blocked users should see a deterministic block page/message instead of silent connection failures. Prefer Messenger v3 where platform support exists.

Upstream edge enforcement (Cloudflare)

Use when origin-side blocking is insufficient because traffic arrives via reverse-proxy edges. Note that automatic Cloudflare sync is intentionally limited to specific trigger classes (primarily LF_MODSEC/LF_CXS).

Multi-node propagation and control-plane workflows

Use when you need cross-node block intelligence sharing and controlled cluster-wide actions. Treat delivery as best-effort and validate timeout/recovery behavior in advance.

Platform-specific control panel environments

Use when panel-specific behavior influences service paths, templates, auth flow, and UI/control-plane ownership.

Generic Linux deployments

Use when no control panel abstraction exists and policy is managed directly.

Pre-integration checklist

  1. Confirm real client IP visibility in logs/app stack.
  2. Define rollback path (console access + known-good config).
  3. Enable one integration at a time.
  4. Capture baseline logs before/after activation.

Validation checklist

csf -ra
systemctl status lfd 2>/dev/null || service lfd status
tail -n 100 /var/log/lfd.log

Also validate that trusted admin workflows still succeed after each integration change.

Common pitfalls

  • Integrating edge controls before confirming client-IP restoration.
  • Enabling UI surfaces without strict allowlists.
  • Mixing temporary and permanent automation workflows without cleanup strategy.
  • Changing several integration layers in one maintenance window.

See also

Last reviewed: 2026-02-27


Security Features Guide · Troubleshooting & Recovery

Clone this wiki locally