Appendix A All Event Types

Every event type in this book, in one table. Thirty-four types across six emitters, plus the registry's watch records, which are a separate mechanism.

A.1 KMES events #

TypeEmitterWhere
access-auditKACS§3.1
continuous-auditKACS§3.2
privilege-useKACS§3.3
caap-policy-diagnosticKACS§3.4
logon-session-destroyedKACS§3.5
corrupt-sdKACS§3.6
STRATAFS_COPY_UPStrataFS§4.1
STRATAFS_MUTATION_REFUSEDStrataFS§4.2
LCS_KEY_OPEN_AUDITLCS§5.2
LCS_BACKUP_STARTLCS§5.1
LCS_BACKUP_COMPLETELCS§5.1
LCS_RESTORE_STARTLCS§5.1
LCS_RESTORE_COMPLETELCS§5.1
LCS_SOURCE_VALIDATION_FAILURELCS§5.3
LCS_SELF_CONFIG_INVALIDLCS§5.3
job.createdpeinit§6.1
job.startedpeinit§6.1
job.endedpeinit§6.1
operation.requestedpeinit§6.2
operation.startedpeinit§6.2
operation.completedpeinit§6.2
operation.failedpeinit§6.2
operation.cancelledpeinit§6.2
operation.mergedpeinit§6.2
operation.abortedpeinit§6.2
peipkg.installpeipkg§7.1
peipkg.upgradepeipkg§7.1
peipkg.uninstallpeipkg§7.1
peipkg.refreshpeipkg§7.1
peipkg.transaction-failedpeipkg§7.1
peipkg.recoverypeipkg§7.1
peipkg.authorisationpeipkg§7.1
peipkg.repo-addpeipkg§7.1
peipkg.repo-removepeipkg§7.1
peipkg.claimpeipkg§7.1
peipkg.config-changepeipkg§7.1specified, not emitted

A.2 Not KMES #

TypeEmitterTransportWhere
synthetic.gapeventdWritten direct to a shard§8.1
synthetic.startupeventdWritten direct to a shard§8.1
synthetic.shutdowneventdWritten direct to a shard§8.1
synthetic.storage_erroreventdWritten direct to a shard§8.1
synthetic.config_changeeventdWritten direct to a shard§8.1
Watch recordsLCSread() on a key fd§5.4

A.3 Which carry an identity, and how #

EventsIdentity from
KACS, all but logon-session-destroyedsubject record in the payload (§2.1)
logon-session-destroyeduser_sid and session_id directly; the session was the subject
LCS, six of sevencaller summary in the payload (§2.3)
StrataFS, peinit, peipkgThe envelope only. No identity in the payload (§1.2)
eventd syntheticNone. eventd is describing itself

A.4 Known holes #

Collected from the chapters, because a reader planning coverage needs them in one place:

  • peipkg.config-change is never emitted (§7.1).
  • peipkg omits the source repository on install and upgrade, the transaction id on committed cross-root success, and emits nothing for automatic recovery, recovery failures, declined prompts, insecure transport, unsigned installs under an optional policy, or peipkg-compose (§7.2).
  • A registry key open requesting MAXIMUM_ALLOWED alone emits no LCS_KEY_OPEN_AUDIT, because the mapped desired mask is zero and no ACE matches zero (§5.2).
  • StrataFS refusals raised before a provider is known emit an empty provider_stratum (§4.2).
  • caap-policy-diagnostic with kind = staging-mismatch does not identify which rule differed, and its two masks can be equal while object_results_differ is true (§3.4).
  • There is no logon-session-created, no token-created, and no heartbeat (§3.6).
  • peipkg emits nothing when the caller's token lacks the audit privilege (§7.1).

Edit this page