In my brief testing, unfortunately, the
user sid of <event log record> did not return the desired result in this particular case (it didn’t via Event Viewer either).
Querying the Windows Event Log (especially the Security Event log) can be fairly expensive given the number of records. For such cases, I like to reference @strawgate’s post here on how to do so more efficiently (a very interesting approach!): Relevance: Speeding Up Event Log Queries
Utilizing that general construct, here’s a sample bit of relevance that will actually parse the output of the description to return the string specified after ‘Account Name’, and return only unique values (I’ve not really tested this very much):
unique values of (preceding text of first "%0d%0a" of following text of first "Account Name:%09%09" of it) of descriptions of records ((integers in (item 0 of it + item 1 of it - 1, maximum of (item 0 of it + item 1 of it - 500;item 1 of it))) of (record count of it, oldest record number of it)) whose (event id of it = 4624 OR event id of it = 4634) of security event log