Skip to main content

Secur-IT Data Solutions – Toronto – Canada

On-premises SharePoint security: a small server room with one rack server pulled forward and a single red status light among green lights

On-Premises SharePoint Security After the House of Commons Breach

On-premises SharePoint security moved up the agenda in Ottawa in August 2025, when staff at the House of Commons learned that someone had broken into a database used to manage their computers and phones. The way in, according to the internal email, was a recent Microsoft vulnerability.

The House never named the flaw. It did not have to for the lesson to land. An office that cannot say which servers it runs, or how fast they get patched, is exposed every time a new alert comes out.

This post sets out what was confirmed about the House of Commons breach, what the Canadian Centre for Cyber Security has warned about SharePoint Server since then, and the on-premises SharePoint security steps that keep your own servers ahead of the next alert.

What Happened at the House of Commons

CBC News reported on August 14, 2025 that it had obtained an internal email telling House of Commons staff about an information breach. The email said a threat actor had exploited a recent Microsoft vulnerability to gain access to a database containing information used to manage computers and mobile devices. The attack took place on a Friday, and staff were told the following Monday.

BleepingComputer reported the same day that the data taken included employees’ names, job titles, office locations and email addresses, plus details about House-managed computers and mobile devices.

The Canadian Centre for Cyber Security told BleepingComputer it was aware of the incident and working with the House of Commons to provide support. It did not say who was behind the attack, noting that attribution of a cyber incident is difficult.

Was It SharePoint? What Is Confirmed and What Is Not

Here the record needs care. Neither the House of Commons nor the Communications Security Establishment disclosed the specific vulnerability, BleepingComputer reported. Some outlets, including Security Affairs, suggested a link to the SharePoint Server flaw CVE-2025-53770, while also noting that the exact flaw was not disclosed.

So treat the SharePoint link as reported, not confirmed. What is confirmed is the timing.

The Canadian Centre for Cyber Security issued alert AL25-009 on July 20, 2025, less than a month before the House breach. That alert said the vulnerability appeared to affect all versions of on-premises SharePoint Server, and that the Canadian Centre for Cyber Security was aware of exploitation happening in Canada.

The same alert, updated on August 19, 2025, states plainly that SharePoint Online in Microsoft 365 is not impacted. That distinction matters for every Canadian office.

If your files live only in Microsoft 365, this specific flaw was Microsoft’s to fix. If you run your own SharePoint server, on-premises SharePoint security is your job.

On-Premises SharePoint Security in 2026: The Alerts Kept Coming

The 2025 flaw was not a one-off. In 2026 the Canadian Centre for Cyber Security issued several more alerts about SharePoint Server, and most of them describe active exploitation:

  • AL26-005, March 20, 2026: a critical flaw, CVE-2026-20963, that could allow an unauthenticated remote attacker to run code over the network. The alert says the Canadian Centre for Cyber Security had observed exploitation and urged immediate action.
  • AL26-015, July 2, 2026: CVE-2026-45659, a critical flaw that could allow a low privileged remote attacker to run code. The alert notes it was added to the CISA Known Exploited Vulnerabilities catalog on July 1, 2026.
  • AL26-017, July 15, 2026: three critical flaws in one release. The alert quotes Microsoft as aware of exploitation of CVE-2026-56164, which CISA added to its catalog on July 14, 2026.
  • AL26-023, September 24, 2026: CVE-2026-65660, which the Canadian Centre for Cyber Security says is under active exploitation and could let an authenticated attacker run code on vulnerable servers.

That last alert adds a warning worth reading twice. Chained with other SharePoint flaws, CVE-2026-65660 can reach code execution before any login on servers configured to permit anonymous access. The alert adds that organizations that have not fully applied earlier SharePoint updates face higher risk.

In other words, each missed patch makes the next flaw worse. Good on-premises SharePoint security is not a single fix. It is a habit of applying every update, every month.

End of Support Changes the Math

There is a second problem in the 2026 alerts. The Canadian Centre for Cyber Security says SharePoint Server 2016 and SharePoint Server 2019 reached end of life in mid-July 2026, and it urges organizations to move to a supported version.

Microsoft’s own lifecycle page for SharePoint Server 2019 lists the extended support end date as July 15, 2026. After that point, new flaws in those versions will not get the regular security updates that every alert above depends on.

If your office still runs one of those two versions, on-premises SharePoint security now starts with a migration plan. The fixed builds listed in AL26-023 are the last word on what “patched” means for each product line, so check your build number against that table.

Why On-Premises SharePoint Security Is Hard for Smaller Offices

Many Ontario offices that still run SharePoint Server set it up years ago for a document library, an intranet or a line of business app. It has kept working quietly ever since.

That quiet is the risk. Three patterns are common:

  1. Nobody owns the server. The person who installed it has moved on, and the IT provider patches Windows but not SharePoint itself.
  2. It faces the internet. Remote staff or partners needed access once, so the site was published, and it never came back inside.
  3. Secrets never change. Service account passwords and the server’s machine keys are the same ones set on day one.

