Boot sequence with user applications starting before Launch daemons and even system extensions clearly represents a potential security risk.
It is very clearly visible when using FileVault. In this case user needs to enter password, OS decrypts volume and then it can startup and launch processes, but very quickly opens user's Desktop and starts to open applications.
The bigest problem is that for example Endpoint system extension, which defends computer from infections or Network system extension, which scans network traffic and defends against infected web pages, email, etc. cannot immediately block harmful content. PIDs of these processes are larger than for example Launch Daemons.
It means that for example Mail could open very quickly and load new message before Network System extension is loaded and traffic captured and scanned.
We see it especaily on new OS versions running on ARM where it can take up to 10-30 seconds to properly load everything to protect users. That happens when OS is setup with FileVault and user has many, many applications opened - Mail, Calendar, Safari with lots of tabs, Teams, Remote Desktop, etc, etc. When user reboots computer, we clearly see this delay in start up of critical processes that should protect users, especially in corporate environment.
Bootup sequence should look something like this:
System Extenisons
Launch Daemons
Launch Agents
User applications
Is there a way to setup this sequence of process start up?
Thanks,
Robert
Topic:
App & System Services
SubTopic:
Core OS
Tags: