The alert came in at 3:17 a.m. A privacy report flagged a live endpoint streaming personal data across borders. Your logs didn’t lie. The SOCat tunnel you spun up for testing had become a direct line to a GDPR nightmare.
GDPR compliance isn’t just fine print. It’s law with teeth. When SOCat moves data between environments, every byte can be in or out of compliance depending on where it flows and who touches it. The risk isn’t hypothetical. €20 million fines aren’t theory.
SOCat is fast, blunt, and trusted for port forwarding, tunneling, and cross-network debugging. But when it’s used in production systems holding personal data, every step must align with GDPR principles: data minimization, lawful processing, security by design. Without controls, SOCat can punch direct pathways that bypass safeguards, logging, and audit trails. That makes data transfers opaque. And opacity breaks compliance.
The fix starts at design. Map your data flows. Know where your SOCat tunnels terminate. Encrypt all data in motion, but don’t stop there—log every session, enforce access control, and tie endpoints to clear retention policies. Under GDPR, encryption without governance is like a lock without a key: it exists, but it’s useless if no one knows how to check it.