The 2025 alert speaks to that third point directly. It recommends rotating any credentials and secrets used on impacted servers, including service accounts, and rotating SharePoint’s ASP.NET machine keys and restarting IIS. A patch closes the hole, but stolen keys can still let an attacker back in.

A Practical On-Premises SharePoint Security Checklist

The recommended actions in AL26-023 and AL25-009 line up well with what a small team can manage. Here is how we would put them in order for a typical office:

  1. Find every server. List every on-premises SharePoint Server you run, with its version and build number, and mark which ones are reachable from the internet.
  2. Patch to the fixed build. Compare each build with the fixed versions in the latest alert, then apply the latest Microsoft security updates.
  3. Plan the move off 2016 and 2019. Both versions are past end of life, so set a date to migrate to a supported version.
  4. Cut the exposure. Reduce internet access to the server and restrict Central Administration and other management pages.
  5. Tighten accounts. Remove unused accounts and require multi-factor authentication for administrators and privileged users.
  6. Turn on AMSI. Enable the Antimalware Scan Interface integration in SharePoint and, where feasible, set its request body scan mode to full.
  7. Rotate secrets after any exposure. Change service account credentials and machine keys if a server sat unpatched while a flaw was being exploited.
  8. Watch the logs. Review SharePoint, IIS, endpoint and sign-in logs for web shells, unusual admin activity and suspicious access to machine keys.

If a server was internet-facing and unpatched during an active campaign, AL25-009 recommends assessing it for compromise and considering isolating it until patching and threat hunting are complete. Patching alone does not prove nobody got in, which is why on-premises SharePoint security has to include a look back as well as a fix.

What Canadian Privacy Law Expects After a Breach

The House of Commons data was employee information, which is a reminder that a breach does not need customer records to count. For private sector organizations covered by PIPEDA, the Office of the Privacy Commissioner of Canada explains that a breach of security safeguards must be reported to the OPC when it is reasonable to believe it creates a real risk of significant harm to an individual.

The OPC’s guidance adds that affected individuals must be notified in that case, and that organizations must keep records of all breaches of security safeguards for two years, whether or not they meet the reporting threshold. Good on-premises SharePoint security makes it far less likely you ever need to file one.

Where Secur-IT Data Fits

Our team runs managed cybersecurity for Toronto and GTA businesses, and on-premises SharePoint security draws on two parts of that work.

Our vulnerability assessment service covers internal and external network vulnerability scans, risk prioritization with CVSS scoring, and patch management guidance and validation. Quarterly rescans are common, and continuous scanning is available for higher-risk environments, so a new SharePoint alert can be checked against your servers quickly.

Our 24/7 managed cybersecurity services add threat monitoring and detection, managed detection and response, penetration testing, and incident response and recovery. Your IT provider keeps running the server, and our team watches it and works alongside them.

Frequently Asked Questions

Q: What is on-premises SharePoint security?

On-premises SharePoint security is the work of protecting SharePoint Server installations that your organization runs itself: patching them to the fixed builds, limiting internet exposure, controlling admin accounts, and monitoring for signs of attack.

Q: Was the House of Commons breach caused by SharePoint?

That is not confirmed. The House of Commons said a recent Microsoft vulnerability was exploited but did not name it. Some outlets linked the breach to CVE-2025-53770, a SharePoint Server flaw, without confirmation.

Q: Is SharePoint Online in Microsoft 365 affected by these alerts?

Alert AL25-009 from the Canadian Centre for Cyber Security states that SharePoint Online in Microsoft 365 is not impacted by that vulnerability. The 2026 alerts list only on-premises SharePoint Server products as affected.

Q: Is SharePoint Server 2019 still supported?

No. Microsoft’s lifecycle page lists July 15, 2026 as the extended support end date for SharePoint Server 2019, and the Canadian Centre for Cyber Security urges a move to a supported version.

Q: What should we do first if we run SharePoint Server?

List every server with its version and build, find the ones exposed to the internet, and patch them to the fixed builds in the latest alert. Then restrict admin access, turn on AMSI and review the logs.


If you want to know which of your servers an attacker could reach today, and what to patch first, our team at Secur-IT Data can walk you through it.

References

  1. BleepingComputer: Canada’s House of Commons investigating data breach after cyberattack
  2. Canadian Centre for Cyber Security: AL25-009 Vulnerability impacting Microsoft SharePoint Server
  3. Canadian Centre for Cyber Security: AL26-017 Critical vulnerabilities impacting Microsoft SharePoint Server
  4. Canadian Centre for Cyber Security: AL26-023 Vulnerability impacting Microsoft SharePoint Server
  5. Microsoft Lifecycle: SharePoint Server 2019

Ready to Strengthen Your Cybersecurity?

Secur-IT Data Solutions is a Toronto-based MSSP providing enterprise-grade cybersecurity for Canadian businesses. Whether you need OT security, AI threat protection, penetration testing, or full managed security services, our team is ready to help.

Talk to our team:

Share article

Let’s Connect

Need advice or you have an inquiry to discuss? We would love to hear from you.

Related Cybersecurity Articles