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

Malware global kill chain doesn't display correct info #4155

Closed
Archidoit opened this issue Aug 24, 2023 · 2 comments · Fixed by #4158
Closed

Malware global kill chain doesn't display correct info #4155

Archidoit opened this issue Aug 24, 2023 · 2 comments · Fixed by #4158
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Archidoit
Copy link
Member

Archidoit commented Aug 24, 2023

Description

Malware global kill chain lines always display the entity in the 'to' of the relationship.

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: { e.g. OpenCTI 1.0.2 }
  3. OpenCTI client: { e.g. frontend or python }
  4. Other environment details:

Reproducible Steps

  • Go to the Knowledge tab of a malware
  • Add a relationship with several threat actor group/individual
  • At the bottom of the Knowledge tab, go on 'Global kill chain'
  • The relationship appears but we have no info on which entity is linked to the malware. If we want to edit a relation there, we don't know which relation we edit, etc.

Explanation: The entity displayed in the line is always the 'to' of the relationship

image

@Archidoit Archidoit added the bug use for describing something not working as expected label Aug 24, 2023
@Archidoit Archidoit self-assigned this Aug 24, 2023
@Archidoit
Copy link
Member Author

Archidoit commented Aug 24, 2023

2 solutions:

  • display the 'from' of the relationship when the 'to' is the entity itself
  • don't display relationships when the 'to' it the entity itself

@SamuelHassine
Copy link
Member

@Archidoit please use the first solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants