NICS Ltd.

10/23/2026

If you are running old public facing PHP it's time to update it! Especially if you are self hosting a PHP password manager or SharePoint make sure you are getting those patched

AL26-026 - Critical vulnerabilities impacting PHP - CVE-2026-109618 and CVE-2026-109619

05/28/2026

Six months past Windows 10 end-of-support. The clock has been ticking for half a year now.

Final post in this series, and the most useful one. The 30-day plan any small Saskatchewan business can actually run.

Week 1: Walk every desk. Find every Windows 10 machine. Don't trust the old IT inventory list, use your eyes. The reception PC. The laptop in the bag. The shop computer. The kiosk.

Week 2: Sort the list into three buckets. PCs from the last 4-5 years probably qualify for free Windows 11. Older hardware needs replacement. Anything running specialized software (CAD, accounting, lab equipment) needs a compatibility check before you touch it.

Week 3: Start the upgrades. Lowest-risk machines first. The spare laptop. The reception PC. Build confidence and find the surprises before you touch the production systems.

Week 4: Replace what can't upgrade. New hardware you'd have bought soon anyway. Plan one or two days per machine of mild disruption.

Throughout the whole 30 days: actually verify your backups. Pick a random file. Try to restore it. If you can't, your backup isn't working. Most ransomware victims find this out at the worst possible moment.

What this plan fixes: the foundation every other security tool sits on top of.

What it doesn't fix on its own: phishing, weak passwords, network segmentation. There's more to security than the operating system. But every other piece works better when the OS underneath isn't a known liability.

If you'd rather just hand this to someone, that's what we do at NICS. Saskatoon office, local team, 13 years of doing exactly this. But you don't need us to follow the plan.

You just need to start. 🛠️

What's your week 1 looking like?

05/27/2026

Six posts deep into a series about everything that goes wrong with Windows 10 after end-of-support. Time to flip it and talk about what actually goes right when you upgrade.

Windows 11 isn't just safer. It's nicer to use.

Things you'll actually notice on day one:

-> Faster wake from sleep. Open the laptop, start working. Less time staring at a black screen.
-> Better video calls. Background blur, eye contact correction, and noise removal built right into the operating system. No extra software.
-> Snap layouts. Pull a window to the corner and a little menu appears showing you exactly how to arrange your other windows. Sounds small. Saves real minutes every day.
-> A cleaner Start menu that doesn't look like it was designed by a committee.
-> Better battery life on laptops in most cases.

Things you won't notice but matter:

-> TPM 2.0 hardware-level security built in.
-> Modern protections that make it much harder for malware to gain admin rights.
-> Actual ongoing security patches from Microsoft. The thing Windows 10 stopped getting six months ago.
-> Better performance on the same hardware in many cases. The OS uses memory and CPU more efficiently.

The Saskatchewan reality: if your business has computers from the last 4-5 years, most of them probably qualify for the upgrade for free. The ones that don't were going to need replacing in the next year or two anyway. Nothing here is wasted budget.

The real choice isn't "upgrade or stay on Windows 10."

The real choice is "upgrade on a Tuesday morning, at your own pace, with coffee in hand, while your team works around you" OR "upgrade at 2 AM after a ransomware attack has shut everything down."

Same upgrade. Different price. The Tuesday morning version costs less in money, time, and dignity. 💻

Final post in the series next week: the 30-day plan to get every Windows 10 machine off your network. Save this post if you'd find that useful.

What's actually holding you back from upgrading? Honest answers welcome.

05/21/2026

"We have antivirus."

That's what most small business owners say when asked about cybersecurity. And in 2026, on a Windows 10 machine that Microsoft stopped patching six months ago, that's like saying "we have a smoke alarm" while the kitchen is on fire.

Antivirus does one thing well: it catches things it has seen before. Known viruses. Known patterns. Known bad files.

Modern attacks aren't designed to look like viruses. They're designed to look like you.

Here's what actually happens on a typical small business attack today:

The attacker doesn't drop a virus. They use the same tools your IT person uses. PowerShell. Built-in Windows commands. Legitimate Microsoft software, just used for bad reasons.

The antivirus sees PowerShell running and goes "yep, that's normal."

Then once they have admin rights (which they usually get within hours on an unpatched Windows 10 machine), they just turn the antivirus off. Or uninstall it. With admin rights they can do basically anything.

