Let’s put it straight:
Siddhu Kalliguddi, at the recent RTC event in Dubai hosted by Restroworks, pointed out that the basic conversation around restaurant technology security nowadays begins with IT leaders talking firewalls, intrusion detection systems, and zero-trust architectures.
In reality, though, the vulnerabilities stem from weak network segmentation, unsynced POS systems, IoT devices running on outdated firmware, WiFi infrastructure, and payment systems.
Kalliguddi brings nearly 17 years of experience in hospitality technology. As of now, he serves as IT Manager at Citymax Hotels (part of Dubai’s Landmark Group) after earlier roles with The Ascott Limited in Mumbai and Fortune Park Hotels.
He is ITIL v4 Foundation–certified, holds CCNA and CCNP credentials, and was recently named IT Manager of the Year at the CIO Connect Summit & Awards in Dubai.
His approach centers on what he calls a reliability-first mindset, in which technology enhances operational efficiency without introducing new vulnerabilities.
The Basics
Restaurant security often fails at the foundational level, only because we tend to ignore the basics.
Take a POS system that has been running on the same software since 2018, with no updates whatsoever, or network segmentation that puts guest WiFi on the same subnet as payment terminals. Or even basic, no password changes for years on end.
It’s the digital version of leaving the back door open because locking it feels inconvenient.
When restaurant groups scale fast and digitize faster, these gaps spread system-wide.
At brands like Nando’s, Kalliguddi keeps it all practical. “I focus on solutions which simplify the workflow, integrate smoothly with the existing system,” he says. “Any new ideas in Nando’s are data-driven, validated, and in close collaboration with the operation before scaling.”
The goal is to reduce friction, manage risk, and help restaurants deliver the same trusted experience every day. Security, in this case, is embedded in how systems are designed and deployed from the very start.
Resilience In Practice
Think of that moment when 200+ orders come through at once. Your POS system definitely shouldn’t be lagging right now. Payments can’t fail. Kitchen display screens need to be as real-time as possible. If any of these systems go down or slow down even for a second or two, the entire operation grinds to a halt.
That’s when resilience becomes non-negotiable. As Kalliguddi explains, “Resilient IT systems come with strong network stability, rapid failover, and simplified systems that keep POS, payment, and kitchen operation running under peak pressure.”
The problem is, a lot of “security” actually creates friction. Be it firewalls that slow payments, login systems that lock staff out mid-service, or monitoring tools that cry wolf so often that real issues get missed. On paper, it may look safe. On the floor, it breaks the flow.
Kalliguddi’s focus is on solutions that work under actual operating conditions. Systems need to maintain stability when under pressure, fail over rapidly when something breaks, and stay simple enough that core functions keep running regardless of what else is happening.
Governance for Speed
In most restaurant groups, Kalliguddi has noticed, governance feels like it was designed by those who’ve never worked a dinner shift.
Simple changes take weeks to approve. Compliance block deployments without offering workable alternatives. Decision rights are so unclear that no one’s quite sure who’s actually allowed to say yes.
Basically, everything moves tortoise, except the dining room.
In response, Kalliguddi pushes for streamlined processes, clear decision rights, and lightweight checks. “Good governance should help teams move, not hold them back,” he says.
This requires rethinking how IT decisions get made. Instead of centralized approval for every minor change, establish clear parameters and let teams operate within them. Instead of comprehensive security reviews before every deployment, implement automated checks that catch critical issues and let everything else through.
Protecting Guest Trust
Looking forward, Kalliguddi believes technology must protect guest trust above everything else. “Speed and data matter. If the guest feels his data is safe, every other innovation is very possible.”
And this isn’t even an abstract concern. Breaches in restaurant groups make the news all the time. Card details get stolen. Customer databases leak. Loyalty accounts get hacked. Every incident chips away at the trust that took years to build.
Solution, surprisingly, starts with the mindset. You must treat security as a foundational requirement from the get-go. Before deploying a new loyalty app, ask what customer data it collects and how it protects that data. Before implementing IoT kitchen equipment, verify that it can be patched and monitored. Before launching online ordering, ensure payment processing meets current standards and can be updated as those standards evolve.
Make sure any innovation you introduce doesn’t break trust. Because once trust is gone, no feature, app, or “experience upgrade” really matters.
Building From the Ground Up
Kalliguddi’s career arc tracks the evolution of hospitality itself. He started out as a system administrator in Goa in 2005, moved through network infrastructure roles at Fortune Park Hotels and The Ascott, and eventually led IT for hotel groups and restaurant brands across India and the UAE. As the industry shifted from basic tech setup to tech as a business driver, his role shifted with it.
Maybe that’s why his view on restaurant security is almost boring in its simplicity. He’s always advocating for “fixing the foundation first.”
Because, after all, installing an alarm system won’t cut it if the back door is still open.
