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

Elastic Defend Missing File Change Record or Wrong Event Action Record #36935

Open
jasoncyp opened this issue Oct 23, 2023 · 3 comments
Open
Assignees
Labels
Team:Security-Linux Platform Linux Platform Team in Security Solution

Comments

@jasoncyp
Copy link

When Elastic Defend Full EDR activated, it should collect the file change events by which users, but when I try to collect event. file creation and deletion are normal and can be recorded correctly. But when file change using below command, it got problem.

  1. using nano to modify existing file, no event collected.
  2. using vi/vim to modify existing file, event.action shows "creation", which is wrong description.

For confirmed bugs, please report:

  • Version: 8.10
  • Operating System: ubuntu 20.04
  • Discuss Forum URL:
  • Steps to Reproduce:
  1. when use "nano" command to make change of existing linux file, it does not record the event, only when nano command to create new file, the event.action with "creation" will be recorded.
  2. when use "vi/vim" command, the event will be recorded, but the event.action shows "creation", which is wrong category, this will affect the security analysis.
@jasoncyp jasoncyp self-assigned this Oct 23, 2023
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@jasoncyp jasoncyp changed the title Elastic Defend Elastic Defend Missing File Change Record or Wrong Event Action Record Oct 23, 2023
@andrewkroh
Copy link
Member

andrewkroh commented Oct 23, 2023

If this is for Elastic Defend then I think the issue is best logged in https://github.com/elastic/endpoint.

@efd6
Copy link
Contributor

efd6 commented Oct 24, 2023

Also note that some editors work in a temporary file and then create the final on write-out, so vim is very probably writing a new file when you make a change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Security-Linux Platform Linux Platform Team in Security Solution
Projects
None yet
Development

No branches or pull requests

5 participants