Many attacks even start before the antivirus fully loads at startup. By the time your security software wakes up, the attacker is already in the system.

Add to all that: on unsupported Windows 10, the operating system has known unpatched holes. The antivirus is sitting on top of a foundation with cracks running through it. No software fixes that.

I'm not saying don't have antivirus. You should. It catches the easy stuff and that matters.

I'm saying don't tell yourself the antivirus is your security plan. It's the smoke alarm. You also need:

-> An OS that's still getting security patches (= Windows 11, in most cases)
-> Real endpoint protection (the kind that watches behavior, not just files)
-> Tested backups that are actually offline
-> Multi-factor authentication on email and the bank
-> Network segmentation so one infected machine doesn't burn the whole house

This is post 6 of our Windows 10 series. One more coming on what Windows 11 actually fixes, and then a 30-day plan you can run yourself. 🛡️

05/18/2026

This is what an actual ransomware attack looks like, hour by hour.

Hour 0, Monday morning: Sarah, the accountant, gets an email about a vendor invoice. She opens the PDF in Outlook's preview pane. Nothing visible happens. The malware quietly drops a small program on her machine.

Hours 1 to 4: That program calls home and downloads more tools. It scans the network. It finds a Windows 10 machine that's missing security updates because Microsoft stopped issuing them. It breaks in. The attacker now has admin rights to the whole office.

Hours 4 to 12: They quietly walk through the network. Reading documents. Finding the QuickBooks file. The customer database. The shared drive with all the project plans. They copy interesting files to their own servers across the world. Nobody notices a thing.

Hours 12 to 20: They locate the backups. The external hard drive someone plugs in once a week. The NAS in the corner of the server room. They delete or encrypt all of it.

Hours 20 to 24: They press the button. Every file on every Windows machine gets locked.

Hour 24, Tuesday morning: The owner walks in. Nothing works. The phones start ringing.

The whole sequence took the attacker maybe a few hours of focused work. Most of it ran automatically.

The cost to the business? Often the business itself.

Here's the thing nobody tells you: this entire chain depends on that one unpatched Windows 10 machine at hour 4. Remove it from the network or upgrade it, and the whole story collapses before lunch.

Question for the comments: when was the last time your business mapped out exactly which devices are still running Windows 10?

05/15/2026

79 stores. Closed for a week. No prescriptions. No retail. Nothing.

That's what a single ransomware attack did to London Drugs in 2024.

If you live anywhere in Western Canada, you probably noticed. Or you couldn't fill a prescription. Or you couldn't pick up the camera battery you needed for the wedding on Saturday.

The attackers wanted $25 million. London Drugs said no.

Good for them.

The cost of saying no was still enormous:

-> Every store dark for over a week
-> Employee data stolen and threatened with public release
-> System rebuilds that ran for months
-> Reputation damage that lingered into 2025 reporting
-> Sales nobody got back

Now think about what one week of being completely offline does to a small business. A 5-person shop in Saskatoon. A 17-person engineering office. A medical clinic in Prince Albert.

Most small businesses can't survive that.

The numbers say roughly 1 in 5 close within six months of a major attack. Many more limp along for two years and then quietly fold. Customers find someone else. Vendors get nervous. Insurance gets expensive. The math just stops working.

The London Drugs attack started the way most do. Someone clicked something. Or a system wasn't fully patched. Or a credential was reused.

Boring causes. Catastrophic results.

Here's the question I want you to actually answer, even if just to yourself:

If your business went completely offline for 7 straight days starting tomorrow morning, how would you make payroll?

If you don't have a clear answer to that, that's the conversation you and your IT person should be having this week.

This is post 4 of a series on the real risks of running Windows 10 after end-of-support. More soon. 🔐

05/12/2026

58 gigabytes.

That's how much data the Akira ransomware group claims they took from Ardene back in January 2025.

If you've shopped at Ardene anywhere in Canada, that's a name you know. Hundreds of stores across the country. A real Canadian success story.

Then someone got in.

Customer information. Financial records. Employee personal details. Gone.

The fallout: stores running on disrupted systems, shipping delays customers noticed and remembered, customer service backlogs, thousands of letters going out to notify people their data was stolen, and recovery costs that don't show up in any press release.

The actual attack? Almost certainly started with something boring. A phishing email. A reused password. Some unpatched system somewhere in the chain.

Ardene has resources. Real IT staff. Security tools and the budget to use them. They still got hit.

