What Santa does when it cannot confirm that the file it evaluated is the image
the kernel loaded: the file changed during launch, or Santa could not read it. If the file
on disk still has the signing identity the kernel reported, Santa evaluates it normally and
this key does not apply.
The default depends on the client mode. In Monitor mode, Enforce behaves as Report, so Santa
does not deny an execution in Monitor mode because its file changed or could not be read, except
for the SEATBELT case below. Temporary Monitor Mode counts as Monitor mode.
| Client mode | Unset or Enforce | Report | Ignore |
|---|
| Monitor | Report | Report | Ignore |
| Lockdown | Enforce | Report | Ignore |
| Standalone | Enforce | Report | Ignore |
Warning: in Lockdown and Standalone modes, Enforce denies every binary that Santa cannot
read. This includes short-lived build outputs and binaries on unreliable network or removable
volumes. If this affects your fleet, use Report.
Under Report and Ignore, Santa evaluates rules against the file on disk, which may not be
the file that ran. If Santa cannot read the file, the FailClosed key decides what happens. The
two values differ only in event storage. Report always stores the event for the sync server.
Ignore stores the event under Santa's normal upload settings, so events can still be stored.
A binary a SEATBELT rule would sandbox is denied outright whenever its identity could not be
confirmed, under every value of this key and in every client mode.