5651 compliance
5651 logging requirement
Businesses, hotels and venues offering public Wi‑Fi must retain access records tied to user identity for the legally required period. Scattered device logs create audit risk. Central 5651 logging keeps signed records in one archive.
What does 5651 require?
Operators offering public internet typically must retain subscriber/user-linked access logs and produce them on lawful request. Details follow current regulation; technically you need identity–session binding and integrity-protected logs.
Why central RADIUS / hotspot?
When every AP or modem keeps its own logs, archives fragment and identity mapping breaks. RADIUS-based auth writes login, duration and logout from one source—audit prep drops from days to hours.
How IDNET applies it
IDNET Radius Manager combines hotspot portal, subscriber management and a 5651-oriented log archive. Retention and signing are central; hotel PMS or directory systems can bind identity.
Who needs it most?
Hotels, café chains, malls, campuses, guest office networks and hotspot ISPs. Existing MikroTik or similar APs usually join as RADIUS clients.
Frequently asked questions
Does every Wi‑Fi network need 5651 logging?
Public or customer-facing internet often triggers obligations. Closed corporate LANs differ—confirm with counsel. A ready logging stack reduces audit risk either way.
How long must logs be kept?
Retention follows current regulation. IDNET configures retention policy with controlled access to the archive.
Must we replace hotspot hardware?
Usually not—APs stay as RADIUS clients while IDNET centralizes identity and logs. Hardware refresh is only for capacity or security needs.
IDNET Radius Manager
This page targets one search intent. See the main product page for full scope and technical detail.
/en/software/idnet-radius-manager ↗