EventRecordID Gaps Catch Crude Deletion. Unreferencing Plus Renumbering Can Keep the Sequence Clean
An attacker who can manipulate the active or offline EVTX can pull a single 4624 out of the Security log without inherently firing Event ID 1102 — and, by renumbering the records that follow, without leaving a hole in the EventRecordID sequence your rule watches. Here is why gap detection misses that, and what actually catches it.