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.

Sign up for GitHub

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

Jump to bottom

Threat level/severity code inverted between The Hive and MISP #292

Closed

gilles-m opened this issue Aug 25, 2017 · 0 comments

Assignees

Milestone

gilles-m commented Aug 25, 2017

Threat level/severity code inverted between The Hive and MISP

Request Type

Bug

Work Environment

Question	Answer
OS version (server)	Debian Strech
TheHive version / git hash	2.12.1 / commit `8300fcc`
Package Type	Docker, Build from source

Problem Description

An event with a high threat level in MISP is imported into The Hive Project as alert with low severity

Steps to Reproduce

Import Event From MISP and compare fields.

Possible Solutions

Maybe change values in Constants.js file but I don't know the impact

Complementary information

When I compare these two codes, we see that the classification is reversed :
[TheHive] https://github.com/CERT-BDF/TheHive/blob/9c5c12b2f0dd17a6f47ecb5e8004b21a964726ba/ui/app/scripts/services/Constants.js
[MISP] https://github.com/MISP/MISP/blob/90c28602c31d88f576f3d676c31d439ad3e58e68/app/Test/Fixture/ThreatLevelFixture.php

The text was updated successfully, but these errors were encountered:

To-om self-assigned this

To-om added this to the 2.13.0 milestone

To-om added a commit that referenced this issue


          #292 Fix MISP threat level and Thehive severity convertion

6c4489d

To-om closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment