Hands-on tutorial
Tutorials · Compliance
GDPR for Network Teams: Practical Security Controls and Checklist
What the EU General Data Protection Regulation expects from your network: security of processing, access control, logging, encryption, guest Wi-Fi data, CCTV, retention and breach readiness, with a checklist you can apply.
Quick answer
GDPR (EU Regulation 2016/679) requires organisations that process personal data of people in the EU to protect it with 'appropriate technical and organisational measures' (Article 32) and to report personal data breaches to the supervisory authority within 72 hours where required (Article 33).
For the network team, that means segmentation, strong authentication, encryption, logging, timely patching, data minimisation in systems such as guest Wi-Fi and CCTV, and the ability to detect and investigate incidents.
This guide explains network controls that commonly support compliance. It is not legal advice; confirm your obligations with your legal or compliance adviser.
Key terms
- Personal data
- Any information about an identifiable person: names, emails, phone numbers, IP and MAC addresses linked to a person, CCTV images.
- Controller / processor
- The controller decides why and how data is processed; a processor processes it on the controller's behalf (for example a cloud provider).
- DPIA
- Data protection impact assessment, required for high-risk processing such as large-scale CCTV monitoring.
Before you start
- A record of processing activities (what personal data, where, why)
- A network diagram showing where personal data flows
- Your organisation's retention and incident response policies
Step by step
Map personal data on the network
Identify systems that hold or carry personal data: HR and customer systems, email, guest Wi-Fi portals, CCTV recorders, access control and logs. Mark them on the network diagram.
Segment and restrict access
Put systems holding personal data in their own VLANs or zones and allow only the flows they need. Guest, IoT and camera networks must not reach them.
Staff VLAN → HR app: TCP 443 only Guest VLAN → internal: deny all CCTV VLAN → NVR only
Strong authentication for administrators
Use individual admin accounts, MFA and role-based access on switches, gateways, NavCloud and servers. Remove shared and default accounts.
Encrypt in transit
Use HTTPS, SSH and TLS for management and applications, WPA3 or WPA2-Enterprise on Wi-Fi, and VPNs between sites and for remote access.
Minimise data in network systems
Guest Wi-Fi portals and CCTV collect personal data. Collect only what you need, show a privacy notice, make marketing consent separate and optional, and set automatic deletion.
Log, monitor and keep time accurate
Collect logs from gateways, firewalls, Wi-Fi and authentication systems centrally, with NTP-synchronised time, so you can investigate who accessed what and when.
Patch and harden
Keep firmware current, especially on internet-facing devices, disable unused services, and keep configuration backups.
Be ready for a breach
Write and practise an incident plan: detect, contain, assess whether personal data was affected, and involve the data protection officer early so notification deadlines can be met.
Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.
Pro tips
- Document every control: auditors ask for evidence, not just configuration.
- Review guest Wi-Fi and CCTV retention settings at least yearly.
- Test restores and incident response, not just backups.
GDPR principles and the network controls that support them
| GDPR principle | Network control |
|---|---|
| Integrity and confidentiality (Art. 5(1)(f)) | Segmentation, encryption, access control, patching |
| Storage limitation (Art. 5(1)(e)) | Retention and automatic deletion for portal data, logs and CCTV |
| Security of processing (Art. 32) | MFA, logging, backups, regular testing |
| Breach notification (Art. 33–34) | Central logging, monitoring and an incident plan |
| Data protection by design (Art. 25) | Minimal data collection in Wi-Fi portals and devices |
Standards and references
FAQ
Frequently asked questions
Is an IP address personal data under GDPR?
It can be, when it can be linked to an identifiable person, which is often the case in logs and guest Wi-Fi records.
Does GDPR apply outside the EU?
Yes, when an organisation offers goods or services to, or monitors, people in the EU, for example a hotel taking bookings from EU guests.
How long can we keep CCTV footage?
GDPR sets no fixed period; keep it only as long as necessary for the purpose, often days or weeks, and document the reason. Local rules may set limits.
Keep learning
Related guides
Hotel guest Wi-Fi sign-in
Read more →Network segmentation
Read more →NavCloud
Read more →Firmware and security updates
Read more →Navijin cybersecurity
Read more →PCI DSS v4.0 for Networks: Segmentation, Firewalls and Wi-Fi
How the Payment Card Industry Data Security Standard applies to your network: defining the cardholder data environment, segmentation to reduce scope, firewall and router rules, wireless, logging, testing and secure management.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.