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

Microsoft Sentinel collector not working #1685

Open
EllynBsc opened this issue Oct 18, 2024 · 2 comments · Fixed by #1712 or OpenBAS-Platform/client-python#37 · May be fixed by #1844
Open

Microsoft Sentinel collector not working #1685

EllynBsc opened this issue Oct 18, 2024 · 2 comments · Fixed by #1712 or OpenBAS-Platform/client-python#37 · May be fixed by #1844
Assignees
Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature
Milestone

Comments

@EllynBsc
Copy link
Member

Description

Microsoft Sentinel collector not working, we don' have have the right prevention detection on Sentinel

@EllynBsc EllynBsc added the bug use for describing something not working as expected label Oct 18, 2024
@EllynBsc EllynBsc added this to the Bugs backlog milestone Oct 18, 2024
@RomuDeuxfois RomuDeuxfois self-assigned this Oct 21, 2024
@jborozco jborozco modified the milestones: Bugs backlog, Release 1.9.0 Oct 22, 2024
@EllynBsc EllynBsc added the regression Label to identify the bug as a regression of previously working feature label Oct 22, 2024
@RomuDeuxfois RomuDeuxfois reopened this Oct 23, 2024
@RomuDeuxfois
Copy link
Member

Need to re align for the Detection & Prevention expectations:

  • The Detection expectation is validated BUT on the log it seems we have a Prevention case
  • The agent has the status MAYBE_PREVENTED

Logs on Sentinel
Action
A. Validate the alert.

  1. Contact the user who ran the tool to verify whether the activity was legitimate and inspect the endpoints for suspicious behavior.
  2. Locate unfamiliar processes in the process tree. Check files for prevalence, their locations, and digital signatures.
  3. Submit relevant files for deep analysis and review file behaviors.
  4. Identify unusual system activities with system owners.

B. Scope the incident. Find related devices, network addresses, and files in the incident graph.

C. Contain and mitigate the breach. Stop suspicious processes, isolate affected devices, decommission compromised accounts, or reset passwords, block IP addresses and URLs, and install security updates.

D. Contact your incident response team, or contact Microsoft support for investigation and remediation services.

Code

if "Action" in extended_properties and extended_properties["Action"] in [
            "blocked",
            "quarantine",
            "remove",
        ]:
            return True
        return False

@RomuDeuxfois
Copy link
Member

Don't forget to build a check list on what to implement to be a valid collector -> usefull for Crowdstrike and the others one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment