Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1de68c67-af5c-4097-9c85-fe5578e09e67 issue #4584

Closed
swachchhanda000 opened this issue Nov 21, 2023 · 1 comment · Fixed by #4577
Closed

1de68c67-af5c-4097-9c85-fe5578e09e67 issue #4584

swachchhanda000 opened this issue Nov 21, 2023 · 1 comment · Fixed by #4577
Assignees
Labels
Bug Indicates a bug with one of the tools and features provided by the project Work In Progress Some changes are needed

Comments

@swachchhanda000
Copy link
Contributor

Description of the Idea of the Rule

Event id 4658 don't have field ObjectName. Event id 4658 can be leveraged by linking it back to the earlier event ID [4656] with the same handle ID. This rule is referencing objectName for 4658. Is this expected?

Same issue also in 39a80702-d7ca-4a83-b776-525b1f86a36d

Public References / Example Event Log

https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4658
https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=4658

@nasbench
Copy link
Member

Thanks for the report. Will look into this and see what can be done.

@nasbench nasbench added Bug Indicates a bug with one of the tools and features provided by the project Work In Progress Some changes are needed labels Nov 21, 2023
@nasbench nasbench linked a pull request Nov 21, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Indicates a bug with one of the tools and features provided by the project Work In Progress Some changes are needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants