Decades of Cybersecurity: Lessons from the Frontlines

Third coffee in, staring at my screen with a confusing mix of excitement and that tired buzz only decades of battling the advancing beast that is cyber security can instill.

My Journey in Cybersecurity

Derek : I began in 1993 as a network admin. You know, back when paging network cables and playing with muxes for voice and data over the good old PSTN was just another day in the office. We were the first, not second wave — establishing beach heads at a time when the internet was barely formed. Today I have my own security company P J Networks Pvt Ltd and over the last month or so I had been fortunate enough to get business from 3 major bank on zero trust upgradation. Zero-trust — that idea’s been to the moon and back, but what happens when you put it into practice out in the field? It’s a different game.

The Worm That Bit Us: Slammer Wakes Up

The Slammer worm that hit in 2003 was yesterday, really. Slammer was a nightmare that ran faster than anything we had ever seen and promptly demonstrated how weak our systems were. It took advantage of unpatched SQL servers as fast as you can say emergency patch. Explaining the chaos while I was knee deep in network traffic — routers clogged, servers crushing. More importantly, I learned some critical basics from that incident:

• Do Patch Quick or Pay. No excuses.
• Legacy protocols and devices will break or be quickly bypassed if forgotten.
• Complexity doesn’t equal security.

I say that last point a lot to clients, and they generally groan. Except that complexity == misconfiguration, holes gone unseen. This is akin to fixing up a vintage car that has been heavily modified, you lose the ability to discern which part will be screaming out when it breaks.

Zero Trust — Only a Buzzword?

Just sitting across those banks made me realize some things. Zero-trust is the magic word on everybody’s lips. But, you see, if you just slap on a zero-trust architecture without first WHY your networking is so perplexed, it fails.

In practice, zero-trust means:

• Treat each user, product, or an area as a potential attacker. Trust no one. Period.
• Micro-segmentation — Since Petya relies on spreading laterally, a tight control by the micro segmentation can help in stopping such movements which can act like a door to stop malware.
• Identity verification in each step.
• Continuous monitoring.

Easy enough to say. More difficult to manage across a patchwork of legacy systems. And banks, wow do they have layers of legacy tech stacked under newer platforms — 20 or more tech stacks at times, ranging from routers and switches to firewalls and VPNs. I tell clients:

Your Network is a grand buffet. Zero-trust is what keeps the cooks, waiters, and diners in separate areas with a strict requirement on who can get into the kitchen. Chaos, right? Chaos which continues to reign over this chaos until the troublemakers ocupam a kids’ room.

The Reality of AI in Cybersecurity

The reliance on marketing jargon is laughable (and a little scary as well). Lately, you may hear about AI-powered cybersecurity everywhere like it is a godsend. I’m skeptical. AI is good at identifying patterns but here are some things it CANNOT do:

• proper firewall configurations
• solid endpoint security
• manual oversight

AI isn’t magic. It’s a tool. Sometimes it gets fooled. It can be blind to things that are painfully, crushingly obvious to any human who knows a thing about networks.

Back to Basics: DefCon and Hardware Hacking

Just returned from DefCon, always great to be blown away by a new view on reality that the hardware hacking village blasts me with. The act makes security more visceral — it is no longer just some bits that we are interacting with but the physical device itself. Takes me back to the good ol’ days when security meant supporting hardware setups, terminal access and physical keys.

Watching people reverse engineer firmware, disecting IoT devices and manipulating RFID cards — it sounds like the old-school hacker ethos getting married with the modern tech.

Rant of the month: we see so many companies chasing after the latest software patch and forgetting about some physical security vectors. But your firewall means nothing if they can simply plugin a bad USB or walk away with a device. Every layer counts.

Password Policies: Why We Get Them Wrong

Then, we (security professionals) squawk when users ruin everything – with their terrible passwords. Oh passwords. I thought that if I had a rupee for every time I ranted about shitty password policy, I might have bought myself a Lamborghini by now. Making complex password rules that are guaranteed not be remembered only yields to:

• Password reuse
• Leaving Sticky notes on monitors
• Insecure password resets

Here’s what works (trust me):

• Long passphrases vs complex passwords (MyDogEats2MAnyBones / P@ssw0rd1!)
• Use MFA. All day, every day.
• Not merely a force-fed set of rules

But still many companies bound by compliance mandates like the 12-character requirement with special characters and a capital letter in the middle. It was like asking for a souffle and working with eggs left in a refrigerator.

In the World of Firewalls, Servers and Routers — A Real Perspective

Averaged — OK, here is a blast from the past for the gear heads in your datacenter or cloud; those routers, servers and firewalls. Do not assume plugging in a product from the most recent Cisco or Palo Alto lines will save you. Configuration is the key.

Do you recall the days of configuring VLANs on a Cisco router is an art? Although physical wiring is less today due to software-defined network (SDN), routers and switches moved directly into the cloud resulting in more complexity but less physical hardware. And complexity is the enemy.

I have also tested work for clients where the recently deployed firewalls had default rules open, allowing literally anyone to walk from the outside network into critical segments. I had a client who never firmware updated in years because of his fear that updating may cause things to break. Here’s the harsh truth:

Do not update and you will be broken — by an attacker.

Quick Wins for Network Security

• Audit your configs regularly. Don’t trust defaults.
• Segment your networks smartly.
• Push firmware and patch updates will be done on schedule.
• Do logchecking daily (not just when something happens)

Quick Take: What You Need to Know in Less Than 5 Minutes

• Legacy systems bite. Don’t ignore them.
• Zero-trust is an attitude, not a check box.
• Avoid the temptation of (nearly) every AI-powered sales pitch — tools do not make up for no understanding.
• Physical security is cybersecurity. One the flip side of the other.
• Passwords easier to remember, harder to guess – passphrases plus MFA.
• Regularly patch and ensure configuration is in place on those firewalls, servers, and routers.

Final Thoughts

And yet…I sometimes wish I could go back to 1993 and tell the me that was just starting out as a leader all of these things– but then I remember how every mistake gave me more insight than any book or article ever could. After all, Cybersecurity is not a destination; it is a journey — tediously slow, continual, annoying but fulfilling.

Owning my own company now means I deal with these frustrations full time. What keeps me going? Because we know that each layer we send along lets someone else rest easier at night.

And you know what, if you got this far, thanks for letting me ramble away with the aid of coffee! So, update your firmware versions, remediate those firewall rules and maybe revisit that password policy.

– Sanjay Seth, sitting at his desk from within P J Networks Pvt Ltd — protecting your networks with another patch around every other corner.