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

Based on relationship should inherit markings & restrictions when created from Indicators or observables #6068

Closed
SouadHadjiat opened this issue Feb 21, 2024 · 0 comments · Fixed by #6069
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)
Milestone

Comments

@SouadHadjiat
Copy link
Member

Description

When creating an observable from an indicator or vice versa, we create automatically a "based on" relationship that should inherit object markings and organization sharing. This is not the case.
The issue happens during indicator or observable creation with the option to promote or extract observable / indicators, also in corresponding playbooks, and bulk tasks (indicators/observables generation).

Environment

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

Reproducible Steps

Multiple scenarios for this bug :

  1. Create an indicator with option "Create observables from this indicator"
  2. Create an observable with option "Create an indicator from this observable"
  3. Playbooks: Set a playbook with component "Promote observable to indicator" / and another one with "Extract observables from indicator"
  4. Bulk actions : select multiple indicators / observables and apply action from the bottom toolbar "Indicators/observables generation".

All these scenarios will create observables or indicators with a relationship "based on". All the objects created and relationship should inherit markings and organization sharing.

@SouadHadjiat SouadHadjiat added the bug use for describing something not working as expected label Feb 21, 2024
@SouadHadjiat SouadHadjiat added this to the Release 6.0.0 milestone Feb 21, 2024
@SouadHadjiat SouadHadjiat self-assigned this Feb 21, 2024
SouadHadjiat added a commit that referenced this issue Feb 21, 2024
…s when created from Indicators or observables (#6068)
SouadHadjiat added a commit that referenced this issue Feb 26, 2024
…s when created from Indicators or observables (#6068)
SouadHadjiat added a commit that referenced this issue Feb 27, 2024
…s when created from Indicators or observables (#6068)
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 27, 2024
Archidoit pushed a commit that referenced this issue Jun 6, 2024
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
3 participants