Another update. We have been able to get the TCC db happy by setting the user for the app to the current user and then prompting them to allow FDA. This works fine on all architectures on macOS 14 and 15. We also believe that it was working in macOS 26.0, but it fails to work on 26.2. The problem is that fidelisevents does not populate into the FDA screen, but is in the TCC db as kTCCServiceEndpointSecurityClient|com.fidelisendpoint.fidelisevents|0|1761918781|5. Then when the user manually adds the app it loads in as the app, not the service so FDA is only given to the app. Is this a permissions problem that keeps it from being populated to FDA screen or is there something else keeping the system from tying the app to the service?
Topic:
App & System Services
SubTopic:
Core OS
Tags: