MacOS 15 Sequoia Update Incompatibility Issues with Multiple Security Tools

TapTechNews September 20th news, the tech media TechCrunch released a blog post yesterday (September 19th), reporting that many security tools developed by companies including CrowdStrike, SentinelOne, and Microsoft are not compatible with the macOS 15 Sequoia update.

Users have reported that after upgrading the macOS 15 Sequoia update, there may be a situation where mainstream security tools cannot operate normally, and the specific problem is not yet clear.

The founder of the security startup DoubleYou, Patrick Wardle, expressed the feeling of helplessness of 'taking the blame'. TapTechNews translated his complaint as follows:

As a macOS security tool developer, having to face (understandably) emotional users (understandably) blaming their Mac malfunctions on your tool time and time again, while in fact it's always Apple's fault, is extremely frustrating.

Writing a bug-free system is extremely challenging, but perhaps if Apple reduced the time and money spent on marketing and instead focused more on actually testing its software, we would all benefit a lot!

On the day of the macOS Sequoia release, a sales engineer from CrowdStrike said in the Mac administrators' Slack channel that the company had to postpone providing support for the new Mac operating system.

MacOS 15 Sequoia Update Incompatibility Issues with Multiple Security Tools_0

The engineer said in the message:

We are very sorry to inform you that although we intended (and as usual) to support the latest operating system within a few hours after [the official release], we will not be able to provide support for Sequoia at the first time.

The engineer also said that CrowdStrike has sent a 'technical report' to customers and added that 'there are quite a lot of changes in the network stack.'

The sales engineer said:

We are also tracking similar problems from other vendors and have provided feedback and cases to Apple. Although we hope there will be a quick follow-up patch to solve this problem, we are acting on the assumption that there will be no such patch and plan to make fixes in our code through sensor updates.

Likes