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

[Playbook] Manipulating knowledge by replacing status does not work on all entities. #7114

Open
NiQuintin opened this issue May 24, 2024 · 1 comment · May be fixed by #7408
Open

[Playbook] Manipulating knowledge by replacing status does not work on all entities. #7114

NiQuintin opened this issue May 24, 2024 · 1 comment · May be fixed by #7408
Assignees
Labels
bug use for describing something not working as expected
Milestone

Comments

@NiQuintin
Copy link

NiQuintin commented May 24, 2024

Description

Trying to automatically replace the status on an exploits relationship via Manipulate Knowledge does not work. The same behavior occurs on other entities such as request for takedown, for information, but works on others such as reports, incidents, Incident response, etc.

OK for:

  • Report Malware Analysis IR Incident Channel

Need to be fixed for:

  • relationship grouping note case RFT case RFI feedback observedData campaign tool vulnerability
  • attackPattern narrative course of action dataComponent dataSource Region Area Country City Position

Environment

OpenCTI 6.1.4

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a playbook that listen entity-type exploits,
  2. Add a step "Manipulate knowledge" and set a replace status for the second stage of the worklow,
  3. From a vulnerability, in knowledge, create a relation exploits with a vulnerability.
  4. Check the relation's status.

Expected Output

The status is automatically changed to the status defined in Manipulate Knowledge.

Actual Output

The status remains on the first step of the workflow and cannot be changed automatically.

Additional information

On entities such as relations, where this does not work for status, manipulate knowledge does manage to play on labels.

Screenshots (optional)

workflow

@NiQuintin NiQuintin added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels May 24, 2024
@nino-filigran
Copy link

Validated, the status of the relation does not get updated. Test automation: https://testing.octi.staging.filigran.io/dashboard/data/processing/automation/f24f9967-0bbc-421f-9e0d-98824f8af8a0

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants