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 standardize our way of gathering our endpoints depending on the executors #2233

Open
RomuDeuxfois opened this issue Jan 17, 2025 · 0 comments
Open

Need to standardize our way of gathering our endpoints depending on the executors #2233

RomuDeuxfois opened this issue Jan 17, 2025 · 0 comments
Assignees
@damgouj
Labels
feature use for describing a new feature to develop technical improvement Technical refactor or improvement is needed

Comments

@RomuDeuxfois
Copy link
Member

RomuDeuxfois commented Jan 17, 2025 •
edited
Loading

Description

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

These do not have the same way to retrieve the properties of the endpoint on which they are deployed.
Which poses a problem on our discriminating factor (the hostname) because is not populate the same depending on executors.
We have two different endpoints on the OpenBAS side, but only one endpoint in reality.

Exemple:

  • OpenBAS Agent -> Filigran-64
  • Crowsstrike -> FILIGRAN-64

Brainstorm

Lowercase hostname on each executor is enough for now.
@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 RomuDeuxfois changed the title Need to standardize our way of gathering our endpoints depending on the executioners. Need to standardize our way of gathering our endpoints depending on the executors Jan 17, 2025
@EllynBsc EllynBsc added technical improvement Technical refactor or improvement is needed and removed needs triage use to identify issue needing triage from Filigran Product team labels Jan 20, 2025
@damgouj damgouj self-assigned this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@damgouj damgouj

Labels
feature use for describing a new feature to develop technical improvement Technical refactor or improvement is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@EllynBsc @RomuDeuxfois @damgouj