Hosting in Iraq: Local, Regional or Cloud?
Hosting in Iraq is changing. A practical method for IT leaders to place each system locally, regionally or in the cloud, with resilience and an exit plan.
Firewalls, SSL VPNs and email gateways were exploited again in November 2026. A practical plan to find, patch, lock down and monitor your edge devices.

In the first two weeks of November 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added several actively exploited flaws to its Known Exploited Vulnerabilities (KEV) catalogue. Most of them sat on the network edge: a Check Point permission flaw, a SonicWall SSL VPN single-factor authentication weakness, two Barracuda Email Security Gateway flaws and a Cisco BroadWorks issue. These are the boxes that keep an organisation connected, and in my experience they are often the least watched. This article sets out a practical plan for edge device security: find your devices, patch them quickly, lock them down and monitor them.
Firewalls, VPN concentrators, email gateways and SD-WAN controllers share three traits that attackers like. They face the internet by design. They hold credentials, sessions and traffic for the whole organisation. And they often run for years with little attention once they are configured and working.
The November alerts show the pattern clearly:
| Date (2026) | Product area | What CISA listed |
|---|---|---|
| 6 Nov | SonicWall SonicOS SSL VPN | Use of single-factor authentication (CVE-2026-19868) |
| 10 Nov | Barracuda Email Security Gateway | Authentication bypass and OS command injection |
| 10 Nov | Cisco BroadWorks | XML external entity (XXE) flaw |
| 10 Nov | Microsoft Outlook | Exploited Outlook flaw |
| 13 Nov | Check Point | Incorrect permission assignment for a critical resource (CVE-2026-123039) |
Two more points are worth noting. According to The Hacker News, the Cisco BroadWorks flaw was fixed in August 2026 but was still being exploited in November. In other words, patches existed and had not been applied. The same report notes that in late October Cisco disclosed active exploitation of Catalyst SD-WAN (CVE-2026-20127, rated CVSS 10.0) and Secure Firewall ASA/FTD.
I want to be fair here. Every vendor ships flaws, and the vendors above published fixes and advisories. What decides your risk is not the logo on the box but how quickly your own team notices and acts.
The identity angle matters too. Sophos's State of Ransomware 2026 found that exploited vulnerabilities are no longer the top root cause after three years in first place. Email now is, and identity-based attacks drive most incidents. A VPN that accepts a password alone is exactly the door those stolen credentials open.
You cannot patch a device you have forgotten. Build a simple register of every internet-facing system:
For each one, record the model, OS or firmware version, support contract status, public IP addresses and a named owner. A spreadsheet is fine to start with. The named owner is the most important column, because an alert with no owner is an alert nobody acts on.
In the Kurdistan Region and wider Iraq, I often see small IT teams inherit appliances from a previous project or supplier, with little documentation. If that sounds familiar, scan your own public IP ranges and compare the results with what you think you have. Surprises are common.
Check the KEV catalogue every week and compare it against your register. Treat any KEV entry that matches an edge device as an emergency change, measured in days. It should not wait for the next quarterly maintenance window.
US federal agencies typically get around two weeks to remediate KEV entries; for the BroadWorks flaw the deadline was 24 November 2026. That is a reasonable benchmark for everyone else. For an exposed VPN or firewall, I would aim to move faster.
The quiet blocker in many organisations is the support contract. When vendor support lapses, firmware downloads often stop, and a team that wants to patch simply cannot. Budget for appliance support renewals the way you budget for electricity: as a running cost, not an optional extra.
Many edge compromises start with an interface that should never have been reachable. A few changes remove a large share of the risk:
If you work to ISO/IEC 27001, these steps map naturally onto its controls for asset management, access control, technical vulnerability management and logging. The standard does not tell you which firewall to buy. It asks you to know your assets, manage their weaknesses and be able to show evidence that you do.
Once a flaw is known to be exploited, patching closes the door. It does not tell you whether someone already walked through it. After applying an emergency fix:
For the longer term, send appliance logs to a central place. Use a SIEM if you have one, or at least a remote syslog server that the device itself cannot alter. Start with three alerts: admin logins from new IP addresses, configuration changes, and logins outside working hours.
Do not forget email, since that is where many incidents now begin. Patch Outlook and Office quickly, consider blocking outbound NTLM and SMB traffic to the internet, and train staff on "paste this command" lures.
Researchers have reported a 2026 campaign aimed at Iraqi government officials. The attackers used a compromised legitimate government website and a fake "Webex for Government" meeting as a ClickFix lure, tricking users into running a command themselves. No firewall rule stops a user who has been persuaded to do the attacker's work.
Finally, keep offline or immutable backups of appliance configurations and critical systems, and practise restoring them. A clean configuration backup turns a compromised firewall from a crisis into a rebuild.
When a KEV alert matches one of your edge devices, this is the timeline I would follow:
| Timeframe | Actions |
|---|---|
| Within 24 hours | Confirm the device and version are affected. Read the vendor advisory. Apply mitigations (restrict management access, disable the affected feature). Tell management. |
| Within 72 hours | Apply the vendor fix in an emergency change. Review logs for signs of compromise. Reset admin credentials and VPN secrets. |
| Within 2 weeks | Run the vendor's integrity checks. Confirm MFA on all access. Update the asset register and record lessons learned. |
And a standing checklist to run every month:
The devices that protect your network are now among the most targeted parts of it. You do not need a large team to defend them well. You need a complete list, a short patch clock, MFA everywhere and someone reading the logs. If you do only one thing this week, build the register of your internet-facing devices and check it against the KEV catalogue.
🤖 Researched and drafted with AI assistance, guided by my editorial standards. Spotted something wrong? Tell me.