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

Create Indicator Entity doesn't include "Pattern Type" #961

Closed
DR913 opened this issue Dec 22, 2020 · 0 comments
Closed

Create Indicator Entity doesn't include "Pattern Type" #961

DR913 opened this issue Dec 22, 2020 · 0 comments
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

@DR913
Copy link

DR913 commented Dec 22, 2020

Description

When creating an Indicator outside of the indicator page (from a report, for example), the "Pattern Type" Field is not displayed. Since this field is immutable, it always creates indicators with unknown types

Environment

  1. OS (where OpenCTI server runs): Ubuntu 20.04
  2. OpenCTI version: OpenCTI 4.0.3
  3. OpenCTI client: front end
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to the "Entities" section of a report in the
  2. Click to add an Indicator (Plus sign in the low right corner)
  3. Click to add a new Indicator (Plus sign in the low right corner again)
  4. Select "Indicator"

Expected Output

A Pattern Type field should exist.

Actual Output

There will be no filed to select a pattern type.

Additional information

There's also no field for actually entering the pattern. I haven't inspected each one individually, but it seems like all the entity add screens are the same and there will likely be other immutable fields that will cause problems.

@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Dec 22, 2020
@SamuelHassine SamuelHassine added this to the Release 4.0.4 milestone Dec 22, 2020
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Dec 22, 2020
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

2 participants