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.

Sign up for GitHub

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

Jump to bottom

Need to improve our management of active/inactive endpoint status based on executors #2234

Closed
RomuDeuxfois opened this issue Jan 17, 2025 · 2 comments · Fixed by #2235
Closed

Need to improve our management of active/inactive endpoint status based on executors #2234

RomuDeuxfois opened this issue Jan 17, 2025 · 2 comments · Fixed by #2235
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved The issue has been solved
Milestone
Release 1.11.2

Comments

@RomuDeuxfois
Copy link
Member

Description

We have 4 executors: OpenBAS agent, Caldera, Tanium and Crowdstrike.

These do not have the same way to handle health management.
Which poses a problem on our way to display active/inactive endpoint status.

The main rule on OBAS is : An endpoint that has not been pinged within three minutes is considered inactive.
This is related to our obas agent which pings every minute, but does not make sense with another executor which can ping every 5, 10 or X minutes.
@RomuDeuxfois RomuDeuxfois added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Jan 17, 2025
@RomuDeuxfois
Copy link
Member Author

Seen with @SamuelHassine, for the moment we set the Threshold at 1 hour on our side.

@RomuDeuxfois RomuDeuxfois closed this as not planned Won't fix, can't repro, duplicate, stale Jan 17, 2025
@RomuDeuxfois RomuDeuxfois reopened this Jan 17, 2025
@RomuDeuxfois RomuDeuxfois added bug use for describing something not working as expected and removed feature use for describing a new feature to develop labels Jan 17, 2025
@guillaumejparis guillaumejparis mentioned this issue Jan 17, 2025
Merged
6 tasks
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 17, 2025
@jborozco jborozco added this to the Bugs backlog milestone Jan 17, 2025
@jborozco jborozco added the critical use to identify critical bug to fix ASAP label Jan 17, 2025
@jborozco
Copy link

mandatory to make crowdstrike executor work properly

guillaumejparis added a commit that referenced this issue Jan 17, 2025
@guillaumejparis
[backend] pass agent active threshold to 1h (#2234)
3217cd0
@guillaumejparis guillaumejparis added the solved The issue has been solved label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved The issue has been solved
Projects
None yet
Milestone
Release 1.11.2
Development

Successfully merging a pull request may close this issue.

[backend] pass agent active threshold to 1h (#2234) OpenBAS-Platform/openbas
3 participants
@guillaumejparis @jborozco @RomuDeuxfois