PlatformThe PlatformWho We ServeInsightsCapabilitiesEnterprise Expense ManagementCarrier ServicesManaged Mobility ServicesManaged ServicesPartnersFirefly Partner NetworkWireless InnovationsCompanyAboutCareersTalk to Our Team
← All insights

Breached! Security Lessons from 2026 and What You Can Do

By Phil Hollenberg, CCSKCybersecurity Solution Developer, OPTRIC

As my high school football coach used to say, “It’s all about the fundamentals.”

Three notable cyber incidents from 2026 show why those fundamentals still matter—and why limiting the blast radius deserves to come first.

Three incidents and the lessons they leave

Instructure / Canvas (April–May): Instructure says attackers exploited an issue related to its Free-For-Teacher accounts. It detected unauthorized activity on April 29, took containment measures, then identified related activity on May 7 and temporarily took Canvas offline. [1] The lesson: containment needs to address the underlying access path, not just the accounts already identified.

Qilin / Check Point VPN (May–June): Check Point reported exploitation of an authentication-bypass flaw affecting VPN deployments using the deprecated IKEv1 protocol, with activity observed from May 7 before its June 8 advisory. One case involved post-compromise activity associated with a Qilin ransomware affiliate; Check Point assessed the actor’s use of Qilin with medium confidence. Establishing a VPN session did not by itself grant access to internal resources—additional activity was required. [2] Retiring legacy configurations and restricting what remote access can reach both matter.

JadePuffer (reported in July): Sysdig assessed this as the first documented ransomware operation driven end-to-end by an AI agent. It reported initial access through a known Langflow vulnerability on an internet-facing instance, credential harvesting, and an attack on a separate production database server. The origin of the root credentials used on that database server is unknown. [3] The lesson is still familiar: reduce exposure, protect secrets, and limit what a compromised system can reach.

The common thread is the fundamentals

The weaknesses are strikingly ordinary: exposed systems, vulnerable or outdated configurations, and credentials within reach of an attacker. AI-driven automation can chain those weaknesses together, but it does not make the fundamentals less relevant.

These reports do not establish the same root cause in every incident. They do give us a practical question to ask: once an attacker gets in, how much of the business can that attacker reach?

Why blast radius comes first

For a business with limited time and resources, I would start with segmentation. You still need to prevent attackers from getting in. But if one system is compromised, it should not give them a path to everything else.

Separate critical systems and data, restrict access between them, and check that those restrictions work. That gives the other fundamentals a stronger foundation. Patching closes known entry points. Strong authentication protects accounts. Secrets management limits credential exposure. Segmentation helps contain the damage when a control fails.

What you can do now

  1. Segment your network. Limit which systems and accounts can reach critical data and services, so one compromised system does not have a path to everything. Test those boundaries.
  2. Shrink your internet exposure. Know what’s reachable from the internet and remove or lock down anything that doesn’t need to be. Prioritize fixes for exposed, vulnerable systems.
  3. Retire legacy configurations. Review outdated protocols and unsupported systems. Apply available security updates and remove configurations you no longer need.
  4. Use phishing-resistant MFA. Prioritize remote access and admin accounts, then extend coverage wherever supported.
  5. Manage secrets properly. Keep passwords and API keys out of code and unsecured files. Restrict access to stored secrets and rotate credentials exposed in an incident.
  6. Protect and test your backups. Keep immutable copies and practice restoring them.
  7. Rehearse your response. Test how the business will operate while IT recovers. Hasbro reported activating continuity plans after identifying unauthorized network access on March 28, allowing orders and shipping to continue while it addressed the incident, with possible delays. Its disclosure did not identify the entry point. [4]

How OPTRIC can help

Contact OPTRIC for a conversation about your security gaps and priorities. After the meeting, you will receive a follow-up in-depth email or document with recommendations prioritized by the criticality of the gaps discussed, security tools that are not effective, and your security priorities. It will include suggested next steps.

To learn more about how OPTRIC can help with cybersecurity, contact our team at optric.com/cybersecurity/.

As my coach used to say, “It’s all about the fundamentals.”

Update — October 29, 2026

The October 21 PHP security disclosures are a practical example: two critical vulnerabilities could allow unauthenticated remote code execution. According to Wiz Research, PHP powers roughly 70% of websites, illustrating the potential reach of vulnerabilities in software organizations may not realize they depend on. PHP can run inside websites, applications and third-party products, so a business may have exposure without realizing that it relies on PHP. Know those dependencies, work with hosting and software providers to apply security updates promptly, and restrict access between systems to help contain a compromise. Visibility identifies what needs attention; patching addresses the vulnerabilities; segmentation limits where an attacker can go. Segmentation does not replace security updates.

New vulnerabilities are another reminder that we cannot rely on prevention alone. Businesses need to patch promptly and limit what a compromised system can reach. Microsegmentation can help reduce that blast radius by restricting connections between workloads and critical systems. It still requires careful design, testing and ongoing management; it does not replace patching, strong authentication or recovery planning.

As you plan for 2027, ask where one compromised machine could expose the rest of the business. Identify the systems that matter most, review the access they need, and prioritize the gaps. Contact your OPTRIC account manager or me to discuss where microsegmentation may fit in your security priorities and budget.

Sources

[1] Instructure, Security Incident Updates. https://instructure.my.site.com/ChannelPartners/s/security-incident-updates

[2] Check Point, Security Advisory — Active Exploitation of Check Point VPN Authentication Bypass, June 8, 2026. https://blog.checkpoint.com/security/check-point-releases-important-hotfix-for-vulnerabilities-in-deprecated-ikev1-vpn-protocol/

[3] Sysdig, JADEPUFFER: Agentic ransomware for automated database extortion, July 1, 2026. https://www.sysdig.com/blog/jadepuffer-agentic-ransomware-for-automated-database-extortion

[4] Hasbro, Form 8-K, April 1, 2026. https://investor.hasbro.com/static-files/2b0ed4ce-8a34-451f-8b29-637e73344b57