Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Managed Security Services can give security teams greater visibility and access to specialized expertise, but finding a threat is only one part of incident response. Once an alert becomes an incident, the operating model between an internal security team and its managed security service provider (MSSP) becomes critical.

You think twice before clicking a link in an unexpected email. Do you do the same for a message in Microsoft Teams? A new message arrives in your Teams chat with the familiar notification sound, a participant’s name, and a link. It feels like a colleague, not a stranger. That feeling is the opening attackers look for. Two things decide whether that message does harm. Can the channel stop it before it reaches your user? And if it gets through, does the user recognize the lure and know what to do?

Last week, US prosecutors indicted three people who allegedly used AI to impersonate both a CEO and a law-firm attorney on live calls to steal about $129 million from companies worldwide. Employees first heard a familiar executive’s voice, then an authoritative “attorney” telling them where to wire the money. Victims allegedly included hospital systems, a bank, a fintech, and a mutual fund company.

For the last two weeks, ARTEX has been on every CISO’s radar, and every blue team has had multiple meetings about it. Honestly, most of what has been said deserves to be ignored. The threats are serious enough to take seriously, but giving ARTEX credit for rewriting offensive security overnight is absurd. What ARTEX did is cheaper and more boring than that, and the boring version is what you should actually be worried about.

Doctor Anywhere is a Singapore healthcare company that reports over three million users across Southeast Asia. Adept Health Pte. Ltd. is its subsidiary that administers corporate benefits for organisations. The company announced the incident in a statement that AsiaOne reported on November 6, 2026. Income Insurance published its own advisory the same day, after Adept Health notified it on November 2, 2026.

Every engineer reading this has at least once committed a secret by accident, noticed within the hour, force-pushed the fix, and gone back to work slightly embarrassed. The dangerous part is that the “fix” we all learned from the first Stack Overflow answer we googled does almost nothing. The next 1,500 words are about why deleting a leaked secret is theatre, how easily attackers find the ones we did not catch, and what posture actually bounds the damage when a credential do.

It's been 20 days since the PHP project disclosed PHP2Shell (CVE-2026-109618 and CVE-2026-109619), and many organizations have already put an action plan in place to patch their own environments. Regulators are also demanding faster responses than ever: U.S. federal agencies had three days to apply fixes under CISA BOD 26-04, and frameworks like PCI DSS, DORA, and NIS2 all set firm expectations for timely remediation.

Insights from 217 IT and cybersecurity leaders across the retail sector in 17 countries whose organizations were hit by ransomware in the past year. This year’s State of Ransomware in Retail report showed significant improvement in the sector’s ransomware outcomes mixed with a few concerning new trends. Retail organizations paid less money to attackers than any other sector and had the fastest recovery times of any year in the survey’s history.

An ARTEX build ships no secret scanner. In our lab, it found 8 of 9 planted secrets in seconds, even when asked only to assess the repo.

A new supply chain attack hits the news. A CVE with a dramatic name starts trending. A malicious package turns up in npm, PyPI, and Hugging Face. Within minutes, your Slack channels fill up, your CISO wants an update, and someone asks the question every DevSecOps professional dreads.