You are reading the documentation for v1.3.0. The current release is v1.4.0. Go to the latest version of this page →

If your deployment is subject to GDPR, CCPA or an equivalent regime

Subscriber MAC addresses and session identifiers are personal data. With the
default configuration they stay on the box, so turning the capture on is a
change to what the box records, not to what it discloses to a processor.

Opting a destination in is the processing change. That is when the
identifiers reach a destination you do not control, under whatever retention it
applies, and that is what belongs in your record of processing. Two other
bounds still apply and are still worth using:

  • Run it as a bounded session. Turn the capture on while you are
    diagnosing and stop it afterwards. Nothing about it is meant to be left
    running, and everything else in the RADIUS diagnostics — the offline engine,
    the conformance report, the capture corpus — works with the tap stopped.
  • Size the exposure. A segment contributes at most 51 entries (a receipt
    plus max_entries, default 50), whatever is in it — so a spool rotating
    every sixty seconds tops out near 3000 entries an hour even during an
    incident.