mirror of https://github.com/MISP/misp-website
grammar
parent
f4042995d3
commit
70105d0f74
|
@ -14,13 +14,13 @@ In MISP 2.4.116, a decaying functionality was added to allow users and organisat
|
|||
|
||||
Based on the feedback of the organisations relying on the decaying feature, the following improvements were included:
|
||||
|
||||
- New setting `default_restsearch_parameters` allowing users to supply restSearch parameters that will be automatically passed during API fetch. The main purpose of this new setting is to enable users to inject filters when integrating with third-party tools not offering the possibility to control the query performed against MISP. This for example allow to add default decaying parameters to all restSearch query done.
|
||||
- Added a new user setting, `default_restsearch_parameters`, allowing users to supply restSearch parameters that will be automatically passed to the export mechanism during API queries fetch. The main purpose of this new setting is to enable users to inject filters when integrating with third-party tools not offering the possibility to control the queries performed against MISP. This for example allow to set the default decaying parameters to all restSearch queries performed by the given user.
|
||||
|
||||
- New setting `tag_numerical_value_override` allowing users to override the `numerical_value` of tags. The main purpose of this new setting is to let users have their own numerical values for tags. It does not constrain site-admin to diverge from the official misp-taxonomy repository, and let them define new values for entries not having one.
|
||||
- Added a new setting, `tag_numerical_value_override`, allowing users to override the `numerical_value` of tags. The main purpose of this new setting is to let users convey their own numerical values for tags. It does not constrain site-admins to the values provided by the official misp-taxonomy repositor, and instead allows them to define new values for entries not having a numerical value in the first place.
|
||||
|
||||
## Major changes in decay computation
|
||||
|
||||
Attribute's `last_seen` will now takes precedences over the attribute's `timestamp` if the former is set. In the decaying implementation prior to this version, if no sightings were recorded, the simulated last sighting was set on the `timestamp` value. However, in this new version, the `last_seen` value will be used instead. Users will be able to alter attributes (attach tags, modify `last_seen`, ...) without refreshing the decaying score to its maximum value.
|
||||
Attributes' `last_seen` will now takes precedences over their `timestamp` if the former is set. In the decaying implementation prior to this version, if no sightings were recorded, the simulated last sighting was set on the `timestamp` value. However, in this new version, the `last_seen` value will be used instead. Users will be able to alter attributes (attach tags, modify `last_seen`, ...) without refreshing the decaying score to its maximum value.
|
||||
|
||||
# New widgets added to MISP
|
||||
|
||||
|
|
Loading…
Reference in New Issue