How to Achieve Law No. 5651 Compliance for Schools and Dormitories

Schools, universities and dormitories provide internet to students, staff and guests, so they are mass-use providers under Law No. 5651 and must record all connections in a way that can be traced to a person. These institutions have two extra challenges: a high number of users (hundreds/thousands of devices at once) and often minors. The solution must therefore combine a scalable captive portal (student number/e-mail, SMS, or LDAP/Active Directory verification), central and timestamped log collection, and, where needed, content filtering. Records must be retained for the legal period with integrity intact.

This page is for information only; consult the current legislation and a legal advisor for definitive obligations.

How is student identity verified?

If the institution has an existing directory (Active Directory/LDAP), students and staff can be verified with these accounts; SMS or form is used for guests. In LDAP portal login, it is important that the user is assigned only to the defined group and that the identity matches correctly. This binds the record clearly to a person.

High user count and density

On campus and dormitory networks, many devices connect at once. The log server must handle this volume, match NAT/DHCP records to identity quickly, and use disk efficiently with automatic rotation/encrypted archiving.

Is content filtering required?

Especially where minors are present, blocking inappropriate content is a frequent requirement. Content filtering can be set up alongside logging; however, the essence of the legal obligation is record-keeping and identification. [TO BE VERIFIED: the scope of any content-filtering obligation for educational institutions should be confirmed from the current legislation.]

How is SignLogger used in schools and dormitories?

SignLogger offers a captive portal with LDAP/Active Directory, SMS and form verification, syslog collection from all brands, daily signing of logs with the TÜBİTAK Kamu SM timestamp and e-signature, and central reporting for high-volume environments. It installs as a VMware/Hyper-V image. For the general framework see Law No. 5651 log obligation, and for the record set see which logs to keep. Explore the features or request a demo.

Frequently Asked Questions

Does collecting students’ personal data violate KVKK?

As long as it is processed purpose-limited, securely and time-bounded, records kept under Law No. 5651 do not conflict with KVKK. Access control and encryption are important.

Can I use Active Directory for student login?

Yes; LDAP/AD verification is possible. The user must be assigned to the correct group and the identity must match clearly.

Will the system keep up when thousands of devices connect at once?

The log server must be sized for high volume; SignLogger supports these scenarios with central collection and automatic rotation.

Is content filtering mandatory?

The essence of the legal obligation is record-keeping and identification; content filtering can be added per institutional policy and environment.

Do dormitory guests need separate verification?

A separate verification flow such as SMS/form can be defined for guests; students/staff are verified from the directory.

How long must I retain records?

Common practice is at least 6 months and at most 2 years; the exact period may vary by current regulation.