Skip to content

Security: fmuffat/sflow-analytics

Security

SECURITY.md

Security policy

Reporting a vulnerability

Please report vulnerabilities privately through GitHub's "Report a vulnerability" (Security tab) rather than in a public issue. Include the version, a description, and steps to reproduce. You should receive an answer within a few working days.

Scope and current limitations

  • Authentication: local accounts (Argon2id), HttpOnly/Secure/SameSite=Strict session cookie, idle and absolute timeouts, login throttling, forced change of the initial password. Only one role (administrator) exists so far. AUTH_ENABLED=false is for local development only.
  • Stored secrets (controller credentials) are encrypted with a per-installation key (SECRET_KEY or secret.key on the app-config volume): back up that volume.
  • The collector accepts sFlow from any source on UDP/6343; restrict it with a firewall to the switches' management addresses.
  • In development, the collector status endpoint and ClickHouse are published on 127.0.0.1 only. Do not publish them in production.
  • Never commit .env: it contains the ClickHouse password (generated by scripts/dev-up.sh). CI scans the history with gitleaks.

There aren't any published security advisories