Describe the bug
We are currently parsing the AccessMask field of all incoming security events and applying the descriptions below to the AccessMaskDescription field. For most events this is correct, however, in the case of event 4663 it is not. The code in question is here https://github.com/elastic/beats/blob/main/x-pack/winlogbeat/module/security/ingest/security.yml#L2203-L2232 and is released as the logs-system.security-1.61.1-standard ingest pipeline.
Related Issue https://github.com/elastic/sdh-beats/issues/5277
Describe the bug We are currently parsing the
AccessMask
field of all incoming security events and applying the descriptions below to theAccessMaskDescription
field. For most events this is correct, however, in the case of event 4663 it is not. The code in question is here https://github.com/elastic/beats/blob/main/x-pack/winlogbeat/module/security/ingest/security.yml#L2203-L2232 and is released as thelogs-system.security-1.61.1-standard
ingest pipeline.An example event is here. https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4663 This event has an access mask of 0x6 which mean
WriteData
andAppendData
but we're applyingDelete Child
andList Contents
.Expected behavior We will need to parse the AccessMask field based on the event id number and apply the correct descriptions.