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

[Auditbeat] Host: Fix reboot detection logic #12591

Merged
merged 2 commits into from
Jun 18, 2019

Conversation

cwurm
Copy link
Contributor

@cwurm cwurm commented Jun 18, 2019

On Windows, BootTime is not fully accurate and can vary by a few milliseconds (see Remarks for GetTickCount64). This causes a lot of false positive event.action: reboot events.

This PR changes to only report a reboot if the new BootTime is at least 1 second after the old. This should fix Windows and not affect the other platforms, assuming it's impossible to reboot a system twice in 1 second.

@cwurm cwurm added bug review needs_backport PR is waiting to be backported to other branches. Auditbeat SecOps labels Jun 18, 2019
@cwurm cwurm requested a review from a team as a code owner June 18, 2019 07:37
@elasticmachine
Copy link
Collaborator

Pinging @elastic/secops

@cwurm cwurm merged commit 9d73bdc into elastic:master Jun 18, 2019
@cwurm cwurm deleted the fix_reboot_detection branch June 18, 2019 10:03
cwurm pushed a commit to cwurm/beats that referenced this pull request Jun 18, 2019
On Windows, `BootTime` is not fully accurate and can vary by a few milliseconds. This causes a lot of false positive `event.action: reboot` events.

This changes to only report a reboot if the new `BootTime` is at least 1 second after the old. This should fix Windows and not affect the other platforms, assuming it's impossible to reboot a system twice in 1 second.

(cherry picked from commit 9d73bdc)
@cwurm cwurm added v7.2.0 and removed needs_backport PR is waiting to be backported to other branches. labels Jun 18, 2019
cwurm pushed a commit to cwurm/beats that referenced this pull request Jun 18, 2019
On Windows, `BootTime` is not fully accurate and can vary by a few milliseconds. This causes a lot of false positive `event.action: reboot` events.

This changes to only report a reboot if the new `BootTime` is at least 1 second after the old. This should fix Windows and not affect the other platforms, assuming it's impossible to reboot a system twice in 1 second.

(cherry picked from commit 9d73bdc)
@cwurm cwurm added the v6.8.1 label Jun 18, 2019
cwurm pushed a commit that referenced this pull request Jun 18, 2019
…ic (#12594)

On Windows, `BootTime` is not fully accurate and can vary by a few milliseconds. This causes a lot of false positive `event.action: reboot` events.

This changes to only report a reboot if the new `BootTime` is at least 1 second after the old. This should fix Windows and not affect the other platforms, assuming it's impossible to reboot a system twice in 1 second.

(cherry picked from commit 9d73bdc)
cwurm pushed a commit that referenced this pull request Jun 18, 2019
…ic (#12595)

On Windows, `BootTime` is not fully accurate and can vary by a few milliseconds. This causes a lot of false positive `event.action: reboot` events.

This changes to only report a reboot if the new `BootTime` is at least 1 second after the old. This should fix Windows and not affect the other platforms, assuming it's impossible to reboot a system twice in 1 second.

(cherry picked from commit 9d73bdc)
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…ion logic (elastic#12594)

On Windows, `BootTime` is not fully accurate and can vary by a few milliseconds. This causes a lot of false positive `event.action: reboot` events.

This changes to only report a reboot if the new `BootTime` is at least 1 second after the old. This should fix Windows and not affect the other platforms, assuming it's impossible to reboot a system twice in 1 second.

(cherry picked from commit 4c44828)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants