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

Related containers / correlation enhancements #3227

Closed
SamuelHassine opened this issue Apr 24, 2023 · 2 comments
Closed

Related containers / correlation enhancements #3227

SamuelHassine opened this issue Apr 24, 2023 · 2 comments
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@SamuelHassine
Copy link
Member

SamuelHassine commented Apr 24, 2023

Use case

When we display the list of "correlated containers":

image

Right now, it is based on common observables and indicators. That being said:

  • Nobody really know this, so most of the time, it is a blackbox.
  • You don't have any details about which observable or indicators is contained "common" to the 2 containers
  • Most of all, when you have multiple correlated containers, it is difficult to know which one it is.

In addition to this, when you are exploring the "correlation view" in the graph (3 clicks away), it is correlating on "everything", not only indicators and observables, so you have to refilter. So to get the real details about correlated containers in the overview, assuming you know how this work, it is more than 5 or 6 clicks away.

We need to implement a quick button here:

image

This button will open a dialog with a table of correlations with details. Something like the list of containers and the number of common objects and you can expand to see the the list of those objects for each container.

What's the functional need
ability to understand among the different correlated cases/reports, the level of correlation (is it high, low...)
ability to view the list of correlated entities
ability to pivot on them/perform actions on them
Potential solution
Potential Solution 1
Add a counter next to each report/cases to indicate the amount of correlated entities/observables
Ability to click on a CTA and be redirected to data/entities to see the list of entities/observables
To do this, add a new filter "contained in = Container A" that would list all entities contained in entity A
Add a filter on the meta type Entity Type = Observable
The screen data entities should be filtered on "contained in = Container A AND container B" AND "entity Type = Indicator OR observable"
BONUS: extend the correlation between containers of different types (ex: a report can be correlated with a case)

Potential Solution 2
Add a counter next to each report/cases to indicate the amount of correlated entities/observables
click on CTA to open a modal that contains all containers correlated, with an option to expand the view of correlated entities

@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Apr 24, 2023
@SamuelHassine SamuelHassine added this to the Release 5.9.0 milestone Apr 24, 2023
@Jipegien Jipegien modified the milestones: Release 5.11.0, Long-term candidates Jul 26, 2023
@SamuelHassine SamuelHassine removed the P1 label Jan 6, 2024
@Jipegien Jipegien removed this from the Long-term candidates milestone Apr 23, 2024
@nino-filigran nino-filigran added this to the Release 6.4.0 milestone Aug 22, 2024
@labo-flg labo-flg removed their assignment Nov 8, 2024
delemaf added a commit that referenced this issue Jan 9, 2025
delemaf added a commit that referenced this issue Jan 9, 2025
delemaf added a commit that referenced this issue Jan 9, 2025
delemaf added a commit that referenced this issue Jan 9, 2025
delemaf added a commit that referenced this issue Jan 15, 2025
delemaf added a commit that referenced this issue Jan 15, 2025
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 27, 2025
@SamuelHassine SamuelHassine reopened this Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

10 participants