Now imagine the same playbook applied to a 17-person engineering firm in Saskatoon. A construction company in PA. A medical clinic in Regina. A law office on 8th Street.

That's the gap. The attacks that hit big companies in 2025 use the same techniques that work on small Saskatchewan businesses today. The only meaningful difference is press coverage.

Honest question for the comments: if a 58 GB data theft hit your business tomorrow, would you know what was actually in those 58 GB?

That's what most owners can't answer. And that's the problem.

05/07/2026

Picture an unlocked door in a rough part of town.

That's a Windows 10 PC after October 14, 2025.

Every day someone walks past. Jiggles the handle. Most keep walking. Eventually one stops. Tries the door. It opens.

That's how it starts.

Not with a Hollywood hacker in a hoodie. Not with some complicated movie-style cyber attack.

It starts with a scan. A list of internet addresses. Software that automatically tests for known weaknesses on millions of computers per hour.

If your computer is on that list and it's running Windows 10, the test eventually finds something. The receptionist clicks an email. A laptop on the kitchen counter checks for updates that never come. A printer driver from 2019 has a flaw nobody bothered to fix because nobody is fixing things anymore.

One door opens.

Then the bad part.

Within hours, the attacker is on every Windows machine in your office. They've copied your client files. They've got the bank login. They've found the QuickBooks data.

You don't know any of this yet.

You'll find out Monday morning when nothing turns on. 🔒

This is post 2 of our series on Windows 10 end-of-support, written for Saskatchewan business owners who don't want to translate IT-speak into English.

If you've got even one Windows 10 machine still running at the office, comment "next" below and I'll tag you when post 3 drops with the first real Canadian example.

05/05/2026

Six months ago, Microsoft pulled the plug on Windows 10.

A lot of Saskatchewan businesses kept right on using it. Some didn't get the memo. Some shrugged. Both groups are running on borrowed time.

I'm running a 8-part series breaking down what actually happens when attackers find an unsupported Windows 10 machine on a small business network. No jargon. Just real Canadian stories and the steps any owner can take.

If you've still got even one Windows 10 PC at the office, follow along.

Honest question to start: are you still on Windows 10 anywhere, or have you fully moved on?

04/28/2026

Last week I posted about quantum computing and why it's a real threat to business data security. A lot of people had the same question:

"Okay, I get it. But what are we supposed to DO about it?"

Fair question. The answer has a name: post-quantum cryptography. And it's not as complicated as it sounds.

Here's the simplest way I can explain it.

Right now, the encryption that protects your email, your banking, your VPN, your cloud files — it all works because it's built on math problems that regular computers can't solve fast enough to be useful. That's what keeps the bad guys out. Your data is technically visible, but cracking the math would take thousands of years. So nobody bothers.

Quantum computers change that equation. They solve those specific math problems fast. Really fast.

So the smartest cryptographers on the planet spent eight years building new encryption algorithms based on completely different math. Math that neither regular computers NOR quantum computers can crack efficiently.

That's post-quantum cryptography. New locks that quantum keys can't open.

And it's not theoretical. NIST — the U.S. standards body — finalized the first three standards in August 2024. Google already has it built into Chrome. Microsoft has rolled it into Azure and Windows updates. Cisco is shipping quantum-safe firewall firmware later this year.

Here's what the timeline looks like:

→ January 2027: All new U.S. national security systems must use quantum-safe encryption
→ 2030: All existing applications must be migrated
→ 2035: Everything must be quantum-resilient. No exceptions.

Canada has its own deadlines — federal departments had to submit migration plans by this month.

"But I'm not the government." I hear you. But here's the thing — your cyber insurance will start asking about this. Your bigger clients will require it in vendor assessments. And the tools you already use — Microsoft 365, Chrome, your firewall — will all ship with PQC built in through normal updates.

The key is making sure you're not running old, unsupported systems that will never get those updates. If you're still on Windows 10, or an aging server with no upgrade path, you're not just behind on today's security. You're locked out of tomorrow's.

That's exactly the kind of thing proactive IT management catches before it becomes a crisis.

At NICS we're already building post-quantum readiness into our technology planning for clients. If you missed last week's post on why quantum computing matters for your business, scroll back on our page — it's worth the read.

And if you want to talk about where your business stands, reach out. No pressure, no pitch. Just a straight conversation.

nics.ca | 306-244-3551