An update on our situation: With the latest macos patches, this seems to affect not only macos 14 but other (all?) macos versions as well. We have a service running as LaunchDaemon. This service can mount a network share and access it without any problems. When this service creates a subprocess, this subprocess cannot access the network share mounted by the parent. Even the subprocess "cat /" fails with "Operation not permitted" - apparently rejected by MAC. A few weeks ago that was not a problem. If i grant "Full Disk Access" to the parent process, the child can access the share alright. Is there a way to make this work without having to set Full Disk Access? A specific mount point location or flag to set? Previously we worked with the home directory /var/opsisetupadmin of a user specifically created for this purpose. If it really would be necessary to set Full Disk Access, is there a way to initiate this through a command? I understand that you want to have manual user interaction involved. But is there a way to simply prompt the user to allow access, without them having to manually go through system settings?