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

Imported sightings' confidence level is always "5 - Improbable" #6835

Open
misje opened this issue Apr 29, 2024 · 0 comments
Open

Imported sightings' confidence level is always "5 - Improbable" #6835

misje opened this issue Apr 29, 2024 · 0 comments
Labels
bug use for describing something not working as expected
Milestone

Comments

@misje
Copy link

misje commented Apr 29, 2024

Description

Imported sightings' confidence level is always "5 - Improbable"

Environment

  1. OS (where OpenCTI server runs): docker: opencti/platform:6.0.9
  2. OpenCTI version: 6.0.9
  3. OpenCTI client: 6.0.9
  4. Other environment details:

Reproducible Steps

The code in question is an enrichment connector producing a sighting between an observable and a identity (system), using a dummy indicator as sighting_of_ref. The code is not public yet. The connector runs as a user with max confidence set to 100, and confidence is set correctly on other entities and relationships.

I was hoping to provide a minimal STIX JSON example, but OpenCTI fails to import my sighting. There are no errors in the worker logs. The wokbench lists the sighting, but only the observable and entity are available in the database. The JSON is attached. It was produced from an investigation with a simple File observable, System identity and a sighting between them. It was attempted imported using the workbench and ImportFileStix.

sighting.json

Expected Output

The sighting imported from STIX should have the confidence from the user/group running the import/connector.

Actual Output

The confidence is "5 - Improbable", regardless of the user's max confidence level, or the confidence set in STIX. The confidence is correct for entities and relationships.

Additional information

@misje misje added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Apr 29, 2024
@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Apr 29, 2024
@Jipegien Jipegien added this to the Release 6.0.11 milestone Apr 29, 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
Projects
None yet
Development

No branches or pull requests

2 participants