New Tech vs Old Tech: From Copy Protection to Ransom Notes
There was a time when “security” meant something wonderfully simple.
You wrote an application, burned it to a CD (or three), and your biggest fear was that someone might copy it without paying you. Maybe they’d share it with a friend. Maybe they’d crack the license check. Maybe if things got serious you’d find your software running on a machine that had absolutely no business running it.
So, you protected the application.
You obfuscated binaries. You added license files tied to hardware IDs. You hid strings, checksums, and the occasional “if this fails, exit dramatically” block of code. Security was inward facing. Defensive. Slightly paranoid, but manageable.
Fast-forward to today, and that version of security feels… almost wholesome.
Because now, nobody really wants to steal your application.
They want your data, your infrastructure, your credentials, and if they’re feeling ambitious your entire business continuity plan.
The Old Model: Guard the Crown Jewels
In the “old tech” world, software lived somewhere you could point at, something tangible, A server, A desktop, A box under someone’s desk humming heroically.
Threats were mostly:
- Piracy
- Tampering
- Reverse engineering
- That one user who didn’t buy a license
Security was about control. If you could control distribution, execution, and licensing, you were winning. Attacks were deliberate, slow, and usually required effort. Someone had to care enough to target you.
And most didn’t.
The New Model: Assume the Doors Are Already Rattling
Modern systems flipped the problem inside out. Don’t share passwords, protect the keys to the kingdom, every word, every thought a secret. Have I shared too much on social media, can information out there be used to target my kingdom?
Your application now lives:
- In containers you didn’t handcraft
- On networks you don’t fully own
- Exposed to the internet by default
- Talking to other systems 24/7
And the threats? They don’t care who you are.
Ransomware doesn’t wake up in the morning thinking, “Today, I’m going after a fintech platform.”
It scans. It probes. It waits. It tries again.
If you exist, you’re a candidate.
Security today isn’t about preventing copying—it’s about preventing extortion.
From “Don’t Steal My App” to “Please Don’t Brick My Company”
That shift changes everything.
Instead of asking:
“How do I stop someone from running this without permission?”
You’re now asking:
- How do I stop lateral movement?
- What happens if credentials leak?
- Can this service talk to things it shouldn’t?
- How fast can I recover when—not if—something breaks badly?
Backups went from “nice-to-have” to an “existential requirement.”
Logs went from “debugging aid” to “forensic evidence.”
Updates went from “when we get to it” to “why is this not patched yet?”
And the attacker is no longer a curious developer with too much time. It’s automation. Relentless, unbothered automation.
The Humour (Because We Need It)
There’s something faintly absurd about modern security advice.
- “Assume breach.”
- “Zero trust.”
- “Rotate secrets.”
- “Never expose anything.”
Meanwhile, you’re just trying to deploy a feature before the sprint ends.
In the old days, security failures meant a cracked license.
Today, they mean a Teams message that starts with:
“Does anyone know why all the files have a new extension?”
Old Tech was simple. New Tech is honest.
Here’s the uncomfortable truth: modern security is harder because systems are more honest about reality.
Old systems felt secure because they were isolated.
New systems acknowledge that isolation is mostly an illusion.
The perimeter is gone. Trust is contextual. Everything talks to everything else. And security is no longer a feature it’s a continuous discipline.
You don’t “finish” securing a system anymore. You just keep adjusting it as the threat model evolves.
Final note from the Stack
If there’s a takeaway here, it’s this:
Security didn’t get worse.
It got real.
We moved from guarding software like a prized object to defending systems like living organisms constantly exposed, constantly adapting.
And yes, it’s more work.
But at least nobody’s cracking your license key anymore.
They’re far too busy trying to encrypt your backups.
“Stay vigilant, stay curious and always watch your back”
Andrew van Dijk
Systems Architect
